- What is proof-carrying action?
- What should an AI action carry before it is trusted?
- What is an action receipt?
- How does this prevent authority leaks?
What does the action carry?
Claim, proof, authority, scope, refusal route, and receipt fields.
Concept / Proof-Carrying Action
This page explains the concept without assuming the reader already knows the internal papers.
Search Intent
Concept
A high-risk action is not just an output. It should carry a warrant: what claim supports it, what authority allows it, what evidence bounds it, and what receipt closes it.
If those fields are missing, the action should be refused, downgraded, or routed to review.
Receipt
A receipt records what happened, under which authority, with which evidence and boundary.
Without a receipt, a team may not be able to distinguish suggestion, approval, execution, and later justification.
Evidence Route
This page is an entry point. The claim should be evaluated through DOI records, evidence maps, registries, GitHub/HF technical routes, and public counterexamples.
Boundary
Claim, proof, authority, scope, refusal route, and receipt fields.
Logging can be passive; proof-carrying action requires permission evidence before high-risk action is credited or allowed.
Find an action claim where authority, evidence, or receipt closure is missing.