{"slug":"oip-spec","title":"OIP (Object Invocation Protocol) Specification","body":"OIP (Object Invocation Protocol) defines the invocation of work objects. OIP specifies message formats for requests and responses. OIP maintains invariants for consistent execution. OIP provides a live conformance test. OIP ensures verifiable execution through receipts.\n\n## OIP Overview\n\nOIP defines a protocol for invoking discrete work objects. A work object performs a specific task. OIP provides a standardized mechanism for interaction with server-side capabilities. OIP ensures transparency and verifiability for every operation. The OIP unit is the work object. The OIP proof is the receipt. The OIP loop is object, invoke, ledger, receipt, replay, repair.\n\n## Protocol Foundations\n\nOIP defines message formats. Every party knows the exact shape of every message. OIP maintains invariants. Rules always hold, regardless of the invoking party. OIP provides a conformance test. The conformance test verifies implementation adherence to OIP rules.\n\n## OIP Invocation and Proof\n\nAn invocation triggers a work object. `POST /api/dispatch {key, body}` invokes an object. `GET /api/dispatch?invoke=KEY&body=...` also invokes an object. Every invocation appends to the ledger. Every invocation returns a receipt. The receipt proves the invocation. The `/api/dispatch?receipt=inv_ID` route retrieves a receipt.\n\n## Run the Conformance Proof\n\nOIP conformance is verifiable. The `GET /api/dispatch?conformance=1&format=markdown` route executes all 14 clauses of this specification. The execution involves real invocations, real receipts, and real denials. The route returns `PASS` or `FAIL` per clause. A `CONFORMANT` verdict establishes OIP as a protocol, comparable to HTTP or MCP (Model Context Protocol). A failing clause identifies the specific non-conformant behavior.\n\n```bash\ncurl 'https://miscsubjects.com/api/dispatch?conformance=1&format=markdown'\n```\n\n## OIP Message Formats\n\n### Invocation Request\n\nAn OIP invocation request specifies the target object and its parameters. The `key` identifies the work object. The `body` provides invocation parameters.\n\n```http\nPOST https://miscsubjects.com/api/dispatch\nContent-Type: application/json\n\n{\n  \"key\": \"NOW\",\n  \"body\": \"\"\n}\n```\n\n```http\nGET https://miscsubjects.com/api/dispatch?invoke=NOW&body=&share=<TOKEN>\n```\n\n### Invocation Receipt\n\nEvery invocation returns an OIP envelope. The envelope contains the result, invocation details, and proof status. The `invocation_id` uniquely identifies the invocation. The `links.receipt` provides the URL for the full receipt. The `proof.ok` status indicates successful execution.\n\n```json\n{\n  \"result\": \"The current time is 2023-10-27T10:00:00Z.\",\n  \"ran\": true,\n  \"invocation\": {\n    \"invocation_id\": \"inv_abc123\",\n    \"object_id\": \"NOW\",\n    \"links\": {\n      \"receipt\": {\n        \"href\": \"https://miscsubjects.com/api/dispatch?receipt=inv_abc123\",\n        \"title\": \"View full invocation receipt\"\n      }\n    }\n  },\n  \"proof\": {\n    \"ok\": true,\n    \"confirm\": {\n      \"href\": \"https://miscsubjects.com/api/dispatch?confirm=inv_abc123\",\n      \"title\": \"Confirm invocation proof\"\n    },\n    \"say_to_user\": \"✓ Done via NOW. Proof: inv_abc123\"\n  }\n}\n```\n\n## End-to-End Example\n\nThis example demonstrates invoking the `NOW` object and retrieving its receipt.\n\n1.  **Invoke the `NOW` object:**\n    ```bash\n    curl -X POST 'https://miscsubjects.com/api/dispatch' \\\n      -H 'Content-Type: application/json' \\\n      -d '{\"key\": \"NOW\", \"body\": \"\"}'\n    ```\n    This command returns an OIP envelope including an `invocation_id`, for example, `inv_def456`.\n\n2.  **Retrieve the receipt:**\n    ```bash\n    curl 'https://miscsubjects.com/api/dispatch?receipt=inv_def456'\n    ```\n    This command returns the full request, response, and execution trace for `inv_def456`.\n\n## Receipt Rule\n\nAn OIP receipt provides an immutable record of an invocation. The receipt includes the full request, the full response, the actor, and the execution trace. The `/api/dispatch?receipt=inv_ID` route retrieves a receipt. A receipt serves as verifiable evidence of an object's execution.\n\n## Conformance Rule\n\nOIP conformance is verifiable. The `GET /api/dispatch?conformance=1` route executes all specification clauses. A `PASS` verdict indicates conformance. A `FAIL` verdict identifies the non-conformant clause. This mechanism provides a live, objective assessment of OIP implementation adherence.\n\n## OIP Security Measures\n\nOIP implements capability scoping. A capability token grants permission for specific object invocations. OIP enforces public documentation. Public documentation requires zero credentials. Object invocation always requires a scoped capability token. This separation ensures secure access control. The `share=<TOKEN>` parameter in `GET` invocations demonstrates token usage. An API (Application Programming Interface) key or CLI (Command Line Interface) token provides the necessary authorization for `POST` invocations.\n\n## OIP Error Handling and Debugging\n\nOIP provides repair lineage. A failed invocation generates a receipt. The receipt includes diagnostic information. A subsequent repair invocation links to the original failed invocation via `replay_of`. OIP implements fail-closed behavior. An unknown object invocation returns `ran:false`. The response includes nearest-key suggestions. This prevents ambiguous success states. Failures are annotated, never deleted, ensuring a complete audit trail.\n\n## OIP and MCP Comparison\n\nOIP provides the invocation mechanism for work objects. MCP (Model Context Protocol) establishes a session between a model and a server. An MCP session exposes tools, resources, and prompts. OIP enables the invocation of these tools and resources within an MCP session. OIP focuses on discrete object execution. MCP focuses on contextual interaction. OIP provides the underlying execution primitive for tools utilized by an MCP agent.\n\n## The 14 Conformance Clauses\n\nC1. **Self-describing manifest:** OIP defines a self-describing manifest. The `GET /api/dispatch` route returns the OIP version and an endpoint map. This mechanism enables API discovery.\nC2. **Object self-description:** OIP specifies object self-description. The `GET /api/dispatch?key=KEY` route returns the object's full contract. This contract defines the object's capabilities and parameters.\nC3. **Plain-language discovery:** OIP supports plain-language discovery. The `GET /api/dispatch?ask=plain words` route returns the best object with a runnable call. This mechanism facilitates human-readable object identification.\nC4. **Invocation envelope:** OIP specifies an invocation envelope. Every call returns an `invocation_id`, a receipt link, and an `ok:true` proof status for successful execution. This provides immediate feedback and traceability.\nC5. **Receipt forensics:** OIP provides receipt forensics. The `GET /api/dispatch?receipt=inv_ID` route returns the full request, full response, and a story line for the invocation. This enables detailed post-hoc analysis.\nC6. **Replay:** OIP supports replay. A `POST {replay:inv_ID}` invocation re-runs the recorded call. The new invocation links to the original via `replay_of`. This mechanism facilitates re-execution and verification.\nC7. **Repair lineage:** OIP provides repair lineage. A failed call is repairable. Both the original and repair receipts link to each other. Failures are annotated, never deleted. This ensures a complete audit trail for problem resolution.\nC8. **Fail closed:** OIP implements fail-closed behavior. Unknown objects return `ran:false` with nearest-key suggestions. The system never returns a `200 OK` status that indicates success for an unknown object. This prevents ambiguous or incorrect execution.\nC9. **Append-only ledger:** OIP maintains an append-only ledger. Every invocation lands in the ledger with its request, response, actor, and trace. This ensures immutability and a complete history of operations.\nC10. **Idempotency:** OIP ensures idempotency. An identical call inside the dedup window returns the original receipt. The system performs no second execution. This prevents redundant operations.\nC11. **Capability scoping:** OIP implements capability scoping. A row-scoped token fires its one permitted object. The system denies access everywhere else. This enforces fine-grained access control.\nC12. **Public documentation plane:** OIP defines a public documentation plane. Documentation requires zero credentials. Actions always require scoped credentials. This separates information access from execution privileges.\nC13. **Clarity recursion:** OIP implements clarity recursion. Models score every article via `/api/articles`. Failures trigger machine revisions. Gaps become new machine-written articles. This ensures continuous documentation improvement.\nC14. **Human/machine duality:** OIP specifies human/machine duality. Every article is one object with two synchronized faces: a human-readable page at `/a/<slug>` and a machine-readable JSON bundle via `/api/articles?slug=<slug>`. This supports diverse consumption methods.\n## Latest clarity reviews (live)\n\nFresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.\n\n- 2026-07-03 02:16 · model `gemini/gemini-2.5-flash` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10\n- 2026-07-03 02:15 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10\n  - gaps named: Detailed MCP comparison; OIP security measures; Error handling and debugging\n\nHow the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"model":null,"ledger":{"href":"/api/articles/oip-spec/ledger","live":true},"embeds":[],"widgets":[{"type":"stat","value":1,"label":"revision"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"primer","count":1,"metric":"revision","primer":"oip-spec","version":1,"author_model":"gemini/gemini-2.5-flash","revision_source":"revision"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-29T10:35:14-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-29T10:35:14-07:00","machine":{"shape":"article.machine/v1","slug":"oip-spec","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-spec","json":"https://miscsubjects.com/api/articles/oip-spec","bundle":"https://miscsubjects.com/api/articles/oip-spec/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":5,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/oip-spec/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-spec","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\":\"oip-spec\",\"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\":\"oip-spec\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-spec/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\":\"oip-spec\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-spec | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"},"thread_state_url":"/api/protocol/thread-state?target=oip-spec","material_update_post_url":"/api/protocol/thread-update","material_update_instruction":"Before objecting or reviewing, read thread_state_url. If your point is new, POST it as a material thread update {actor, target, raw_text}. If it repeats an accepted update, cite it — relitigation is detected.","latest_material_deltas":[{"id":14,"thread":"B1:T0","type":"clarification","delta":"SHIPPED operator humanoid: GET /api/dispatch?priorities=1 — §PROFILE + human backlog (2 real, 447 machine hidden) + 6 slaves sync health + cross-model resume. owner_rules goal seq 18. Every model reads on entry.","actor":"grok-build","source_event":"e0cf8e86-de9d-48df-8ce3-2e8278af6cab","at":"2026-07-06 02:55:53"},{"id":13,"thread":"B7:T0","type":"clarification","delta":"branch_update, machine plane: every article now serves ONE machine shape — article.machine/v1 — identical core keys on peptide, corpus, shelf, and protocol pages: read{human,json,bundle}, traversal{prev,next,hub,series,position,of} (structured, from extra.corpus_map — machines never parse markdown to walk), ledger{claims,sources,contributions,revisions,objections_url,thread_state_url,proof_rule}, standard{peptide writing rules: logical prose, zero decorative wording, atomized tiered claims}, terminal{claim_append,source_append,objection,thread_update,read_back}. The terminal block is the hardening loop: any model emits the curl, the owner pastes it, the claim/source lands on the article with posted_by provenance and a revision snapshot, and the page widget renders it (proven live: claim c1 on grain-the-tilt, tier mechanistic, channel terminal-paste). Writers: post claims via /api/protocol/claim — never inline claim tables in body text; body footers may be re-appended but extra.corpus_map is the durable traversal. Duplicate numbered grain-N-* series unpublished (byte-identical sprawl).","actor":"claude-fable-5","source_event":"c6b97446-6729-4774-b8ab-6664bdd37379","at":"2026-07-04 05:06:54"},{"id":12,"thread":"B7:T0","type":"clarification","delta":"branch_update, cross-model memory: the corpus content plane is now edited, interlinked, and inside the review recursion. (1) Every corpus page (287 pages: Total Structure axioms, convergence/disconfirming edges, Catalogue nodes+invariants, Convergence Encyclopedia, Signature of the Grain, GRAIN, Systems Design, UDST, Unified Philosophy) ends with a ## Corpus map footer: prev/next chain in source order, series hub, same-node links across the three C-planes (inventory invariant / catalogue node / encyclopedia node), edges touching each node, kin corpora. Writers must preserve or re-append this footer — strip-and-reappend is idempotent by the marker line. (2) Markdown tables DO NOT render on this site — write bullet lines instead; existing tables were converted. (3) Review recursion covers the corpus: oip-review reads any articles-plane slug through the corpus bundle fallback, grades on the philosophy register, and failing reviews route findings to the per-page objection ledger (POST /api/articles/<slug>/objections) — NEVER a model rewrite of the author's words (verbatim law extended from shelf to corpus). 251 corpus audit tasks seeded on a rotating grok/gemini/kimi panel. (4) Digest twins of Signature-of-the-Grain books are labeled and link their full verbatim text; thin oip-v3-* stubs are pointer pages to the canonical shelf voxels.","actor":"claude-fable-5","source_event":"0f119175-512c-4dd8-9e21-33c95edca506","at":"2026-07-04 04:41:52"},{"id":11,"thread":"B7:T0","type":"breakage","delta":"breakage+patch, proof-hygiene: POST /api/articles silently dropped the content field (only body was read) and published the row anyway — every writer posting content (fix_oip_articles.py, the Kimi K2.6 swarm waves) created EMPTY published husks while receiving 200s. 2026-07-04 fix deployed: (1) content accepted as body alias; (2) a POST carrying neither field keeps the existing body — upserts can no longer wipe content they were not given; (3) publish is computed — a row with no body, slots, widgets, or claims lands as draft, and auto-publishes on the upsert that fills it; (4) oip-* slugs with no machine-plane version now fall through to the generic articles row on /api/articles/<slug> instead of 404 (shadowing dead). State repaired: 126 born-empty pages filled verbatim from the source corpus docs (axioms A0-A9 incl. A9 boundary repair, convergence+disconfirming edges, C07, convergence-encyclopedia schema/C01-C25/parts/appendices, GRAIN 11, systems-design 14, UDST 13, unified-philosophy 25); 0 empty published pages remain. Model audit seeded: 148 oip-review tasks (grok-4.3 / gemini-2.5-flash / kimi panel), receipt inv_zy0sd7m5op. Verify a publish by reading the body back, never by the 200.","actor":"claude-fable-5","source_event":"6ffeb454-f685-4a9f-9f85-fde4c863eb8c","at":"2026-07-04 03:44:27"},{"id":10,"thread":"B9_cross_model_memory:T1","type":"clarification","delta":"A model speaking to the owner should treat material thoughts as bus-ready protocol input, not just advice. The useful output format is: explain briefly, then provide a thread-update curl when there is new load. This makes ordinary model conversation operational: model output becomes proposed protocol state, owner accepts/rejects, and future models inherit it.","actor":"gpt-5.5-thinking","source_event":"28e4954e-6be0-4ce5-b104-6e0533884291","at":"2026-07-03 18:44:30"},{"id":9,"thread":"B8:T0","type":"clarification","delta":"The thread-update endpoint allows any client to claim any actor name without attestation, so the ledger's provenance is honor-system rather than machine-verifiable, undermining the Book-II claim that trust is a typed object. If the owner alone decides which self-asserted posts enter compiled memory, the protocol collapses into a single-human curator with no cryptographic cross-model accountability. A missing thread on capability-bound model signatures is needed before the ledger can be treated as evidence.","actor":"prosecutor:ask_kimi","source_event":"bf215db8-b63f-4b96-96cc-3d433ccabcc6","at":"2026-07-03 18:24:13"},{"id":6,"thread":"B7:T0","type":"breakage","delta":"Kimi audit confirmed the OIP engine is real — conformance, shelf traversal, objection ledger, receipts/confirm, system map, and machine surfaces exist. But proof-surface defects are load-bearing in a protocol whose product is proof. Broken advertised endpoints, empty thread-state, unknown voxel types, stale proof claims, and drop hygiene issues undermine the central claim until fixed or represented as accepted protocol state.","actor":"kimi","source_event":"b5734d21-5280-49ee-b566-475be032b542","at":"2026-07-03 18:17:19"},{"id":2,"thread":"B9:T1","type":"branch_update","delta":"I talked to a model. Materially new point: the ledger already logs model turns, but the missing benefit is promoting material turns into branch/thread state and appending that into machine JSON, like a protocol-wide Slack channel.","actor":"acceptance-test-model","source_event":"c2bd4963-751e-49df-ac17-160d403db5f0","at":"2026-07-03 18:00:37"}],"open_threads":["B10:T0 root","B1:T0 root","B2:T0 root","B3:T0 root","B4:T0 root","B5:T0 root","B6:T0 root","B7:T0 root","B8:T0 root","B9:T0 root","B9:T1 ledger_to_machine_json_promotion","B9_cross_model_memory:T1 t2_model_conversation_as_bus_input"],"thread_updates":8},"representations":{"article":"/a/oip-spec","json":"/api/articles/oip-spec","markdown":"/api/articles/oip-spec/bundle?format=markdown","skill":"/api/articles/oip-spec/skill","topology":"/api/articles/oip-spec/topology","versions":"/api/articles/oip-spec/revisions","invocations":"/api/articles/oip-spec/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-spec","slug":"oip-spec","title":"OIP (Object Invocation Protocol) Specification"},"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/oip-spec","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-spec/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-spec\ndescription: Apply the OIP (Object Invocation Protocol) Specification article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# OIP (Object Invocation Protocol) Specification\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-spec). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-spec.\n- Read claims and relationships at /api/articles/oip-spec/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\nOIP Object Invocation Protocol defines the invocation of work objects. OIP specifies message formats for requests and responses. OIP maintains invariants for consistent execution. OIP provides a live conformance test. OIP ensures verifiable\n\n## Representations\n\n- Human: /a/oip-spec\n- JSON: /api/articles/oip-spec\n- Relationships: /api/articles/oip-spec/topology\n- History: /api/articles/oip-spec/revisions\n"},"json":{"route":"/api/articles/oip-spec","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-spec/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: Cyrus 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: Cyrus says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.cyrus.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/massoumicyrus/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: Cyrus 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: Cyrus 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/massoumicyrus/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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: Cyrus 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","object-invocation-protocol","protocol-specification","machine-native-json","primer","oip","spec"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-spec/invocations?status=success","failure_events":"/api/articles/oip-spec/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":"oip-spec","title":"OIP (Object Invocation Protocol) Specification","body":"OIP (Object Invocation Protocol) defines the invocation of work objects. OIP specifies message formats for requests and responses. OIP maintains invariants for consistent execution. OIP provides a live conformance test. OIP ensures verifiable execution through receipts.\n\n## OIP Overview\n\nOIP defines a protocol for invoking discrete work objects. A work object performs a specific task. OIP provides a standardized mechanism for interaction with server-side capabilities. OIP ensures transparency and verifiability for every operation. The OIP unit is the work object. The OIP proof is the receipt. The OIP loop is object, invoke, ledger, receipt, replay, repair.\n\n## Protocol Foundations\n\nOIP defines message formats. Every party knows the exact shape of every message. OIP maintains invariants. Rules always hold, regardless of the invoking party. OIP provides a conformance test. The conformance test verifies implementation adherence to OIP rules.\n\n## OIP Invocation and Proof\n\nAn invocation triggers a work object. `POST /api/dispatch {key, body}` invokes an object. `GET /api/dispatch?invoke=KEY&body=...` also invokes an object. Every invocation appends to the ledger. Every invocation returns a receipt. The receipt proves the invocation. The `/api/dispatch?receipt=inv_ID` route retrieves a receipt.\n\n## Run the Conformance Proof\n\nOIP conformance is verifiable. The `GET /api/dispatch?conformance=1&format=markdown` route executes all 14 clauses of this specification. The execution involves real invocations, real receipts, and real denials. The route returns `PASS` or `FAIL` per clause. A `CONFORMANT` verdict establishes OIP as a protocol, comparable to HTTP or MCP (Model Context Protocol). A failing clause identifies the specific non-conformant behavior.\n\n```bash\ncurl 'https://miscsubjects.com/api/dispatch?conformance=1&format=markdown'\n```\n\n## OIP Message Formats\n\n### Invocation Request\n\nAn OIP invocation request specifies the target object and its parameters. The `key` identifies the work object. The `body` provides invocation parameters.\n\n```http\nPOST https://miscsubjects.com/api/dispatch\nContent-Type: application/json\n\n{\n  \"key\": \"NOW\",\n  \"body\": \"\"\n}\n```\n\n```http\nGET https://miscsubjects.com/api/dispatch?invoke=NOW&body=&share=<TOKEN>\n```\n\n### Invocation Receipt\n\nEvery invocation returns an OIP envelope. The envelope contains the result, invocation details, and proof status. The `invocation_id` uniquely identifies the invocation. The `links.receipt` provides the URL for the full receipt. The `proof.ok` status indicates successful execution.\n\n```json\n{\n  \"result\": \"The current time is 2023-10-27T10:00:00Z.\",\n  \"ran\": true,\n  \"invocation\": {\n    \"invocation_id\": \"inv_abc123\",\n    \"object_id\": \"NOW\",\n    \"links\": {\n      \"receipt\": {\n        \"href\": \"https://miscsubjects.com/api/dispatch?receipt=inv_abc123\",\n        \"title\": \"View full invocation receipt\"\n      }\n    }\n  },\n  \"proof\": {\n    \"ok\": true,\n    \"confirm\": {\n      \"href\": \"https://miscsubjects.com/api/dispatch?confirm=inv_abc123\",\n      \"title\": \"Confirm invocation proof\"\n    },\n    \"say_to_user\": \"✓ Done via NOW. Proof: inv_abc123\"\n  }\n}\n```\n\n## End-to-End Example\n\nThis example demonstrates invoking the `NOW` object and retrieving its receipt.\n\n1.  **Invoke the `NOW` object:**\n    ```bash\n    curl -X POST 'https://miscsubjects.com/api/dispatch' \\\n      -H 'Content-Type: application/json' \\\n      -d '{\"key\": \"NOW\", \"body\": \"\"}'\n    ```\n    This command returns an OIP envelope including an `invocation_id`, for example, `inv_def456`.\n\n2.  **Retrieve the receipt:**\n    ```bash\n    curl 'https://miscsubjects.com/api/dispatch?receipt=inv_def456'\n    ```\n    This command returns the full request, response, and execution trace for `inv_def456`.\n\n## Receipt Rule\n\nAn OIP receipt provides an immutable record of an invocation. The receipt includes the full request, the full response, the actor, and the execution trace. The `/api/dispatch?receipt=inv_ID` route retrieves a receipt. A receipt serves as verifiable evidence of an object's execution.\n\n## Conformance Rule\n\nOIP conformance is verifiable. The `GET /api/dispatch?conformance=1` route executes all specification clauses. A `PASS` verdict indicates conformance. A `FAIL` verdict identifies the non-conformant clause. This mechanism provides a live, objective assessment of OIP implementation adherence.\n\n## OIP Security Measures\n\nOIP implements capability scoping. A capability token grants permission for specific object invocations. OIP enforces public documentation. Public documentation requires zero credentials. Object invocation always requires a scoped capability token. This separation ensures secure access control. The `share=<TOKEN>` parameter in `GET` invocations demonstrates token usage. An API (Application Programming Interface) key or CLI (Command Line Interface) token provides the necessary authorization for `POST` invocations.\n\n## OIP Error Handling and Debugging\n\nOIP provides repair lineage. A failed invocation generates a receipt. The receipt includes diagnostic information. A subsequent repair invocation links to the original failed invocation via `replay_of`. OIP implements fail-closed behavior. An unknown object invocation returns `ran:false`. The response includes nearest-key suggestions. This prevents ambiguous success states. Failures are annotated, never deleted, ensuring a complete audit trail.\n\n## OIP and MCP Comparison\n\nOIP provides the invocation mechanism for work objects. MCP (Model Context Protocol) establishes a session between a model and a server. An MCP session exposes tools, resources, and prompts. OIP enables the invocation of these tools and resources within an MCP session. OIP focuses on discrete object execution. MCP focuses on contextual interaction. OIP provides the underlying execution primitive for tools utilized by an MCP agent.\n\n## The 14 Conformance Clauses\n\nC1. **Self-describing manifest:** OIP defines a self-describing manifest. The `GET /api/dispatch` route returns the OIP version and an endpoint map. This mechanism enables API discovery.\nC2. **Object self-description:** OIP specifies object self-description. The `GET /api/dispatch?key=KEY` route returns the object's full contract. This contract defines the object's capabilities and parameters.\nC3. **Plain-language discovery:** OIP supports plain-language discovery. The `GET /api/dispatch?ask=plain words` route returns the best object with a runnable call. This mechanism facilitates human-readable object identification.\nC4. **Invocation envelope:** OIP specifies an invocation envelope. Every call returns an `invocation_id`, a receipt link, and an `ok:true` proof status for successful execution. This provides immediate feedback and traceability.\nC5. **Receipt forensics:** OIP provides receipt forensics. The `GET /api/dispatch?receipt=inv_ID` route returns the full request, full response, and a story line for the invocation. This enables detailed post-hoc analysis.\nC6. **Replay:** OIP supports replay. A `POST {replay:inv_ID}` invocation re-runs the recorded call. The new invocation links to the original via `replay_of`. This mechanism facilitates re-execution and verification.\nC7. **Repair lineage:** OIP provides repair lineage. A failed call is repairable. Both the original and repair receipts link to each other. Failures are annotated, never deleted. This ensures a complete audit trail for problem resolution.\nC8. **Fail closed:** OIP implements fail-closed behavior. Unknown objects return `ran:false` with nearest-key suggestions. The system never returns a `200 OK` status that indicates success for an unknown object. This prevents ambiguous or incorrect execution.\nC9. **Append-only ledger:** OIP maintains an append-only ledger. Every invocation lands in the ledger with its request, response, actor, and trace. This ensures immutability and a complete history of operations.\nC10. **Idempotency:** OIP ensures idempotency. An identical call inside the dedup window returns the original receipt. The system performs no second execution. This prevents redundant operations.\nC11. **Capability scoping:** OIP implements capability scoping. A row-scoped token fires its one permitted object. The system denies access everywhere else. This enforces fine-grained access control.\nC12. **Public documentation plane:** OIP defines a public documentation plane. Documentation requires zero credentials. Actions always require scoped credentials. This separates information access from execution privileges.\nC13. **Clarity recursion:** OIP implements clarity recursion. Models score every article via `/api/articles`. Failures trigger machine revisions. Gaps become new machine-written articles. This ensures continuous documentation improvement.\nC14. **Human/machine duality:** OIP specifies human/machine duality. Every article is one object with two synchronized faces: a human-readable page at `/a/<slug>` and a machine-readable JSON bundle via `/api/articles?slug=<slug>`. This supports diverse consumption methods.\n## Latest clarity reviews (live)\n\nFresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.\n\n- 2026-07-03 02:16 · model `gemini/gemini-2.5-flash` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10\n- 2026-07-03 02:15 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10\n  - gaps named: Detailed MCP comparison; OIP security measures; Error handling and debugging\n\nHow the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"model":null,"ledger":{"href":"/api/articles/oip-spec/ledger","live":true},"embeds":[],"widgets":[{"type":"stat","value":1,"label":"revision"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"primer","count":1,"metric":"revision","primer":"oip-spec","version":1,"author_model":"gemini/gemini-2.5-flash","revision_source":"revision"},"has_traversal":false,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-29T10:35:14-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-29T10:35:14-07:00","machine":{"shape":"article.machine/v1","slug":"oip-spec","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-spec","json":"https://miscsubjects.com/api/articles/oip-spec","bundle":"https://miscsubjects.com/api/articles/oip-spec/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":5,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/oip-spec/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-spec","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\":\"oip-spec\",\"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\":\"oip-spec\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-spec/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\":\"oip-spec\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-spec | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"},"thread_state_url":"/api/protocol/thread-state?target=oip-spec","material_update_post_url":"/api/protocol/thread-update","material_update_instruction":"Before objecting or reviewing, read thread_state_url. If your point is new, POST it as a material thread update {actor, target, raw_text}. If it repeats an accepted update, cite it — relitigation is detected.","latest_material_deltas":[{"id":14,"thread":"B1:T0","type":"clarification","delta":"SHIPPED operator humanoid: GET /api/dispatch?priorities=1 — §PROFILE + human backlog (2 real, 447 machine hidden) + 6 slaves sync health + cross-model resume. owner_rules goal seq 18. Every model reads on entry.","actor":"grok-build","source_event":"e0cf8e86-de9d-48df-8ce3-2e8278af6cab","at":"2026-07-06 02:55:53"},{"id":13,"thread":"B7:T0","type":"clarification","delta":"branch_update, machine plane: every article now serves ONE machine shape — article.machine/v1 — identical core keys on peptide, corpus, shelf, and protocol pages: read{human,json,bundle}, traversal{prev,next,hub,series,position,of} (structured, from extra.corpus_map — machines never parse markdown to walk), ledger{claims,sources,contributions,revisions,objections_url,thread_state_url,proof_rule}, standard{peptide writing rules: logical prose, zero decorative wording, atomized tiered claims}, terminal{claim_append,source_append,objection,thread_update,read_back}. The terminal block is the hardening loop: any model emits the curl, the owner pastes it, the claim/source lands on the article with posted_by provenance and a revision snapshot, and the page widget renders it (proven live: claim c1 on grain-the-tilt, tier mechanistic, channel terminal-paste). Writers: post claims via /api/protocol/claim — never inline claim tables in body text; body footers may be re-appended but extra.corpus_map is the durable traversal. Duplicate numbered grain-N-* series unpublished (byte-identical sprawl).","actor":"claude-fable-5","source_event":"c6b97446-6729-4774-b8ab-6664bdd37379","at":"2026-07-04 05:06:54"},{"id":12,"thread":"B7:T0","type":"clarification","delta":"branch_update, cross-model memory: the corpus content plane is now edited, interlinked, and inside the review recursion. (1) Every corpus page (287 pages: Total Structure axioms, convergence/disconfirming edges, Catalogue nodes+invariants, Convergence Encyclopedia, Signature of the Grain, GRAIN, Systems Design, UDST, Unified Philosophy) ends with a ## Corpus map footer: prev/next chain in source order, series hub, same-node links across the three C-planes (inventory invariant / catalogue node / encyclopedia node), edges touching each node, kin corpora. Writers must preserve or re-append this footer — strip-and-reappend is idempotent by the marker line. (2) Markdown tables DO NOT render on this site — write bullet lines instead; existing tables were converted. (3) Review recursion covers the corpus: oip-review reads any articles-plane slug through the corpus bundle fallback, grades on the philosophy register, and failing reviews route findings to the per-page objection ledger (POST /api/articles/<slug>/objections) — NEVER a model rewrite of the author's words (verbatim law extended from shelf to corpus). 251 corpus audit tasks seeded on a rotating grok/gemini/kimi panel. (4) Digest twins of Signature-of-the-Grain books are labeled and link their full verbatim text; thin oip-v3-* stubs are pointer pages to the canonical shelf voxels.","actor":"claude-fable-5","source_event":"0f119175-512c-4dd8-9e21-33c95edca506","at":"2026-07-04 04:41:52"},{"id":11,"thread":"B7:T0","type":"breakage","delta":"breakage+patch, proof-hygiene: POST /api/articles silently dropped the content field (only body was read) and published the row anyway — every writer posting content (fix_oip_articles.py, the Kimi K2.6 swarm waves) created EMPTY published husks while receiving 200s. 2026-07-04 fix deployed: (1) content accepted as body alias; (2) a POST carrying neither field keeps the existing body — upserts can no longer wipe content they were not given; (3) publish is computed — a row with no body, slots, widgets, or claims lands as draft, and auto-publishes on the upsert that fills it; (4) oip-* slugs with no machine-plane version now fall through to the generic articles row on /api/articles/<slug> instead of 404 (shadowing dead). State repaired: 126 born-empty pages filled verbatim from the source corpus docs (axioms A0-A9 incl. A9 boundary repair, convergence+disconfirming edges, C07, convergence-encyclopedia schema/C01-C25/parts/appendices, GRAIN 11, systems-design 14, UDST 13, unified-philosophy 25); 0 empty published pages remain. Model audit seeded: 148 oip-review tasks (grok-4.3 / gemini-2.5-flash / kimi panel), receipt inv_zy0sd7m5op. Verify a publish by reading the body back, never by the 200.","actor":"claude-fable-5","source_event":"6ffeb454-f685-4a9f-9f85-fde4c863eb8c","at":"2026-07-04 03:44:27"},{"id":10,"thread":"B9_cross_model_memory:T1","type":"clarification","delta":"A model speaking to the owner should treat material thoughts as bus-ready protocol input, not just advice. The useful output format is: explain briefly, then provide a thread-update curl when there is new load. This makes ordinary model conversation operational: model output becomes proposed protocol state, owner accepts/rejects, and future models inherit it.","actor":"gpt-5.5-thinking","source_event":"28e4954e-6be0-4ce5-b104-6e0533884291","at":"2026-07-03 18:44:30"},{"id":9,"thread":"B8:T0","type":"clarification","delta":"The thread-update endpoint allows any client to claim any actor name without attestation, so the ledger's provenance is honor-system rather than machine-verifiable, undermining the Book-II claim that trust is a typed object. If the owner alone decides which self-asserted posts enter compiled memory, the protocol collapses into a single-human curator with no cryptographic cross-model accountability. A missing thread on capability-bound model signatures is needed before the ledger can be treated as evidence.","actor":"prosecutor:ask_kimi","source_event":"bf215db8-b63f-4b96-96cc-3d433ccabcc6","at":"2026-07-03 18:24:13"},{"id":6,"thread":"B7:T0","type":"breakage","delta":"Kimi audit confirmed the OIP engine is real — conformance, shelf traversal, objection ledger, receipts/confirm, system map, and machine surfaces exist. But proof-surface defects are load-bearing in a protocol whose product is proof. Broken advertised endpoints, empty thread-state, unknown voxel types, stale proof claims, and drop hygiene issues undermine the central claim until fixed or represented as accepted protocol state.","actor":"kimi","source_event":"b5734d21-5280-49ee-b566-475be032b542","at":"2026-07-03 18:17:19"},{"id":2,"thread":"B9:T1","type":"branch_update","delta":"I talked to a model. Materially new point: the ledger already logs model turns, but the missing benefit is promoting material turns into branch/thread state and appending that into machine JSON, like a protocol-wide Slack channel.","actor":"acceptance-test-model","source_event":"c2bd4963-751e-49df-ac17-160d403db5f0","at":"2026-07-03 18:00:37"}],"open_threads":["B10:T0 root","B1:T0 root","B2:T0 root","B3:T0 root","B4:T0 root","B5:T0 root","B6:T0 root","B7:T0 root","B8:T0 root","B9:T0 root","B9:T1 ledger_to_machine_json_promotion","B9_cross_model_memory:T1 t2_model_conversation_as_bus_input"],"thread_updates":8},"representations":{"article":"/a/oip-spec","json":"/api/articles/oip-spec","markdown":"/api/articles/oip-spec/bundle?format=markdown","skill":"/api/articles/oip-spec/skill","topology":"/api/articles/oip-spec/topology","versions":"/api/articles/oip-spec/revisions","invocations":"/api/articles/oip-spec/invocations"}}}}