Development record
The out-of-scope page says the spec close that ships an intent is a manual step; the build loop's landing runs the close itself.
The out-of-scope page says the spec close that ships an intent is a manual step; the build loop's landing runs the close itself.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/06-delivery/03-out-of-scope.md:172— "the close is a manual step run in the change that lands the work" - End B:
.abcd/development/brief/04-surfaces/34-build.md:743— "In the lane's worktree it runs the spec's close (which ships the intent and parks the fidelity receipt)"
03-out-of-scope.md says nothing promotes a record on its own and the close is a manual step run in the change that lands the work. 34-build.md says the landing stage runs the spec's close in the lane's worktree, which ships the intent with no person running it. A build run does promote a record on its own, so the manual-step claim does not hold.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 695.
Frontmatter
| id | iss-2610262037049481 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262037049481-the-out-of-scope-page-says-the-spec.md
open on GitHub ↗ · commit history ↗