{"_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-replay-repair","title":"What Is Replay and Repair","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 Replay and Repair**\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 Replay and Repair\n\n## §SELF — what-is-replay-repair\n\n**What this page is:** A definition of two mechanisms for handling and correcting invocation results in a ledger-based system.\n**What it explains:** How replay re-runs past invocations for verification, and how repair creates linked corrections without erasing errors.\n**Why read it:** To understand why appending corrections (rather than overwriting errors) creates an auditable history of what happened and what was fixed.\n\n### What Replay and Repair Are\n\nReplay and repair are two operations on an invocation ledger. A ledger is an append-only record: every invocation is stored as a receipt that cannot be changed or deleted. Replay and repair are the two ways to handle a receipt after it has been created.\n\n**Replay** means re-running a recorded invocation. You send a receipt ID to a replay endpoint. The system runs the same object with the same input again, producing a new receipt. The new receipt links back to the original. You now have two receipts for the same operation. You can compare them.\n\n**Repair** means creating a corrected invocation linked to a failed one. You send a new invocation with a `repairs` parameter containing the receipt ID of the failed invocation. The system runs the new invocation and creates bidirectional links: the failed receipt points to the repair, and the repair points to the failed receipt. Both receipts remain in the ledger.\n\n### Why They Matter\n\nIn systems where multiple components invoke objects on each other's behalf, errors happen. A model misinterprets a contract. An object returns an unexpected format. A network timeout causes a partial result. Without replay and repair, handling these errors requires either: (a) overwriting the error (destroying the record), or (b) creating disconnected corrections (losing the relationship between error and fix). Replay and repair solve both problems. The ledger stays complete. The lineage stays visible.\n\n### The Key Idea\n\nErrors are not erased. They are linked to their corrections. The ledger is append-only — nothing is deleted. Repair creates lineage, not replacement.\n\n**Replay use cases:**\n\n- **Verification.** A receipt claims that object X returned value Y. You replay it. If the new receipt shows the same result, you have independent confirmation. If not, you have detected non-determinism or a state change.\n- **Idempotency.** You sent an invocation but the network dropped the response. You do not know if it succeeded. You replay the receipt ID. The system returns the result without re-executing (if cached) or re-executes and returns a new receipt you can compare.\n- **Audit.** An investigator asks \"what happened at step 7?\" You replay the receipt for step 7 and show the exact input, output, and object that were involved.\n\n**Repair use cases:**\n\n- **Correction.** The first invocation failed because the input was wrong. You send a repair with corrected arguments. The new receipt links to the failed one. Anyone inspecting the ledger sees both the error and the fix.\n- **Lineage.** A downstream result depends on an invocation that later turned out to be wrong. The repair link lets you trace forward from the error to its correction, and backward from the correction to the error.\n- **Audit.** Nothing is erased. An auditor can see the complete history: what was attempted, what failed, what was corrected, and when. No data is hidden.\n\n### What Replay and Repair Got Right\n\n- **Append-only ledger.** The ledger never loses information. Every invocation, every error, every correction is preserved. This is the property that makes audit possible.\n- **Bidirectional linking.** A repair is not an isolated new receipt. It is explicitly connected to the receipt it repairs. You can navigate both directions.\n- **Deterministic verification.** Replay produces evidence. Either the result matches (confirming reproducibility) or it differs (revealing a state dependency or bug).\n- **No silent fixes.** Because repairs are linked, you cannot hide an error by overwriting it. The error remains visible. This prevents \"sweeping under the rug.\"\n\n### What Replay and Repair Cannot Do\n\n- **Replay does not guarantee identical results.** If the object's state changed between the original invocation and the replay, the result may differ. Replay verifies the operation, not the state.\n- **Repair does not undo side effects.** If the failed invocation already wrote to a database or sent a message, the repair does not reverse those effects. It creates a new, correct invocation. Cleanup of side effects is a separate problem.\n- **Both operations assume the ledger is trustworthy.** If the ledger itself is compromised, replay and repair operate on false data. They are integrity mechanisms, not security mechanisms.\n- **Repair chains can grow long.** A sequence of failed repairs creates a chain of linked receipts. Navigating long chains requires tooling.\n\n### How It Connects to Other Ideas\n\n- **Event sourcing.** In event-sourced systems, state is derived from an append-only log of events. Replay is the mechanism for reconstructing state. Repair is analogous to a compensating event that corrects a prior error.\n- **Blockchain immutability.** Blockchains enforce append-only ledgers cryptographically. Replay and repair achieve a similar property by convention and linking rather than by cryptographic hashing.\n- **Git version control.** Git does not overwrite commits. It adds new commits that correct prior ones. The history remains complete. Repair follows the same principle at the invocation level.\n- **OIP's invocation model.** Every object invocation in OIP produces a receipt. Replay and repair are first-class operations on those receipts, making the system auditable by design.\n\n### Sources\n\n- OIP Protocol Specification — invocation ledger, replay endpoint, and repair linking semantics\n- Fowler, Martin. \"Event Sourcing.\" martinfowler.com (2005) — the append-only event log pattern\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-replay-repair`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-replay-repair`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20Replay%20and%20Repair`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: replay and repairs are first-class verbs with lineage fields on the receipt.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-replay-repair","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-replay-repair/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: replay and repairs are first-class verbs with lineage fields on the receipt."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:03.153Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"d4af9171a71cc20e1ca893cb95f0e2b443151f48274dd99e4e2b2903f78dfcca"},{"ts":"2026-07-15T06:24:58.819Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"d4af9171a71cc20e1ca893cb95f0e2b443151f48274dd99e4e2b2903f78dfcca","hash":"d4117a62028f92881efa0e61d138caee292b222cf6a99b948b3197f7477360d4"},{"ts":"2026-07-17T02:43:39.576Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-replay-repair","response":"35 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"d4117a62028f92881efa0e61d138caee292b222cf6a99b948b3197f7477360d4","hash":"9f25138cd1aace1eea536b140530b0cf29881d7833804982b9b1a34e86abb486"}],"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":"9f25138cd1aace1eea536b140530b0cf29881d7833804982b9b1a34e86abb486"},"posted_at":"2026-07-15T04:21:03.153Z","created_at":"2026-07-15T04:21:03.153Z","updated_at":"2026-07-17T02:43:39.576Z","machine":{"shape":"article.machine/v1","slug":"what-is-replay-repair","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-replay-repair","json":"https://miscsubjects.com/api/articles/what-is-replay-repair","bundle":"https://miscsubjects.com/api/articles/what-is-replay-repair/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-replay-repair/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-replay-repair","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-replay-repair\",\"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-replay-repair\",\"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-replay-repair/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-replay-repair\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-replay-repair | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-replay-repair","json":"/api/articles/what-is-replay-repair","markdown":"/api/articles/what-is-replay-repair/bundle?format=markdown","skill":"/api/articles/what-is-replay-repair/skill","topology":"/api/articles/what-is-replay-repair/topology","versions":"/api/articles/what-is-replay-repair/revisions","invocations":"/api/articles/what-is-replay-repair/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-replay-repair","ok":false,"issues":[{"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":"4e0f5a275f68026e07ff80ba27e3a2323ad63e508825729e137d1019c8b22eb1","object":{"object_type":"article-object","identity":{"id":"article:what-is-replay-repair","slug":"what-is-replay-repair","title":"What Is Replay and Repair"},"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-replay-repair","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-replay-repair/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-replay-repair\ndescription: Apply the What Is Replay and Repair article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is Replay and Repair\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-replay-repair). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-replay-repair.\n- Read claims and relationships at /api/articles/what-is-replay-repair/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 Replay and Repair Shelf: Prot\n\n## Representations\n\n- Human: /a/what-is-replay-repair\n- JSON: /api/articles/what-is-replay-repair\n- Relationships: /api/articles/what-is-replay-repair/topology\n- History: /api/articles/what-is-replay-repair/revisions\n"},"json":{"route":"/api/articles/what-is-replay-repair","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-replay-repair/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-replay-repair","objection-7","oip-edge","what","is","replay","repair"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-replay-repair/invocations?status=success","failure_events":"/api/articles/what-is-replay-repair/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-replay-repair","title":"What Is Replay and Repair","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 Replay and Repair**\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 Replay and Repair\n\n## §SELF — what-is-replay-repair\n\n**What this page is:** A definition of two mechanisms for handling and correcting invocation results in a ledger-based system.\n**What it explains:** How replay re-runs past invocations for verification, and how repair creates linked corrections without erasing errors.\n**Why read it:** To understand why appending corrections (rather than overwriting errors) creates an auditable history of what happened and what was fixed.\n\n### What Replay and Repair Are\n\nReplay and repair are two operations on an invocation ledger. A ledger is an append-only record: every invocation is stored as a receipt that cannot be changed or deleted. Replay and repair are the two ways to handle a receipt after it has been created.\n\n**Replay** means re-running a recorded invocation. You send a receipt ID to a replay endpoint. The system runs the same object with the same input again, producing a new receipt. The new receipt links back to the original. You now have two receipts for the same operation. You can compare them.\n\n**Repair** means creating a corrected invocation linked to a failed one. You send a new invocation with a `repairs` parameter containing the receipt ID of the failed invocation. The system runs the new invocation and creates bidirectional links: the failed receipt points to the repair, and the repair points to the failed receipt. Both receipts remain in the ledger.\n\n### Why They Matter\n\nIn systems where multiple components invoke objects on each other's behalf, errors happen. A model misinterprets a contract. An object returns an unexpected format. A network timeout causes a partial result. Without replay and repair, handling these errors requires either: (a) overwriting the error (destroying the record), or (b) creating disconnected corrections (losing the relationship between error and fix). Replay and repair solve both problems. The ledger stays complete. The lineage stays visible.\n\n### The Key Idea\n\nErrors are not erased. They are linked to their corrections. The ledger is append-only — nothing is deleted. Repair creates lineage, not replacement.\n\n**Replay use cases:**\n\n- **Verification.** A receipt claims that object X returned value Y. You replay it. If the new receipt shows the same result, you have independent confirmation. If not, you have detected non-determinism or a state change.\n- **Idempotency.** You sent an invocation but the network dropped the response. You do not know if it succeeded. You replay the receipt ID. The system returns the result without re-executing (if cached) or re-executes and returns a new receipt you can compare.\n- **Audit.** An investigator asks \"what happened at step 7?\" You replay the receipt for step 7 and show the exact input, output, and object that were involved.\n\n**Repair use cases:**\n\n- **Correction.** The first invocation failed because the input was wrong. You send a repair with corrected arguments. The new receipt links to the failed one. Anyone inspecting the ledger sees both the error and the fix.\n- **Lineage.** A downstream result depends on an invocation that later turned out to be wrong. The repair link lets you trace forward from the error to its correction, and backward from the correction to the error.\n- **Audit.** Nothing is erased. An auditor can see the complete history: what was attempted, what failed, what was corrected, and when. No data is hidden.\n\n### What Replay and Repair Got Right\n\n- **Append-only ledger.** The ledger never loses information. Every invocation, every error, every correction is preserved. This is the property that makes audit possible.\n- **Bidirectional linking.** A repair is not an isolated new receipt. It is explicitly connected to the receipt it repairs. You can navigate both directions.\n- **Deterministic verification.** Replay produces evidence. Either the result matches (confirming reproducibility) or it differs (revealing a state dependency or bug).\n- **No silent fixes.** Because repairs are linked, you cannot hide an error by overwriting it. The error remains visible. This prevents \"sweeping under the rug.\"\n\n### What Replay and Repair Cannot Do\n\n- **Replay does not guarantee identical results.** If the object's state changed between the original invocation and the replay, the result may differ. Replay verifies the operation, not the state.\n- **Repair does not undo side effects.** If the failed invocation already wrote to a database or sent a message, the repair does not reverse those effects. It creates a new, correct invocation. Cleanup of side effects is a separate problem.\n- **Both operations assume the ledger is trustworthy.** If the ledger itself is compromised, replay and repair operate on false data. They are integrity mechanisms, not security mechanisms.\n- **Repair chains can grow long.** A sequence of failed repairs creates a chain of linked receipts. Navigating long chains requires tooling.\n\n### How It Connects to Other Ideas\n\n- **Event sourcing.** In event-sourced systems, state is derived from an append-only log of events. Replay is the mechanism for reconstructing state. Repair is analogous to a compensating event that corrects a prior error.\n- **Blockchain immutability.** Blockchains enforce append-only ledgers cryptographically. Replay and repair achieve a similar property by convention and linking rather than by cryptographic hashing.\n- **Git version control.** Git does not overwrite commits. It adds new commits that correct prior ones. The history remains complete. Repair follows the same principle at the invocation level.\n- **OIP's invocation model.** Every object invocation in OIP produces a receipt. Replay and repair are first-class operations on those receipts, making the system auditable by design.\n\n### Sources\n\n- OIP Protocol Specification — invocation ledger, replay endpoint, and repair linking semantics\n- Fowler, Martin. \"Event Sourcing.\" martinfowler.com (2005) — the append-only event log pattern\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-replay-repair`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-replay-repair`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20Replay%20and%20Repair`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: replay and repairs are first-class verbs with lineage fields on the receipt.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-replay-repair","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-replay-repair/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: replay and repairs are first-class verbs with lineage fields on the receipt."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:03.153Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"d4af9171a71cc20e1ca893cb95f0e2b443151f48274dd99e4e2b2903f78dfcca"},{"ts":"2026-07-15T06:24:58.819Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"d4af9171a71cc20e1ca893cb95f0e2b443151f48274dd99e4e2b2903f78dfcca","hash":"d4117a62028f92881efa0e61d138caee292b222cf6a99b948b3197f7477360d4"},{"ts":"2026-07-17T02:43:39.576Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-replay-repair","response":"35 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"d4117a62028f92881efa0e61d138caee292b222cf6a99b948b3197f7477360d4","hash":"9f25138cd1aace1eea536b140530b0cf29881d7833804982b9b1a34e86abb486"}],"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":"9f25138cd1aace1eea536b140530b0cf29881d7833804982b9b1a34e86abb486"},"posted_at":"2026-07-15T04:21:03.153Z","created_at":"2026-07-15T04:21:03.153Z","updated_at":"2026-07-17T02:43:39.576Z","machine":{"shape":"article.machine/v1","slug":"what-is-replay-repair","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-replay-repair","json":"https://miscsubjects.com/api/articles/what-is-replay-repair","bundle":"https://miscsubjects.com/api/articles/what-is-replay-repair/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-replay-repair/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-replay-repair","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-replay-repair\",\"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-replay-repair\",\"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-replay-repair/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-replay-repair\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-replay-repair | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-replay-repair","json":"/api/articles/what-is-replay-repair","markdown":"/api/articles/what-is-replay-repair/bundle?format=markdown","skill":"/api/articles/what-is-replay-repair/skill","topology":"/api/articles/what-is-replay-repair/topology","versions":"/api/articles/what-is-replay-repair/revisions","invocations":"/api/articles/what-is-replay-repair/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-replay-repair","ok":false,"issues":[{"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":"4e0f5a275f68026e07ff80ba27e3a2323ad63e508825729e137d1019c8b22eb1"}}}