Development record
itd-2610170634394993 puts agents' work claims on the shared remote; 04-universal-patterns puts multi-agent claims in .abcd/coordination/
itd-2610170634394993 puts agents' work claims on the shared remote; 04-universal-patterns puts multi-agent claims in .abcd/coordination/
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2610170634394993-several-headless-agents-work-one.md:22— "Each agent takes a piece of work by a claim on the shared remote" - End B:
.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/"
The headless-agents intent has each agent take work by a claim on the shared remote, on the stance that coordination lives there. 04-universal-patterns puts multi-agent claims at .abcd/coordination/ in the checkout, with a committed append-log beside local lock files. The two documents give the same claims two incompatible homes.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 837.
Frontmatter
| id | iss-2610262039043469 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262039043469-itd-2610170634394993-puts-agents-work.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610170634394993Headless agents in parallel coordinate through the shared remote, not conversationrelated
mentions1
- itd-33Multiple Agents Coordinate On Intent And Spec Work Without Duplicating Effort Or Producing Competing Artefacts