Add HRC-001 Handoff Reachability & Causal Basis - #262
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Exact-head executable evidenceCanonical HRC-001 conformance is green on the current PR head: CI: The log explicitly exercises both distinct stale-transition classes: and the live reachability boundary: RESONANCE Article 12: Evidence / non-claims: Executable proof addendum: The upstream low-concurrency non-reproduction of the proposed CAS-race class remains a preserved negative observation. This PR does not rewrite it into a confirmed production race. |
What changed
Introduces HRC-001 — Handoff Reachability & Causal Basis, a framework-neutral executable contract for multi-agent status transitions and handoffs.
Core separation
HRC-001 keeps four facts distinct:
Load-bearing invariants:
Executable behavior
The reference evaluator distinguishes:
Handoffs are two-phase. The current owner remains authoritative while reachability is checked. A reachable target makes the handoff deliverable, but ownership advances only after the target acknowledges the exact handoff event, target ownership epoch and predecessor.
Evidence origin
The motivating Claude Code #24798 discussion produced an intentionally asymmetric result:
The contract preserves that distinction instead of turning the non-reproduction into either a universal safety claim or a universal race claim.
Conformance
Adds four JSON Schemas, a reference evaluator, and a 24-test falsification suite covering ownership epochs, causal basis, true CAS conflicts, surfaced reachability, expiry/unavailability, two-phase handoff and exact recipient acknowledgement.
Scope / non-claims
This is a bounded reference/conformance model. It does not claim watcher processes are the only valid reachability primitive, that READY guarantees successful delivery, that an observation cursor is truthful without trusted read evidence, that CAS races are universal, or that Anthropic/Claude Code has adopted the model.