{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"what-is-receipt-is-proof","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt-is-proof/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"what-is-receipt-is-proof","title":"What Is \"The Receipt Is the Proof\"","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-receipt-is-proof"],"updated_at":"2026-07-15T04:21:01.114Z","body_excerpt":"<!-- 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","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"what-is-receipt-is-proof","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":0,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}