Velaru Standards · Counterfactual Evidence · v1.0
IETF draft-noa-scitt-ai-agent-receipt-00 leaves policy-replay out of scope. TCB fills that gap: a Counterfactual Receipt (CCR) cryptographically bound to a frozen Handler Receipt, answering what would have happened under the committed policy.
A CCR attests that a specific represented path was available within the observation boundary, cryptographically sealed, and not selected as the final path — enabling audit of rejected alternatives in EPL and carrier disputes.
POST https://velaru.onrender.com/tcb/counterfactual-replay
Content-Type: application/json
{
"entry_id": "SOURCE_RECEIPT_HASH",
"session_id": "pilot-1"
}
→ 200 { "ccr_id", "causal_binding_hash", "counterfactual_reply",
"handler_receipt_id", "verify_url", "signature" }
GET https://velaru.onrender.com/tcb/ccr/{ccr_id}/verify.json
→ portable CCR receipt for /verify
draft-noa-scitt-ai-agent-receipt leaves policy-replay out of scope (§9). TCB is the companion profile for offline counterfactual binding under a frozen Handler Receipt.
/verify runs CHECK 9 — TCB CAUSAL BINDING when bound_ccr_id or CCR receipt type is present. Recomputes causal_binding_hash from source + handler + digest.