One exact action. One portable identifier.
Change what matters and the identifier changes. Keep the exact typed action, and any conforming system can recompute the same canactid: value.
Move one material fact. Watch the match break.
The approved record below is an $82,000 payment to Acme. Compare it unchanged, then change the amount or destination. The page uses the repository's reference implementation and active payment.release.1 definition.
Matches the approved action
The exact typed content recomputes to the same identifier.
canactid:1:payment.release.1:jcs-sha256:8kT37VvytPPqTDLdG0cBjPcW-407E3IkfymTyP0sv5Ecanactid:1:payment.release.1:jcs-sha256:8kT37VvytPPqTDLdG0cBjPcW-407E3IkfymTyP0sv5ESee the typed action used for this identifier
{
"action_type": "payment.release.1",
"amount": "82000.00",
"currency": "USD",
"beneficiary_account": "sha256:3c9d6b8dbbdd0bc9d7aed0e1b1309d9dfb023c3d45c31828a44b097b1e341cc7",
"payment_instruction_id": "pi-demo-1042"
}It tells systems what action they are talking about.
CAID is content correlation. It gives independently produced records a precise way to refer to the same material action without making a bigger claim.
- It does not authorize an action. Authority still comes from the relying party's policy and evidence.
- It does not prove execution. The executor must report the outcome separately.
- It does not prevent replay. Use an operation ID, nonce, and atomic consumption for that.
- It is not an idempotency key. Identical action content may legitimately occur more than once.
- It is not a URL to fetch. A
canactid:URI is not dereferenceable.
A registered name, with a deliberately narrow claim.
The canactid URI scheme is provisionally registered in IANA's URI Schemes registry and references CAID-05. CAID remains an individual Internet-Draft. The registration is not IETF adoption, endorsement, or permanent status.