Three segment leaves the contract has no row for
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
Curate the four leaves every segment kind shares: PillarChoice,
DuplicatePillarPolicy, Priority and MinDistance. The extractor records all
four, for every kind, with the type and default the ORE source states. What they
lack is a text: the guide explains them in the simple segment's prose and never
lists them as items, so no term carries a text and curve_parameter_rows.py writes
no row for a term without one.
Taken by Curate the shared segment leaves.
2. Why
The curve screen reads a segment's leaves from the projection's dispatch, so it draws all five leaves a simple segment reads. Three of them have no contract row, which the walk on 2026-10-30 shows as a dash and as 3 without documentation on the entry, and the page reads 238 of 289 parameters carry documentation where it read 238 of 238.
Conventions has a row because the guide lists it under each kind. The four that
do not are the ones the guide describes once, in prose, as settings of the segment
it is describing. The contract's rule is right: a term without a text is a gap,
not a row. What is missing is the person's text.