Development record

2026-09-15 — The 1:n intent–spec rule of adr-2609151513118583 is built, and the spec's `intent:` back-link is the single source of truth for which specs realise an intent (implementing session, ruling on iss-2609100508566552's build, reversible by the product thinker): the intent's `spec_id` stays a scalar meaning the spec it was planned with, the set is derived by one canonical comparison shared by the spec store, the intent corpus and the record-lint index (a zero-padded back-link once let one reader ship an intent the other saw as still open), and the bidirectional check becomes membership. `spec close <spc> --remainder <slug>` mints the follow-on spec before any move and reuses an open one with that slug on retry; `--remainder` is refused on a shipped intent or a closed spec; `--impact` at a close that does not ship is refused rather than ignored, because the flag's only effect is the judgement `shipped/` requires. The fidelity audit request names every spec that realised the intent and the receipt stays owed once per intent. Noted for the gate itd-2609111003026787 plans on the peer's branch, a commit declaring delivery of an intent must move it to shipped/: under this rule a change may deliver one spec and leave the intent planned with a remainder open, so that gate's condition should read "no open spec remains" when it is built. Rejected: an intent-side list of spec ids (a second writable carrier that can disagree with the store, and eighty-five records to edit); a new verb for the remainder (the close is the moment the remainder is known).