Docs Collaboration
Conflict Radar
Surface overlaps between teammates at the moment of overlap, not at the moment of merge.
Conflict Radar is the feature that turns the attestation stream into team coordination. The local daemon subscribes to the org's channel. The moment a teammate attests work touching files you currently have open, a notification fires — before either of you has pushed.
Severity model
| Severity | Trigger | Action |
|---|---|---|
| HIGH | Same file, overlapping regions within the last 15 minutes. | OS-level notification + IDE badge + panel. |
| MEDIUM | Same file, non-overlapping regions, same short timeframe. | IDE badge + panel entry. |
| LOW | Sibling files or shared imports, wider timeframe. | Panel entry only. Never interrupts. |
Privacy, by design
- The radar works on metadata — file paths, predicates, identities, timestamps. It does not read source, keystrokes, cursor positions or time-on-file.
- Overlaps are symmetric. If you see a teammate, they see you. There is no manager's view of the developer's screen.
- Every developer can opt out per repo. Opt-out is silent to peers by design.
- The radar surfaces warnings, never blocks. Blocking is the policy contract's job, and it runs server-side on the ledger, not on peer gossip.