{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_bundle","feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","contains":"body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest","slug":"what-is-receipt","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt/bundle?format=markdown"},"how_to_use":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","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/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":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt/topology"}},{"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/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"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/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"claim_post","name":"Claim post protocol","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"llm_manifest","name":"LLM manifest","what":"Machine-readable read/write contract for external LLMs.","urls":{"read":"https://miscsubjects.com/api/articles/llm-manifest"}}],"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":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","why":"Every feature is auditable collective intelligence","how":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/what-is-receipt/bundle?format=markdown"},"imessage":null,"router":null,"related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."},{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"claim_post","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by."},{"id":"llm_manifest","what":"Machine-readable read/write contract for external LLMs."}],"not_medical_advice":true},"bundle_version":1,"generated_at":"2026-07-15T06:13:01.941Z","slug":"what-is-receipt","title":"What Is a Receipt","url":"https://miscsubjects.com/a/what-is-receipt","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-receipt"],"posted_at":"2026-07-15T04:21:02.436Z","updated_at":"2026-07-15T04:21:02.436Z","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 a Receipt**\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 a Receipt\n\n## §SELF — what-is-receipt\n\n**What this page is:** A definition of a receipt as a technical object in protocol design.\n**What it explains:** What a receipt contains, what properties it has, and why it is the fundamental unit of proof in OIP.\n**Why read it:** To understand how to prove that an action happened — not with a log entry or a status code, but with a self-contained, verifiable, immutable record.\n\n### What a Receipt Is\n\nIn protocol design, a receipt is a proof that an action was performed. It is not a log entry (a chronological record of events). It is not an audit trail (a history of who accessed what). It is a self-contained, verifiable, immutable record of a single invocation — one specific call to one specific function with one specific result.\n\nA receipt is created at the moment an invocation completes. It cannot be changed afterward. If the invocation was wrong, a new receipt is created to correct it. The original receipt remains.\n\n### Why It Matters\n\nIn most systems, \"proof that something happened\" means a log line in a database, a 200 HTTP status code, or an entry in an audit trail. These are not proof. A log line can be deleted. A status code is ephemeral — it exists only in the response and is not stored. An audit trail tracks access, not action.\n\nA receipt fixes this. It is a cryptographic object: it has hashes, signatures, and unique identifiers. It can be verified by anyone with access to the confirm URL. It can be replayed (run again to check the result). It can be repaired (superseded by a corrected invocation, with both receipts linked). The receipt is the only object that proves an action occurred. Everything else is a signal, a record, or a claim — not proof.\n\n### The Key Idea\n\nThe central concept is **proof through immutability and linkage.** A receipt proves an action happened because:\n\n1. It was created at the moment of the action (it is contemporaneous).\n2. It contains hashes of the input and output (tampering is detectable).\n3. It is stored immutably (it cannot be altered after creation).\n4. It is linked to related receipts (parent invocations, repairs, replays form a chain).\n\nErrors are not corrected by editing. They are corrected by creating a new receipt that references the old one. The history of corrections is itself a provable chain.\n\n### What a Receipt Contains\n\nA receipt has four sections:\n\n**Identity:**\n- `invocation_id` — a unique identifier for this specific invocation (UUID, never reused).\n- `timestamp` — when the invocation completed.\n- `actor` — who invoked the action (a principal identifier).\n- `credential_scope` — what authority the actor was exercising (which credentials they presented).\n\n**Object:**\n- `object_key` — what was invoked (the function or operation).\n- `object_version` — which version of the function was used.\n- `input_hash` — the cryptographic hash of the input parameters.\n- `input_body` — the actual input parameters (optional if the hash is sufficient).\n\n**Result:**\n- `runner` — what executed the invocation (the compute environment or service).\n- `status` — the outcome: `success` or `failure`.\n- `output_hash` — the cryptographic hash of the output.\n- `artifact_urls` — links to any files produced by the invocation.\n\n**Lineage:**\n- `error` — if the status is `failure`, the error details.\n- `ledger_url` — the canonical location where this receipt is stored.\n- `confirm_url` — a public URL where anyone can verify this receipt exists.\n- `replay_url` — a URL that reruns the same invocation, producing a new receipt.\n- `repair_url` — a URL to create a corrected invocation if this one failed.\n- `parent_invocation_id` — if this invocation was delegated from another, the parent's ID.\n- `repair_of_invocation_id` — if this receipt corrects a failed one, the failed receipt's ID.\n\n### Properties of a Receipt\n\n**Immutable:** Once created, a receipt is never changed. If an invocation produced the wrong result, a repair receipt is created. The original receipt remains, linked to the repair via `repair_of_invocation_id`. This preserves a complete, auditable history of what happened and what was done about it.\n\n**Verifiable:** Anyone can confirm a receipt exists by checking its `confirm_url`. No secret key, no special access, no database query is required. Verification is a public operation.\n\n**Replayable:** The same invocation can be run again from the receipt. The `replay_url` reruns the same `object_key` with the same `input_body`. The new receipt is linked to the original via `parent_invocation_id`. This lets you check whether the same inputs produce the same outputs.\n\n**Repairable:** A failed invocation is not deleted or edited. A new invocation is created with a link back to the failed receipt via `repair_of_invocation_id`. The failed receipt's `repair_url` points forward to the correction. The linkage is bidirectional.\n\n### How It Connects to Other Ideas\n\n- **Blockchain transactions:** A blockchain transaction is a proof that a transfer occurred. Like a receipt, it is immutable, verifiable, and linked (to previous blocks). Unlike a receipt, a blockchain transaction is typically public, permanent, and does not have a built-in repair mechanism. Receipts are more flexible: they can be private, scoped to a specific ledger, and explicitly repairable.\n- **Merkle trees:** A collection of receipts can be organized into a Merkle tree. The root hash of the tree commits to all receipts. A single receipt can be proven to be in the tree with a Merkle proof — the receipt plus a logarithmic number of sibling hashes. This is how BitTorrent verifies file pieces and how OIP can prove receipt inclusion without revealing the whole ledger.\n- **Event sourcing:** In event-sourced systems, state is derived from a log of events. A receipt is similar to an event, but it is self-proving (hashes, confirm URLs) and explicitly linked to related events (parent, repair, replay). Event sourcing typically does not include cryptographic verification or public confirmation.\n- **OIP's §SELF block:** The §SELF block is a form of receipt — it is a self-contained description of an article that can be verified against the article's content. The conformance test suite generates receipts (pass/fail records with hashes of expected vs. actual output). The voxel graph links receipts into a dependency structure.\n\n### Sources\n\n- OIP Protocol Specification: Receipt Format (v1).\n- OIP Protocol Specification: Invocation Lifecycle (v1).\n- OIP Protocol Specification: Ledger and Confirmation (v1).\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`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-receipt`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Receipt`\n","claims":[],"sources":[],"voxels":{"slug":"what-is-receipt","counts":{"voxels":0,"sources":0,"edges":0},"note":"slim bundle — full voxels at /api/articles/what-is-receipt/voxels"},"constitution":{"url":"https://miscsubjects.com/api/articles/constitution"},"provenance":[{"action":"write","model":"kimi-agent-import","ts":"2026-07-15T04:21:02.436Z","hash":"f15264852a78c5c8","tokens_in":0,"tokens_out":0}],"contributions":[],"topology":null,"slim":true,"ledger_totals":{"claims":0,"sources":0,"exported_claims":0,"exported_sources":0},"question_graph":{"slug":"what-is-receipt","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"verification":{"provenance":{"valid":true,"entries":1,"head":"f15264852a78c5c84251bfe30c48a107789af25afa0ebbbebad827cd6e77c6d4"},"sources":{"valid":true,"entries":0,"head":"genesis"}},"counts":{"claims":0,"sources":0,"provenance":1,"contributions":0,"questions":0,"evidence_ingests":0,"voxel_edges":0},"transport":"Open every URL in this bundle with your browser or web / URL-fetch tool. Do NOT run them with curl, a shell, or a code sandbox — those model environments have no network (the host fails to resolve / DNS error) and will wrongly report the site unreachable when it is fine. Opening the link IS the call.","llm_manifest":{"version":"1","site":"https://miscsubjects.com","purpose":"Peptide evidence articles with hash-chained source ledgers, tiered claims, and a question graph. LLMs should READ bundles/URLs and WRITE back via ingest — never invent doses.","read":{"human_page":"https://miscsubjects.com/a/what-is-receipt","bundle_json":"https://miscsubjects.com/api/articles/what-is-receipt/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/what-is-receipt/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/what-is-receipt/topology","question_graph":"https://miscsubjects.com/api/articles/what-is-receipt/question-graph","sources":"https://miscsubjects.com/api/articles/what-is-receipt/sources","provenance":"https://miscsubjects.com/api/articles/what-is-receipt/provenance","contributions":"https://miscsubjects.com/api/articles/what-is-receipt/contributions","graph_topology":"https://miscsubjects.com/api/articles/what-is-receipt/graph-topology?question={question}","voxels":"https://miscsubjects.com/api/articles/what-is-receipt/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","health":"https://miscsubjects.com/api/articles/what-is-receipt/health","repair":"POST https://miscsubjects.com/api/protocol/repair","list_articles":"https://miscsubjects.com/api/articles","graph_canvas":"https://miscsubjects.com/graph.html?slugs=what-is-receipt","graph_yield":"https://miscsubjects.com/api/graph?slugs=what-is-receipt&layer=yield","obsidian_vault":"https://miscsubjects.com/api/articles/obsidian-vault?slugs=what-is-receipt","graph_query":"https://miscsubjects.com/api/v1/query?from=what-is-receipt&kind=claim&where=tier=human"},"ask":{"description":"Answer only from topology; creates a question_node with gaps.","api":"POST https://miscsubjects.com/api/protocol/ask","body":{"slug":"{slug}","question":"string"},"imessage":"what-is-receipt|your question","router_tag":"[ARTICLE_ASK]what-is-receipt|question[/ARTICLE_ASK]","auth":"x-terminal-key header for API; iMessage/WhatsApp via miscsubjects build"},"ingest":{"description":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","api":"POST https://miscsubjects.com/api/protocol/ingest","body":{"slug":"{slug}","evidence":"paste text","question_node_id":"optional qn_..."},"imessage":"ingest what-is-receipt|q:{node_id}|paste evidence","router_tag":"[ARTICLE_INGEST]what-is-receipt|evidence[/ARTICLE_INGEST]","tiers":["human","preclinical","anecdotal","mechanistic","speculative"]},"claim":{"description":"Prompt-injection style POST — one claim voxel with who_claims + posted_by provenance.","api":"POST https://miscsubjects.com/api/protocol/claim","body":{"slug":"{slug}","text":"one assertion","tier":"human|preclinical|anecdotal|mechanistic|speculative","who_claims":"study author, platform, or model id","source_ids":"optional [s1]"},"imessage":"claim what-is-receipt|tier|assertion — who claims it?","router_tag":"[ARTICLE_CLAIM]what-is-receipt|tier|assertion[/ARTICLE_CLAIM]","slots":["what_it_is","who_claims_what","what_is_known","what_is_unknown","mechanism","limitations","disclaimer"]},"tiers":{"human":0.8,"preclinical":0.5,"anecdotal":0.3,"mechanistic":0.3,"speculative":0.1},"invariants":["Self-explaining — every API JSON has _self; every paste widget has §SELF; root index at /api/articles/system-map","Append-only — revisions preserved at ?rev=n","Source chain verifies integrity, not truth","Answers must cite claim ids and source ids from topology","Not medical advice"],"constitution":{"version":1,"principle":"Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.","slots":[{"id":"what_it_is","required":true,"answers":"What is this peptide/stack/condition?"},{"id":"who_claims_what","required":true,"answers":"Who claims what — study authors, platforms, n=?"},{"id":"what_is_known","required":true,"answers":"What is known with tier labels (human/preclinical/anecdotal)"},{"id":"what_is_unknown","required":true,"answers":"What is NOT known — explicit gaps"},{"id":"mechanism","required":false,"answers":"Proposed mechanism (mechanistic tier only)"},{"id":"limitations","required":true,"answers":"Limits of evidence — no dose advice"},{"id":"disclaimer","required":true,"answers":"Not medical advice"}],"claim_rules":["One claim = one falsifiable assertion. No compound claims.","Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative|system.","system tier = architecture/design axioms (not biological mechanism). Use for protocol self-definition.","Sourced claims must cite source_ids from the hash-chained ledger.","Unsourced claims must set source_status: unsourced and why_material.","posted_by is mandatory on every new claim (model id, human, or channel).","No medical advice, no doses, no 'you should take'.","Bad information is retracted (status:retracted), never deleted — retraction event stays on ledger.","Adversary challenges link via challenges[] / challenged_by[] — target may be downweighted.","Leaked secrets are scrubbed to [REDACTED:secret-leak] with scrub_events tombstone — honest audit trail."],"source_rules":["Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.","Sources hash-chain — prev/hash on append.","Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry)."],"ontology_rules":["Peptide articles (bpc-157, tb-500) are tree roots.","Condition articles (bpc-157-glp1-gut-damage) branch from peptides.","Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.","If an article has no parent embeds and is not a root peptide → sprawl candidate.","Misstep = duplicate scope with another slug; merge or reparent via embeds."],"post_protocol":{"claim":"POST /api/protocol/claim","source":"POST /api/protocol/sources","ingest":"POST /api/protocol/ingest","webhook":"POST /api/articles/<slug>/webhook {kind:claim|source}","imessage_claim":"claim {slug}|{tier}|your assertion — who claims it, source?","imessage_ingest":"ingest {slug}|evidence paste"}},"this_article":{"slug":"what-is-receipt","url":"https://miscsubjects.com/a/what-is-receipt","bundle_url":"https://miscsubjects.com/api/articles/what-is-receipt/bundle?format=markdown"}},"api_urls":{"bundle":"https://miscsubjects.com/api/articles/what-is-receipt/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/what-is-receipt/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/what-is-receipt/topology","voxels":"https://miscsubjects.com/api/articles/what-is-receipt/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","question_graph":"https://miscsubjects.com/api/articles/what-is-receipt/question-graph","ask":"https://miscsubjects.com/api/protocol/ask","ingest":"https://miscsubjects.com/api/protocol/ingest","claim":"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"}}