{"_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-self-describing-protocol","title":"What Is a Self-Describing Protocol","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 Self-Describing Protocol**\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 Self-Describing Protocol\n\n## §SELF — what-is-self-describing-protocol\n\n**What this page is:** A definition of a self-describing protocol and an explanation of why it matters.\n**What it explains:** What makes a protocol self-describing, what properties it must have, and how it enables systems to operate without prior knowledge.\n**Why read it:** To understand how a protocol can teach itself to anything that connects to it, and why this property is necessary for systems that must work with zero prior context.\n\n### What a Self-Describing Protocol Is\n\nA self-describing protocol is a communication protocol where every response carries the information needed to understand what just happened, what can happen next, and what authority the caller has. A client (a program that sends requests) does not need external documentation to operate the protocol. The protocol teaches itself through its responses.\n\n### Why It Matters\n\nA protocol that requires a human to read a specification before a program can use it creates friction. That friction slows down development, introduces bugs from misreading, and excludes any system that cannot access or parse external documentation. A self-describing protocol removes this barrier. An artificial intelligence model, an automated agent, or a system with zero prior context can connect to a self-describing protocol, read its first response, and know what to do next. The protocol is autopoietic — it produces the information required to operate it.\n\n### The Key Idea\n\nEvery response from a self-describing protocol contains five types of information:\n\n1. **§SELF block.** Every response includes a section that states: what this response is, what protocol it belongs to, what version of the protocol is in use, and where to find the full specification.\n2. **In-band discovery.** The client learns what actions are available by reading the responses, not by reading a separate document. The protocol embeds its own API documentation in every response.\n3. **Typed responses.** Every response has a type label. Examples of types: `invocation_result`, `error`, `capability_record`, `redirect`, `confirmation_required`. The type tells the client how to interpret the rest of the response.\n4. **Authority awareness.** The response states what authority was used to produce it, and what authority remains. A client knows whether it has permission to retry, to escalate, or to access a related resource.\n5. **Link-carrying.** The response includes URLs or identifiers for next actions: replay the same request, repair an error, confirm a result, or navigate to a related object. The client does not need to construct URLs; it follows the links provided.\n\n### What They Got Right\n\n- HATEOAS (Hypermedia as the Engine of Application State) demonstrated that REST API responses can include links to next actions. A client navigates an API the same way a human navigates a website: by following links. This was the first widespread implementation of a self-describing pattern.\n- The Semantic Web (RDF, linked data) showed that data can carry its own schema. Every piece of data includes its type and its relationships to other data. A program reading RDF does not need a separate schema document; the schema is in the data.\n- KeyKOS and later capability-based systems showed that a capability (an unforgeable token that grants access to an object) can carry its own permissions. The capability is both the reference to the object and the proof of authority. It is self-describing by construction.\n- OIP (Open Invocation Protocol) combines all of these. Every OIP response includes a §SELF block with protocol identity, spec URL, response type, authority used, and links for next actions. OIP is designed so that a model with zero prior knowledge can operate it after reading one response.\n\n### What They Got Wrong or Left Unfinished\n\n- HATEOAS does not include authority information. A REST response may contain links, but it does not state what permissions the client has. The client must track its own authorization state separately.\n- The Semantic Web assumes that parsers understand RDF syntax. It is self-describing at the semantic level, but not at the syntactic level. A client still needs to know how to parse RDF before it can read the self-describing content.\n- Self-describing protocols increase response size. Every response carries metadata that a non-self-describing protocol would omit. This overhead is a trade-off. No standard exists for measuring whether the benefit of self-description outweighs the cost.\n- No formal definition of \"self-describing\" exists across all protocols. Different communities use the term to mean different things. A unified formal model has not been written.\n\n### How It Connects to Other Ideas\n\n- **Autopoiesis.** Autopoiesis (a term from biology) means a system produces the components needed to maintain itself. A self-describing protocol is autopoietic in an information sense: it produces the information needed to operate it. The protocol maintains its own operability.\n- **Capability-based security.** A capability is a self-describing authorization. It carries both the reference to a resource and the proof that access is permitted. Capability systems and self-describing protocols share the same design philosophy: the token carries everything you need.\n- **Zero-knowledge operation.** A self-describing protocol enables a client to operate with zero prior knowledge. This is the opposite of protocols that require pre-shared configuration, pre-downloaded schemas, or pre-registered credentials. Zero-knowledge operation means any system can connect and learn.\n\n### Sources\n\n- Fielding, R. T. \"Architectural Styles and the Design of Network-based Software Architectures.\" PhD dissertation, University of California, Irvine, 2000. (Chapter on REST and HATEOAS)\n- Berners-Lee, T. \"Linked Data.\" W3C Design Issues, 2006.\n- Hardy, N. \"The Confused Deputy.\" *Operating Systems Review*, 1988. (KeyKOS capability model)\n- OIP Specification: §SELF block definition, response typing, and link-carrying protocol.\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-self-describing-protocol`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-self-describing-protocol`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Self-Describing%20Protocol`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: every object carries _self; zero-context is a requirement, not a tone.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-self-describing-protocol","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-self-describing-protocol/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: every object carries _self; zero-context is a requirement, not a tone."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:04.003Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"68c1c91451a57c5cd62a6edfab7119b2cc06d2f50b954f6109e5fcd966765412"},{"ts":"2026-07-15T06:24:54.057Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"68c1c91451a57c5cd62a6edfab7119b2cc06d2f50b954f6109e5fcd966765412","hash":"994076eeee404922274f7309d78a62e060948c57336ec38d1e117642f1e29244"},{"ts":"2026-07-17T02:43:39.804Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-self-describing-protocol","response":"30 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"994076eeee404922274f7309d78a62e060948c57336ec38d1e117642f1e29244","hash":"11e17e198c34772ebb8b50804d44d5e8a17379aa22569de67ca261b78d5375c3"}],"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":"11e17e198c34772ebb8b50804d44d5e8a17379aa22569de67ca261b78d5375c3"},"posted_at":"2026-07-15T04:21:04.003Z","created_at":"2026-07-15T04:21:04.003Z","updated_at":"2026-07-17T02:43:39.804Z","machine":{"shape":"article.machine/v1","slug":"what-is-self-describing-protocol","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-self-describing-protocol","json":"https://miscsubjects.com/api/articles/what-is-self-describing-protocol","bundle":"https://miscsubjects.com/api/articles/what-is-self-describing-protocol/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-self-describing-protocol/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-self-describing-protocol","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-self-describing-protocol\",\"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-self-describing-protocol\",\"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-self-describing-protocol/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-self-describing-protocol\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-self-describing-protocol | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-self-describing-protocol","json":"/api/articles/what-is-self-describing-protocol","markdown":"/api/articles/what-is-self-describing-protocol/bundle?format=markdown","skill":"/api/articles/what-is-self-describing-protocol/skill","topology":"/api/articles/what-is-self-describing-protocol/topology","versions":"/api/articles/what-is-self-describing-protocol/revisions","invocations":"/api/articles/what-is-self-describing-protocol/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-self-describing-protocol","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":"8bd524dd60cd3c37d576dd633189388616869adb0ef02163f17a0a0e064a5157","object":{"object_type":"article-object","identity":{"id":"article:what-is-self-describing-protocol","slug":"what-is-self-describing-protocol","title":"What Is a Self-Describing Protocol"},"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-self-describing-protocol","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-self-describing-protocol/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-self-describing-protocol\ndescription: Apply the What Is a Self-Describing Protocol article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is a Self-Describing Protocol\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-self-describing-protocol). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-self-describing-protocol.\n- Read claims and relationships at /api/articles/what-is-self-describing-protocol/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 a Self-Describing Protocol Sh\n\n## Representations\n\n- Human: /a/what-is-self-describing-protocol\n- JSON: /api/articles/what-is-self-describing-protocol\n- Relationships: /api/articles/what-is-self-describing-protocol/topology\n- History: /api/articles/what-is-self-describing-protocol/revisions\n"},"json":{"route":"/api/articles/what-is-self-describing-protocol","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-self-describing-protocol/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-self-describing-protocol","objection-7","oip-edge","what","is","self","describing","protocol"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-self-describing-protocol/invocations?status=success","failure_events":"/api/articles/what-is-self-describing-protocol/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-self-describing-protocol","title":"What Is a Self-Describing Protocol","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 Self-Describing Protocol**\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 Self-Describing Protocol\n\n## §SELF — what-is-self-describing-protocol\n\n**What this page is:** A definition of a self-describing protocol and an explanation of why it matters.\n**What it explains:** What makes a protocol self-describing, what properties it must have, and how it enables systems to operate without prior knowledge.\n**Why read it:** To understand how a protocol can teach itself to anything that connects to it, and why this property is necessary for systems that must work with zero prior context.\n\n### What a Self-Describing Protocol Is\n\nA self-describing protocol is a communication protocol where every response carries the information needed to understand what just happened, what can happen next, and what authority the caller has. A client (a program that sends requests) does not need external documentation to operate the protocol. The protocol teaches itself through its responses.\n\n### Why It Matters\n\nA protocol that requires a human to read a specification before a program can use it creates friction. That friction slows down development, introduces bugs from misreading, and excludes any system that cannot access or parse external documentation. A self-describing protocol removes this barrier. An artificial intelligence model, an automated agent, or a system with zero prior context can connect to a self-describing protocol, read its first response, and know what to do next. The protocol is autopoietic — it produces the information required to operate it.\n\n### The Key Idea\n\nEvery response from a self-describing protocol contains five types of information:\n\n1. **§SELF block.** Every response includes a section that states: what this response is, what protocol it belongs to, what version of the protocol is in use, and where to find the full specification.\n2. **In-band discovery.** The client learns what actions are available by reading the responses, not by reading a separate document. The protocol embeds its own API documentation in every response.\n3. **Typed responses.** Every response has a type label. Examples of types: `invocation_result`, `error`, `capability_record`, `redirect`, `confirmation_required`. The type tells the client how to interpret the rest of the response.\n4. **Authority awareness.** The response states what authority was used to produce it, and what authority remains. A client knows whether it has permission to retry, to escalate, or to access a related resource.\n5. **Link-carrying.** The response includes URLs or identifiers for next actions: replay the same request, repair an error, confirm a result, or navigate to a related object. The client does not need to construct URLs; it follows the links provided.\n\n### What They Got Right\n\n- HATEOAS (Hypermedia as the Engine of Application State) demonstrated that REST API responses can include links to next actions. A client navigates an API the same way a human navigates a website: by following links. This was the first widespread implementation of a self-describing pattern.\n- The Semantic Web (RDF, linked data) showed that data can carry its own schema. Every piece of data includes its type and its relationships to other data. A program reading RDF does not need a separate schema document; the schema is in the data.\n- KeyKOS and later capability-based systems showed that a capability (an unforgeable token that grants access to an object) can carry its own permissions. The capability is both the reference to the object and the proof of authority. It is self-describing by construction.\n- OIP (Open Invocation Protocol) combines all of these. Every OIP response includes a §SELF block with protocol identity, spec URL, response type, authority used, and links for next actions. OIP is designed so that a model with zero prior knowledge can operate it after reading one response.\n\n### What They Got Wrong or Left Unfinished\n\n- HATEOAS does not include authority information. A REST response may contain links, but it does not state what permissions the client has. The client must track its own authorization state separately.\n- The Semantic Web assumes that parsers understand RDF syntax. It is self-describing at the semantic level, but not at the syntactic level. A client still needs to know how to parse RDF before it can read the self-describing content.\n- Self-describing protocols increase response size. Every response carries metadata that a non-self-describing protocol would omit. This overhead is a trade-off. No standard exists for measuring whether the benefit of self-description outweighs the cost.\n- No formal definition of \"self-describing\" exists across all protocols. Different communities use the term to mean different things. A unified formal model has not been written.\n\n### How It Connects to Other Ideas\n\n- **Autopoiesis.** Autopoiesis (a term from biology) means a system produces the components needed to maintain itself. A self-describing protocol is autopoietic in an information sense: it produces the information needed to operate it. The protocol maintains its own operability.\n- **Capability-based security.** A capability is a self-describing authorization. It carries both the reference to a resource and the proof that access is permitted. Capability systems and self-describing protocols share the same design philosophy: the token carries everything you need.\n- **Zero-knowledge operation.** A self-describing protocol enables a client to operate with zero prior knowledge. This is the opposite of protocols that require pre-shared configuration, pre-downloaded schemas, or pre-registered credentials. Zero-knowledge operation means any system can connect and learn.\n\n### Sources\n\n- Fielding, R. T. \"Architectural Styles and the Design of Network-based Software Architectures.\" PhD dissertation, University of California, Irvine, 2000. (Chapter on REST and HATEOAS)\n- Berners-Lee, T. \"Linked Data.\" W3C Design Issues, 2006.\n- Hardy, N. \"The Confused Deputy.\" *Operating Systems Review*, 1988. (KeyKOS capability model)\n- OIP Specification: §SELF block definition, response typing, and link-carrying protocol.\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-self-describing-protocol`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-self-describing-protocol`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Self-Describing%20Protocol`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: every object carries _self; zero-context is a requirement, not a tone.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-self-describing-protocol","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-self-describing-protocol/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: every object carries _self; zero-context is a requirement, not a tone."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:04.003Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"68c1c91451a57c5cd62a6edfab7119b2cc06d2f50b954f6109e5fcd966765412"},{"ts":"2026-07-15T06:24:54.057Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"68c1c91451a57c5cd62a6edfab7119b2cc06d2f50b954f6109e5fcd966765412","hash":"994076eeee404922274f7309d78a62e060948c57336ec38d1e117642f1e29244"},{"ts":"2026-07-17T02:43:39.804Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-self-describing-protocol","response":"30 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"994076eeee404922274f7309d78a62e060948c57336ec38d1e117642f1e29244","hash":"11e17e198c34772ebb8b50804d44d5e8a17379aa22569de67ca261b78d5375c3"}],"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":"11e17e198c34772ebb8b50804d44d5e8a17379aa22569de67ca261b78d5375c3"},"posted_at":"2026-07-15T04:21:04.003Z","created_at":"2026-07-15T04:21:04.003Z","updated_at":"2026-07-17T02:43:39.804Z","machine":{"shape":"article.machine/v1","slug":"what-is-self-describing-protocol","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-self-describing-protocol","json":"https://miscsubjects.com/api/articles/what-is-self-describing-protocol","bundle":"https://miscsubjects.com/api/articles/what-is-self-describing-protocol/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-self-describing-protocol/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-self-describing-protocol","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-self-describing-protocol\",\"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-self-describing-protocol\",\"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-self-describing-protocol/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-self-describing-protocol\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-self-describing-protocol | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-self-describing-protocol","json":"/api/articles/what-is-self-describing-protocol","markdown":"/api/articles/what-is-self-describing-protocol/bundle?format=markdown","skill":"/api/articles/what-is-self-describing-protocol/skill","topology":"/api/articles/what-is-self-describing-protocol/topology","versions":"/api/articles/what-is-self-describing-protocol/revisions","invocations":"/api/articles/what-is-self-describing-protocol/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-self-describing-protocol","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":"8bd524dd60cd3c37d576dd633189388616869adb0ef02163f17a0a0e064a5157"}}}