release-claim

/release-claim — Multi-Operator Claim Release

Release a claim from the coordination log. Two modes:

• Self-release — operator releases their own claim. Writes a signed release record.
• Cross-operator reap (--reap … --cosigner …) — releases a STALE claim held by a SIBLING. Requires the §4.4 reap ceremony (distinct-person_id cosigner + pinned victim heartbeat past LIVENESS_TTL_MS).

Usage

/release-claim <claim-ref>
/release-claim --reap <other-claim-ref> --cosigner <person_id>

• <claim-ref> — either <verified_id>:<seq> (canonical) OR the claim_id from /claims output.
• --reap — explicit dispatch to the cross-operator reap ceremony. The <other-claim-ref> MUST point at a stale sibling claim (verified_id != self).
• --cosigner <person_id> — required on --reap; the person_id of a distinct, eligible cosigner per .claude/hooks/lib/eligibility.js::isEligibleSigner("gate-approval") (R5-S-04: CI hosts BLOCKED).

Self-release flow

1. Parse <claim-ref> — resolve to (verified_id, seq). If passed as claim_id, look up the matching claim record in the folded accepted set.
2. Resolve identity via operator-id.js::resolveIdentity(cwd).
3. Bind check — the resolved claim's verified_id MUST equal the current operator's verified_id. If they differ, halt-and-report:

   Cross-operator claim release attempted via self-release.
   Use the reap ceremony for stale sibling claims:
     /release-claim --reap <other-claim-ref> --cosigner <person_id>
   

   Direct the user to /claims to see the stale claim's current display_id and a candidate cosigner.
4. Build release record:

   {
     type: "release",
     verified_id, person_id, display_id, seq, prev_hash, ts,
     content: {
       claim_id: <released claim_id>,
       released_claim_ref: { verified_id, seq },
       reason: "self-release",
     },
     sig
   }
   

5. Sign + append via filesystem Transport appendRecord. Print confirmation.