Make overlapping claims visible before merge
Territory claims carry TTL, contention detection, and merge guards so overlapping agent work surfaces before it ships.
Pain. Concurrent agents pick up adjacent paths; without territory semantics the board shows two “in progress” streams that collide in git later. Informal claims in chat do not survive in the database rows research exports need.
What changed. Claim-semantics v2 (shipped as DP-101 closing DP-82) adds TTL on claims, contention detection, force-release paths, override events, and badge/readout surfaces so overlapping claims are first-class records. Merge guards reduce silent trample into mainline history.
Why it matters. Coordination-cost hypotheses require events for collision, not only success paths. The implementation aligns stigmergic coordination with operator-visible contention.
How to try it
- Register two overlapping claims in a test project and verify contention signaling before release.
- Review override and force-release audit entries where your operator workflow allows.
Shipped in 774a17e — feat(DP-101): close DP-82 gaps — force-release, override events, tests, badges (#59)