The build sequence says the dependency graph and the sequencing over it are a design target; the build loop sequences a spec's steps by their declared needs.

The build sequence says the dependency graph and the sequencing over it are a design target; the build loop sequences a spec's steps by their declared needs.

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/06-delivery/01-build-sequence.md:123 — "The dependency graph and the sequencing over it are a design target; readiness today is per-intent, through abcd intent ready."
• End B: .abcd/development/brief/04-surfaces/34-build.md:417 — "A lane opens for a spec step once every step it needs has landed (its - needs: line, or by default every step before it, ruling DR6b)"

01-build-sequence.md says the dependency graph over specs and tasks and the sequencing over it are a design target, with readiness today per-intent through abcd intent ready. 34-build.md says a lane opens for a spec step only once every step it needs has landed, read from each step's - needs: line: a dependency graph over a spec's steps, with sequencing over it, that ships. One of the two describes the shipped state wrongly.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 696.