step

A step is the unit below a spec (itd-2609212103565953, planned): the spec's author lists them in order, each with its own footprint, and the build loop (abcd build) takes them one lane at a time, the spec's next pending step opening the next lane when a lane is done. A step that does not fit a cut leaves the rest as the spec's remainder. In the build loop the word names the spec's piece and nothing else (BU1, iss-2609291313276243): the build loop lands each step as one lane and takes that lane through its stages — worktree, brief, implement, validate, land — and abcd implement step performs one stage, not one step. The run's state file and the loop's payloads keep the two apart: spec_step and step_title name the spec's step, stage the lane's.

When to use

When a spec is larger than one implementer can hold and land. Not as a task tracker: a step is a section of the design record, not a record of its own.

Related terms

• record families — the one page that maps the record families and how they relate