Development record
The announce intent says a reservation records who owns an item, but universal patterns puts multi-agent claims in `.abcd/coordination/`
The announce intent says a reservation records who owns an item, but universal patterns puts multi-agent claims in .abcd/coordination/
A scope leakage (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2609151838312703-sessions-announce-what-they-are-doing.md:91— "who owns an item is its reservation" - End B:
.abcd/development/brief/05-internals/04-universal-patterns.md:139— "multi-agent claims per itd-33) lives at.abcd/coordination/"
itd-2609151838312703 rules that who owns an item is its reservation on the shared remote, and that a release hold is a reservation too. 04-universal-patterns says coordination state, including multi-agent claims per itd-33, lives at .abcd/coordination/ inside the repository. Ownership of an item is placed in two stores with different reach, and neither document says which one a session reads.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 858.
Frontmatter
| id | iss-2610262039259706 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262039259706-the-announce-intent-says-a-reservation.md
open on GitHub ↗ · commit history ↗
References1
- 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 reservationrelated
mentions1
- itd-33Multiple Agents Coordinate On Intent And Spec Work Without Duplicating Effort Or Producing Competing Artefacts