Development record
2026-10-28 — Merge-gate step 3 (itd-2610150602547271, recording the review pair's verdicts for a head) goes ahead while other copies hold files it shares, under the coordinator's narrowed rule for lapsed holds (recorded with the store-and-sweep change): a hold that overlaps only in files, on another subject, with nothing pushed, does not hold a ready change back. The laptop's iss-2610241107191205 shares only commands/land.md, has pushed nothing but its reservation ref, and is about lapsed holds and reservations in internal/core/claim. Step 3 changes no claim code and no behaviour of a lapsed hold or reservation: its change stays in internal/core/landing (a review receipt store beside the preflight receipts) and the land verb's --record-review flag. This machine's itd-2609151838312703 (sessions announce what they do) and itd-2610091010348892 (the hosted site) share land.md, 38-land.md, land.go and land_surface_test.go, but neither is about review receipts. With no shared subject, step 3 lands when it is ready, and whichever change lands second merges main. Ruled by the coordinator, abcd-f5, on 2026-10-28; applied by lane A.
2026-10-28 — Merge-gate step 3 (itd-2610150602547271, recording the review pair's verdicts for a head) goes ahead while other copies hold files it shares, under the coordinator's narrowed rule for lapsed holds (recorded with the store-and-sweep change): a hold that overlaps only in files, on another subject, with nothing pushed, does not hold a ready change back. The laptop's iss-2610241107191205 shares only commands/land.md, has pushed nothing but its reservation ref, and is about lapsed holds and reservations in internal/core/claim. Step 3 changes no claim code and no behaviour of a lapsed hold or reservation: its change stays in internal/core/landing (a review receipt store beside the preflight receipts) and the land verb's --record-review flag. This machine's itd-2609151838312703 (sessions announce what they do) and itd-2610091010348892 (the hosted site) share land.md, 38-land.md, land.go and land_surface_test.go, but neither is about review receipts. With no shared subject, step 3 lands when it is ready, and whichever change lands second merges main. Ruled by the coordinator, abcd-f5, on 2026-10-28; applied by lane A.
Frontmatter
| id | dcn-2610281727151348 |
|---|---|
| type | decision |
| date | 2026-10-28 |
.abcd/work/decisions/dcn-2610281727151348-merge-gate-step-3-itd-2610150602547271.md
open on GitHub ↗ · commit history ↗
mentions4
- iss-2610241107191205A lapsed hold or reservation must be lifted without a person, or autonomous work waits on a holder that no longer exists. On 2026-10-24 a computer that had reserved a release cut (rel-v0.15.2) and dozens of issues and intents crashed. Its leases lapsed, yet sessions on another machine kept waiting on it: one session relayed the release hold to six others as live, from a read made before it lapsed, two finished pull requests waited for the dead cut's ruling, and a build was held behind the crashed copy's work. The product thinker ruled the same day that lifting a lapsed hold is autonomous: no person is needed to declare a lapsed holder gone. The reading side already counts a reservation five minutes past its expiry as released. What is missing is that every reader, verb and agent instruction acts on that, and that spent branches leave origin without a person. This record carries the ruling that the whole path runs unattended.
- itd-2609151838312703Sessions under any account, on any machine or in the cloud announce what they are doing through short fixed-form announcements on the shared remote, a person reads everyone's status with one command, and what is really a hold stays a reservation
- itd-2610091010348892An opted-in project's record is built at each release onto its own GitHub Pages
- itd-2610150602547271The facilitator's mode gates the merge