{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"what-is-receipt-is-proof","title":"What Is \"The Receipt Is the Proof\"","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is \"The Receipt Is the Proof\"**\n>\n> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is \"The Receipt Is the Proof\"\n\n## §SELF — what-is-receipt-is-proof\n\n**What this page is:** An explanation of OIP's foundational accountability principle.\n**What it explains:** Why the receipt is the sole proof that an action occurred, and how the system ensures this.\n**Why read it:** To understand how OIP establishes ground truth in a world of model-generated actions.\n\n### What \"The Receipt Is the Proof\" Means\n\n\"The receipt is the proof\" is the foundational principle of OIP's accountability model. It means: an action is proven only by the receipt — the immutable, verifiable, ledgered record of the invocation. Not by intent. Not by documentation. Not by a success status code from a server.\n\nThe receipt is the ground truth.\n\n### What a Receipt Contains\n\nA receipt contains six elements:\n\n1. **Who invoked what** — the entity (human or model) that initiated the action, and the operation that was called.\n2. **When** — the timestamp of the invocation, recorded at the time of execution.\n3. **With what authority** — the credentials or permissions that authorized the invocation.\n4. **What the result was** — the output of the operation, whether success, failure, or error.\n5. **Where to verify it** — a confirm URL that anyone can access to check the receipt's validity.\n6. **Links to related receipts** — bidirectional links to prior and subsequent invocations in the chain.\n\nAnyone can verify a receipt by opening its confirm URL. No secret key, no special access, no authentication is required. Verification is public.\n\n### How the Receipt System Works\n\nReceipts are append-only. Once a receipt is created, it is never edited. Never deleted. Never modified.\n\nIf an invocation was wrong — if it produced an incorrect result, used wrong parameters, or failed due to a bug — the system does not delete or alter the original receipt. Instead, it creates a repair receipt. The repair receipt is linked bidirectionally to the failed receipt: the failed receipt points to the repair, and the repair points back to the failed receipt.\n\nThe failed receipt remains part of the permanent record. The full history — every attempt, every failure, every repair — is preserved.\n\nThis is proof through persistence, not through perfection.\n\n### Why It Matters\n\nIn a system where models operate infrastructure, you need a way to prove what happened. Models can hallucinate (generate plausible but incorrect information), misremember (lose context or confuse similar events), or claim to have performed actions they did not perform.\n\nThe receipt is the arbiter between:\n\n- Human memory (which is fallible)\n- Model output (which is not guaranteed to correspond to system state)\n- Actual system state (which the receipt records)\n\nWhen a human says \"I told the model to do X\" and the model says \"I did X,\" the receipt determines whether X actually occurred, when it occurred, and what the result was.\n\n### What It Replaces\n\nTraditional systems use multiple incomplete proxies for proof:\n\n- **Intent:** \"I meant to deploy the service.\" Intent is not proof. Intent does not guarantee execution.\n- **Documentation:** \"The docs say the pipeline should run.\" Documentation describes intended behavior, not actual behavior.\n- **HTTP status codes:** \"The server returned 200 OK.\" A status code indicates the server accepted a request, not that the intended action occurred correctly.\n- **Logs:** Log entries are mutable. They can be altered, truncated, or lost. They are not designed for verification by third parties.\n\nThe receipt replaces all of these with a single, verifiable, immutable record.\n\n### Limitations\n\n- **Receipts prove invocation, not correctness.** A receipt proves that operation X was called with arguments Y at time Z. It does not prove that X was the right operation to call, or that Y were the right arguments. Human judgment is still required.\n- **Receipts depend on the ledger's integrity.** If the ledger itself is compromised, receipts may be forged or reordered. OIP mitigates this through distributed replication (Viewstamped Replication) and cryptographic chaining.\n- **Verification requires access.** The confirm URL must be accessible. If the ledger is offline or the URL is unreachable, verification fails even if the receipt is valid.\n- **Repairs create complexity.** A chain of repairs can become long and difficult to audit. The system preserves full history, but navigating that history requires tooling.\n\n### How It Connects to Other Ideas\n\n- **Double-entry bookkeeping:** In accounting, every transaction is recorded as a debit and a credit in separate accounts. Neither can be altered once recorded; errors are corrected with new entries. The receipt system follows the same principle: immutable records, correction through new entries.\n- **Blockchain:** A blockchain is an append-only ledger of transactions, verified by consensus among distributed participants. OIP's receipt ledger uses similar principles (append-only, verifiable, distributed) but is optimized for invocations rather than financial transfers.\n- **Event sourcing:** Event sourcing is a software architecture pattern where system state is derived from a log of immutable events, rather than stored directly. The receipt system is a form of event sourcing: the ledger of receipts is the source of truth, and system state is derived from it.\n- **The Actor Model:** In the Actor Model, actors communicate by sending messages. An invocation in OIP is a message to an actor (an OIP object). The receipt is the proof that the message was sent, processed, and produced a result. It closes the loop: message in, receipt out.\n\n### Sources\n\n- OIP Specification — Accountability Layer (receipt format and verification protocol)\n- Hewitt, C., Bishop, P., Steiger, R. \"A Universal Modular Actor Formalism for Artificial Intelligence.\" *IJCAI*, 1973. (Actor Model — message passing as fundamental operation)\n- Oki, B., Liskov, B. \"Viewstamped Replication.\" *PODC*, 1988. (Distributed ledger consensus)\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-receipt-is-proof`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-receipt-is-proof`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20%22The%20Receipt%20Is%20the%20Proof%22`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: philosophy must pass the same bar — no count or convergence without checkable source ([Count Discipline](/a/oip-count-discipline)).\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-receipt-is-proof","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-receipt-is-proof/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Protocol Concepts (oip-protocol-concepts). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":20,"label":"Protocol Concepts on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: philosophy must pass the same bar — no count or convergence without checkable source ([Count Discipline](/a/oip-count-discipline))."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:01.114Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"819510c294e1a099b7ece1784a9126e11183f51d402efa640e44e94cb0179918"},{"ts":"2026-07-15T06:24:50.478Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"819510c294e1a099b7ece1784a9126e11183f51d402efa640e44e94cb0179918","hash":"9aba0d11dc8ab0b696fd561df13b52d934049b98113713d9a06b5766f68d0345"},{"ts":"2026-07-17T02:43:39.338Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-receipt-is-proof","response":"42 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"9aba0d11dc8ab0b696fd561df13b52d934049b98113713d9a06b5766f68d0345","hash":"847f10dc6a3bedd36cf7d4dc6017f29a2aad35c32140247f233c8575e57bc8ef"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"847f10dc6a3bedd36cf7d4dc6017f29a2aad35c32140247f233c8575e57bc8ef"},"posted_at":"2026-07-15T04:21:01.114Z","created_at":"2026-07-15T04:21:01.114Z","updated_at":"2026-07-17T02:43:39.338Z","machine":{"shape":"article.machine/v1","slug":"what-is-receipt-is-proof","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-receipt-is-proof","json":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof","bundle":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-receipt-is-proof","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-receipt-is-proof\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-receipt-is-proof\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-receipt-is-proof/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"what-is-receipt-is-proof\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-receipt-is-proof | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-receipt-is-proof","json":"/api/articles/what-is-receipt-is-proof","markdown":"/api/articles/what-is-receipt-is-proof/bundle?format=markdown","skill":"/api/articles/what-is-receipt-is-proof/skill","topology":"/api/articles/what-is-receipt-is-proof/topology","versions":"/api/articles/what-is-receipt-is-proof/revisions","invocations":"/api/articles/what-is-receipt-is-proof/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-receipt-is-proof","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"06d288bfc2cac5d37b4bb01ca55c7db230c47c53ae5b2c6580ea967d982ef64b","object":{"object_type":"article-object","identity":{"id":"article:what-is-receipt-is-proof","slug":"what-is-receipt-is-proof","title":"What Is \"The Receipt Is the Proof\""},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/what-is-receipt-is-proof","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-receipt-is-proof/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-receipt-is-proof\ndescription: Apply the What Is \"The Receipt Is the Proof\" article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is \"The Receipt Is the Proof\"\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-receipt-is-proof). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-receipt-is-proof.\n- Read claims and relationships at /api/articles/what-is-receipt-is-proof/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\n<!-- hierarchy:nav -- Path: OIP https://miscsubjects.com/a/oip › Thinker Reference https://miscsubjects.com/a/oip-thinker-reference › Protocol Concepts https://miscsubjects.com/a/oip-protocol-concepts › What Is \"The Receipt Is the Proof\" Sh\n\n## Representations\n\n- Human: /a/what-is-receipt-is-proof\n- JSON: /api/articles/what-is-receipt-is-proof\n- Relationships: /api/articles/what-is-receipt-is-proof/topology\n- History: /api/articles/what-is-receipt-is-proof/revisions\n"},"json":{"route":"/api/articles/what-is-receipt-is-proof","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-receipt-is-proof/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","kimi-import","self-explaining","voxel","concepts","what-is-receipt-is-proof","objection-7","oip-edge","what","is","receipt","is","proof"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-receipt-is-proof/invocations?status=success","failure_events":"/api/articles/what-is-receipt-is-proof/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"what-is-receipt-is-proof","title":"What Is \"The Receipt Is the Proof\"","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is \"The Receipt Is the Proof\"**\n>\n> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is \"The Receipt Is the Proof\"\n\n## §SELF — what-is-receipt-is-proof\n\n**What this page is:** An explanation of OIP's foundational accountability principle.\n**What it explains:** Why the receipt is the sole proof that an action occurred, and how the system ensures this.\n**Why read it:** To understand how OIP establishes ground truth in a world of model-generated actions.\n\n### What \"The Receipt Is the Proof\" Means\n\n\"The receipt is the proof\" is the foundational principle of OIP's accountability model. It means: an action is proven only by the receipt — the immutable, verifiable, ledgered record of the invocation. Not by intent. Not by documentation. Not by a success status code from a server.\n\nThe receipt is the ground truth.\n\n### What a Receipt Contains\n\nA receipt contains six elements:\n\n1. **Who invoked what** — the entity (human or model) that initiated the action, and the operation that was called.\n2. **When** — the timestamp of the invocation, recorded at the time of execution.\n3. **With what authority** — the credentials or permissions that authorized the invocation.\n4. **What the result was** — the output of the operation, whether success, failure, or error.\n5. **Where to verify it** — a confirm URL that anyone can access to check the receipt's validity.\n6. **Links to related receipts** — bidirectional links to prior and subsequent invocations in the chain.\n\nAnyone can verify a receipt by opening its confirm URL. No secret key, no special access, no authentication is required. Verification is public.\n\n### How the Receipt System Works\n\nReceipts are append-only. Once a receipt is created, it is never edited. Never deleted. Never modified.\n\nIf an invocation was wrong — if it produced an incorrect result, used wrong parameters, or failed due to a bug — the system does not delete or alter the original receipt. Instead, it creates a repair receipt. The repair receipt is linked bidirectionally to the failed receipt: the failed receipt points to the repair, and the repair points back to the failed receipt.\n\nThe failed receipt remains part of the permanent record. The full history — every attempt, every failure, every repair — is preserved.\n\nThis is proof through persistence, not through perfection.\n\n### Why It Matters\n\nIn a system where models operate infrastructure, you need a way to prove what happened. Models can hallucinate (generate plausible but incorrect information), misremember (lose context or confuse similar events), or claim to have performed actions they did not perform.\n\nThe receipt is the arbiter between:\n\n- Human memory (which is fallible)\n- Model output (which is not guaranteed to correspond to system state)\n- Actual system state (which the receipt records)\n\nWhen a human says \"I told the model to do X\" and the model says \"I did X,\" the receipt determines whether X actually occurred, when it occurred, and what the result was.\n\n### What It Replaces\n\nTraditional systems use multiple incomplete proxies for proof:\n\n- **Intent:** \"I meant to deploy the service.\" Intent is not proof. Intent does not guarantee execution.\n- **Documentation:** \"The docs say the pipeline should run.\" Documentation describes intended behavior, not actual behavior.\n- **HTTP status codes:** \"The server returned 200 OK.\" A status code indicates the server accepted a request, not that the intended action occurred correctly.\n- **Logs:** Log entries are mutable. They can be altered, truncated, or lost. They are not designed for verification by third parties.\n\nThe receipt replaces all of these with a single, verifiable, immutable record.\n\n### Limitations\n\n- **Receipts prove invocation, not correctness.** A receipt proves that operation X was called with arguments Y at time Z. It does not prove that X was the right operation to call, or that Y were the right arguments. Human judgment is still required.\n- **Receipts depend on the ledger's integrity.** If the ledger itself is compromised, receipts may be forged or reordered. OIP mitigates this through distributed replication (Viewstamped Replication) and cryptographic chaining.\n- **Verification requires access.** The confirm URL must be accessible. If the ledger is offline or the URL is unreachable, verification fails even if the receipt is valid.\n- **Repairs create complexity.** A chain of repairs can become long and difficult to audit. The system preserves full history, but navigating that history requires tooling.\n\n### How It Connects to Other Ideas\n\n- **Double-entry bookkeeping:** In accounting, every transaction is recorded as a debit and a credit in separate accounts. Neither can be altered once recorded; errors are corrected with new entries. The receipt system follows the same principle: immutable records, correction through new entries.\n- **Blockchain:** A blockchain is an append-only ledger of transactions, verified by consensus among distributed participants. OIP's receipt ledger uses similar principles (append-only, verifiable, distributed) but is optimized for invocations rather than financial transfers.\n- **Event sourcing:** Event sourcing is a software architecture pattern where system state is derived from a log of immutable events, rather than stored directly. The receipt system is a form of event sourcing: the ledger of receipts is the source of truth, and system state is derived from it.\n- **The Actor Model:** In the Actor Model, actors communicate by sending messages. An invocation in OIP is a message to an actor (an OIP object). The receipt is the proof that the message was sent, processed, and produced a result. It closes the loop: message in, receipt out.\n\n### Sources\n\n- OIP Specification — Accountability Layer (receipt format and verification protocol)\n- Hewitt, C., Bishop, P., Steiger, R. \"A Universal Modular Actor Formalism for Artificial Intelligence.\" *IJCAI*, 1973. (Actor Model — message passing as fundamental operation)\n- Oki, B., Liskov, B. \"Viewstamped Replication.\" *PODC*, 1988. (Distributed ledger consensus)\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Convergence Catalogue](https://miscsubjects.com/a/what-is-convergence-catalogue)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-receipt-is-proof`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-receipt-is-proof`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20%22The%20Receipt%20Is%20the%20Proof%22`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: philosophy must pass the same bar — no count or convergence without checkable source ([Count Discipline](/a/oip-count-discipline)).\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-receipt-is-proof","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-receipt-is-proof/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Protocol Concepts (oip-protocol-concepts). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":20,"label":"Protocol Concepts on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: philosophy must pass the same bar — no count or convergence without checkable source ([Count Discipline](/a/oip-count-discipline))."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:01.114Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"819510c294e1a099b7ece1784a9126e11183f51d402efa640e44e94cb0179918"},{"ts":"2026-07-15T06:24:50.478Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"819510c294e1a099b7ece1784a9126e11183f51d402efa640e44e94cb0179918","hash":"9aba0d11dc8ab0b696fd561df13b52d934049b98113713d9a06b5766f68d0345"},{"ts":"2026-07-17T02:43:39.338Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-receipt-is-proof","response":"42 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"9aba0d11dc8ab0b696fd561df13b52d934049b98113713d9a06b5766f68d0345","hash":"847f10dc6a3bedd36cf7d4dc6017f29a2aad35c32140247f233c8575e57bc8ef"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"847f10dc6a3bedd36cf7d4dc6017f29a2aad35c32140247f233c8575e57bc8ef"},"posted_at":"2026-07-15T04:21:01.114Z","created_at":"2026-07-15T04:21:01.114Z","updated_at":"2026-07-17T02:43:39.338Z","machine":{"shape":"article.machine/v1","slug":"what-is-receipt-is-proof","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-receipt-is-proof","json":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof","bundle":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-receipt-is-proof","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-receipt-is-proof\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-receipt-is-proof\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-receipt-is-proof/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"what-is-receipt-is-proof\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-receipt-is-proof | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-receipt-is-proof","json":"/api/articles/what-is-receipt-is-proof","markdown":"/api/articles/what-is-receipt-is-proof/bundle?format=markdown","skill":"/api/articles/what-is-receipt-is-proof/skill","topology":"/api/articles/what-is-receipt-is-proof/topology","versions":"/api/articles/what-is-receipt-is-proof/revisions","invocations":"/api/articles/what-is-receipt-is-proof/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-receipt-is-proof","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"06d288bfc2cac5d37b4bb01ca55c7db230c47c53ae5b2c6580ea967d982ef64b"}}}