{"slug":"oip-machine-json","title":"Machine-native JSON","body":"## Introduction to Machine-native JSON\n\nMachine-native JSON is a structured operating map that a model can read without guessing. It contains routes, object ids, invocation shapes, proof links, and repair paths. A model can use this JSON to operate a system, while a human can read the accompanying prose article to understand the same system.\n\n## Why JSON matters\n\nThe JSON is not decoration. It is the essential map a model can read without guessing. It contains routes, object ids, invocation shapes, proof links, and repair paths.\n\n## Prose and JSON\n\nThe prose article helps a human understand the system. The JSON bundle lets a model operate the same system. Both describe the same object.\n\n## Rule\n\nIf a machine has to infer a route, key, argument shape, or proof path from vibes, the object is not self-explaining enough.\n\n## What is MCP?\n\nMCP stands for Model Context Protocol, an open standard where an AI model connects to an MCP server over a session, and the server exposes tools, resources, and prompts the model can call. MCP is NOT a content-management system.\n\n## OIP vs MCP\n\nOIP stands for Object Invocation Protocol. OIP differs from MCP by using plain URLs and receipts with no persistent session: any model that can open a URL can act. In contrast, MCP requires a persistent session between the model and the server. On miscsubjects.com, the build uses OIP, where directory rows are the objects, and invocations are made using POST /api/dispatch {key, body} or GET /api/dispatch?invoke=KEY&body=..., resulting in an append-only ledger with a receipt at /api/dispatch?receipt=inv_ID.\n\n## Using OIP with curl\n\nThe build operation can be performed using curl, with the exact route shape being POST /api/dispatch or GET /api/dispatch?invoke=KEY&body=....\n\n## Subsidiary Concepts\n\nSubsidiary concepts that need their own OIP articles include API (Application Programming Interface), CLI (Command-Line Interface), REST (Representational State of Resource), JSON (JavaScript Object Notation), and URL (Uniform Resource Locator). A server is a computer that provides services or data to other computers, and a token is a unique string used for authentication or authorization. An endpoint is a URL that an API uses to interact with a server.\n\n## Conclusion\n\nIn conclusion, machine-native JSON is essential for models to operate a system without guessing. OIP and MCP are two different protocols, with OIP using plain URLs and receipts, and MCP requiring a persistent session. Understanding the differences between these protocols and concepts is crucial for building and using machine-native JSON effectively.\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:36 · 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: API; CLI; REST; JSON\n- 2026-07-02 23:28 · 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: MCP explanation; Detailed comparison between OIP and MCP\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.","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"style":{"accent":"#16324f","measure":860},"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"}],"prov":{"model":"system/oip_articles","action":"generate"}}