miscsubjects.com
Object Invocation Protocol · protocol specification

Articles and content objects

#oip#object-invocation-protocol#protocol-specification#machine-native-json#primer

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-articles-content-plane
**Machine bundle:** https://miscsubjects.com/api/articles/oip-articles-content-plane/bundle?format=markdown
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

Introduction to OIP and MCP

OIP stands for Object Invocation Protocol. MCP 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. OIP differs from MCP by using plain URLs and receipts with no persistent session: any model that can open a URL can act.

Content articles

The peptide articles are content objects. They carry body, claims, sources, provenance, widgets, bundles, and ledger history.

OIP articles

OIP articles use the same article machinery, but their subject is the build itself. They explain capability objects, not peptide evidence.

Same pattern, different domain

Both article families should be self-explaining. A peptide article explains evidence. An OIP article explains build operation.

Using curl with OIP

To invoke an object using curl, you can use the following command: curl -X POST /api/dispatch -H 'Content-Type: application/json' -d '{"key":"KEY","body":"BODY"}'. You can also use GET requests with the invoke parameter: curl /api/dispatch?invoke=KEY&body=BODY. To get a receipt, use curl /api/dispatch?receipt=inv_ID.

For example, to invoke an object with key my_key and body my_body, you would use: curl -X POST /api/dispatch -H 'Content-Type: application/json' -d '{"key":"my_key","body":"my_body"}'. To get the receipt for an invocation with ID my_inv_ID, you would use: curl /api/dispatch?receipt=my_inv_ID.

Latest clarity reviews (live)

Fresh 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.

  • 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

- gaps named: MCP explanation; Detailed curl usage examples

  • 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

- gaps named: MCP explanation; Detailed curl usage examples

How 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.

1
revision
Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance
1 / 5

Key evidence

5 claims · tier-ranked · API
system
The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.
sources: oip-s3, oip-s4
system
The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.
sources: oip-s1
system
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.
sources: oip-s2, oip-s3
system
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.
sources: oip-s2
system
OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.
sources: oip-s2, oip-s5
Talk to this article
Tap a phone. Ask anything about Articles and content objects. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.

Related articles

Open evidence map →
Oipprotocol rootoipOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curlWhat is MCP?protocol comparisonoip-mcpWhat is GitHub?subsidiary conceptoip-github
Loading more articles…