This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

04-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.

issuewontfixminoriss-2610262039590757

04-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.

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 like shape.lock, multi-agent claims per itd-33) lives at .abcd/coordination/"
  • End B: .abcd/development/intents/shipped/itd-2609091034175565-nothing-tells-an-agent-that-a-record-it.md:211 — "nothing kept only on one computer (the local tier, a note on the desktop, same-account messaging) is the source of truth for who holds what."

04-universal-patterns says coordination state, including multi-agent claims under itd-33, lives at .abcd/coordination/, with active-work.json and the locks kept local and gitignored. itd-2609091034175565 rules that nothing kept on one computer, the local tier included, decides who holds what, and that the reservation branch is the only transport. Both documents say where agent claims live, and they put them in different places.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 901.

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262036565450. Same End A; itd-33 was superseded by the shipped reservation-branch intent that this record cites as End B.

Frontmatter

idiss-2610262039590757
typeissue
lifecyclewontfix
severityminor

References1

mentions3