A — Tool-call binding
The grant binds the canonical tool-call bytes, so what-was-called equals what-was-authorized — closing prompt-injection and argument-drift. Not available.
CodeRifts · claim table · two blocks, never mixed
What is a gate today, and what is only direction
The left block is enforced today. The right block is the roadmap — planned or on request, never available. They are not one table. A roadmap row is not a proof.
The done gate is exactly grant + consume + target-state + offline-verify. Roadmap items (tool-call binding, the evidence bundle, delegation attenuation, the TRACE bridge) are listed so they cannot be read as shipping.
Enforced today
Done · enforcedFail-closed authorization-execution gate
One grant binds authorize → consume → target-state transition → offline readback. Without the receipt the mutator does not run. Verifiable offline. No provider-witness. No TEE.
Without this receipt the check is red. That is the product.
This is what VERIFY.md proves on a stranger’s machine, and what the published packages enforce.
Public chain: @coderifts/prove@0.1.9 · @coderifts/conformance@0.8.6 · coderifts-sdk 3.7.0 · coderifts 8.6.0
Replay: npx @coderifts/conformance@0.8.6 --assurance END_TO_END
Roadmap (planned / on-request)
None of these rows is available. None carries a proof claim. Direction only.
F — Cross-domain evidence bundle
One hash over grant + measurement + supply-chain, so those three domains are a single evidence object. Not available.
C — Agent-to-agent delegation attenuation
A downstream agent receives a strictly narrower grant than the caller held. Not available.
TRACE bridge
Authorized-intent equals the CodeRifts receipt-digest, so a TRACE-shaped intent can be checked against the same receipt. Intent / on request. Not available.