Development record
The loop glossary says abcd never owns the run loop; the build chapter ships abcd's own implement loop.
The loop glossary says abcd never owns the run loop; the build chapter ships abcd's own implement loop.
A premise contradiction (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/loop.md:38— "abcd never owns the run loop." - End B:
.abcd/development/brief/04-surfaces/34-build.md:5— "It starts the implement loop: a loop over a state file, not a model, where every invocation reads the state, does at most one stage, writes the state and exits."
loop.md says abcd never owns the run loop (the iteration that picks up ready work and gates each step on a receipt): abcd defines the contract and a pluggable adapter supplies the loop. 34-build.md says abcd build starts abcd's own implement loop, a loop over a state file that the binary advances one stage per invocation. The glossary rule and the shipped loop cannot both hold.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 691.
Deferral 2026-10-27
Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.
Frontmatter
| id | iss-2610262037018200 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | major |
.abcd/work/issues/open/iss-2610262037018200-the-loop-glossary-says-abcd-never-owns.md
open on GitHub ↗ · commit history ↗
mentions10
- dcn-26102711123302352026-10-27 — The product thinker ruled on 2026-10-27 that the design brief shows the target design, in the present tense, with a status tag where a part is built, rather than the shipped state. With the ruling that behaviour lives in the command pages, the brief holds the product as aimed for and why, and the command pages hold what abcd does today. This reverses itd-147's currency rule, so a superseding ADR is owed, and the brief's checks are rebuilt around the status overlay.
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- dcn-26102711123395162026-10-27 — The product thinker ruled on 2026-10-27 that each abcd command's behaviour is written once, in its command page, which agents follow when they run it. The brief's chapter for the command keeps why the command exists, its trade-offs and why it refuses what it does, with its sub-verb table and generated appendix, and points to the command page for behaviour. The documentation-fidelity check moves to the command pages. This reverses the behaviour half of adr-2609231028044006 and invariant 18, so a superseding ADR is owed.
- iss-2610262035468845The glossary says abcd never owns the run loop; the site chapter reads the state file of abcd's own implement loop
- iss-2610262038283527The glossary keeps bare "the loop" for the record loop and says abcd never owns a run loop; the agent catalog uses bare "the loop" for abcd's own implement loop.
- iss-2610262040273336The loop glossary says abcd never owns the run loop; the build sequence says abcd's own loop ships through abcd build without the seam.
- iss-2610262040545166The glossary says abcd never owns the run loop; the build intent makes abcd's own verb that loop.
- iss-2610262040552734The glossary has a pluggable adapter supply the run loop; the drain draft puts the driving loop inside `abcd drain` itself.
- iss-2610262041372020The loop glossary says abcd never owns the run loop and an adapter supplies it; itd-82 sends drain's issues through the loop `abcd build` itself runs
- iss-2610262041445723The loop glossary entry says abcd never owns the run loop; the shipped pacing intent describes the loop abcd's own build, drain and implement verbs run.