Development record
Multi-agent claims live in-tree under `.abcd/coordination/` per the universal patterns, but in the machine-scoped run store per the implement chapter
Multi-agent claims live in-tree under .abcd/coordination/ per the universal patterns, but in the machine-scoped run store per the implement chapter
A scope leakage (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/05-internals/04-universal-patterns.md:139— "Coordination state (file locks likeshape.lock, multi-agent claims per itd-33) lives at.abcd/coordination/" - End B:
.abcd/development/brief/04-surfaces/27-implement.md:3— "It holds a run's shared state in the machine-scoped store, records the sessions that join it, makes a record the unit of exclusion between them with a claim"
04-universal-patterns places multi-agent claims (itd-33) under .abcd/coordination/, beside a committed coordination append-log with daily UTC rotation. 27-implement keeps the claim that makes a record the unit of exclusion between concurrent sessions in the machine-scoped store, with its own per-UTC-day run log, and has the sessions write no repository file. Both documents claim the same ground, the exclusion record between concurrent agents, and give it incompatible homes.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 686.
Frontmatter
| id | iss-2610262036565450 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262036565450-multi-agent-claims-live-in-tree-under.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-261026203959075704-universal-patterns keeps multi-agent claims in `.abcd/coordination/` with local-only state; itd-2609091034175565 makes the reservation branch on origin the one record of who holds what.
- itd-33Multiple Agents Coordinate On Intent And Spec Work Without Duplicating Effort Or Producing Competing Artefacts