Development record
The step glossary says the build loop takes a spec's steps one lane at a time; the build chapter runs lanes in parallel up to a ceiling.
The step glossary says the build loop takes a spec's steps one lane at a time; the build chapter runs lanes in parallel up to a ceiling.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/step.md:18— "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" - End B:
.abcd/development/brief/04-surfaces/34-build.md:406— "A run works in parallel up to its ceiling (ruling DR6, spc-2609202134341288)."
step.md says abcd build takes a spec's steps one lane at a time, the next pending step opening the next lane only when a lane is done. 34-build.md says a run works in parallel up to its ceiling (ruling DR6), so several of a spec's steps can be in lanes at once. A reader building from the glossary would serialise what the loop runs in parallel.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 693.
Frontmatter
| id | iss-2610262037021391 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037021391-the-step-glossary-says-the-build-loop.md
open on GitHub ↗ · commit history ↗
mentions1
- spc-2609202134341288an-autonomous-implementation-run-paces-itself-by-default-and