{"slug":"oip-articles-content-plane","title":"OIP Articles and Content Objects","body":"OIP (Object Invocation Protocol) defines work objects for protocol operations and content presentation.\nAn OIP work object is the unit of work.\nAn OIP invocation appends to the ledger and returns a receipt.\nThe OIP proof is the receipt.\nThe OIP loop is object, invoke, ledger, receipt, replay, repair.\n\n## Introduction to OIP and MCP\n\nObject Invocation Protocol (OIP) defines a protocol for invoking work objects. Model Context Protocol (MCP) defines a protocol where a Model Context Protocol (MCP) server exposes tools, resources, and prompts to an Artificial Intelligence (AI) model over a session. OIP uses plain Uniform Resource Locators (URLs) for invocation and returns receipts. MCP establishes a persistent session for model interaction. OIP operates without a persistent session. OIP enables any model capable of opening a URL to act.\n\n## Content Articles\n\nContent articles are work objects. Content articles carry body, claims, sources, provenance, widgets, bundles, and ledger history. Content articles present evidence. The `/a/<slug>` route retrieves a content article.\n\n## OIP Articles\n\nOIP articles are work objects. OIP articles explain Object Invocation Protocol (OIP) capability objects. OIP articles explain OIP build operations. The `/api/articles` route lists OIP articles. The `/a/<slug>` route retrieves an OIP article.\n\n## Object Invocation Mechanism\n\nObject invocation is the act of sending a request to the `/api/dispatch` route. The `POST /api/dispatch {key, body}` mechanism invokes an object. The `GET /api/dispatch?invoke=KEY&body=...` mechanism invokes an object. Every invocation appends to the ledger. Every invocation returns a receipt.\n\n## Receipt Mechanism\n\nA receipt is proof of an invocation. The `GET /api/dispatch?receipt=inv_ID` mechanism retrieves a receipt.\n\n## End-to-End Example\n\nTo invoke an object with key `my_key` and body `my_body` using a `POST` request, execute:\n```bash\ncurl -X POST /api/dispatch -H 'Content-Type: application/json' -d '{\"key\":\"my_key\",\"body\":\"my_body\"}'\n```\nThis invocation returns a receipt with an `inv_ID`. To retrieve the receipt for an invocation with ID `my_inv_ID`, execute:\n```bash\ncurl /api/dispatch?receipt=my_inv_ID\n```\nTo invoke an object with key `another_key` and body `another_body` using a `GET` request, execute:\n```bash\ncurl '/api/dispatch?invoke=another_key&body=another_body'\n```\nThis invocation returns a receipt with an `inv_ID`. To retrieve the receipt for an invocation with ID `another_inv_ID`, execute:\n```bash\ncurl /api/dispatch?receipt=another_inv_ID\n```\n\n## Receipt Rule\n\nA receipt proves the successful ledgering of an object invocation. A receipt contains the `inv_ID`, `key`, `body`, and `timestamp` of the invocation.\n\n## Conformance Rule\n\nA conformant OIP implementation invokes work objects via `/api/dispatch`. A conformant OIP implementation provides receipts via `/api/dispatch?receipt=inv_ID`. A conformant OIP implementation maintains a ledger of all invocations.\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:45 · 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 curl usage examples\n- 2026-07-02 23:31 · 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 curl usage examples\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"}}