miscsubjects.com
Object Invocation Protocol · protocol specification

OIP Operating Playbook

#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-operating-playbook
**Machine bundle:** https://miscsubjects.com/api/articles/oip-operating-playbook/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

OIP stands for Object Invocation Protocol, a protocol that allows models to invoke objects using plain URLs and receipts with no persistent session. This means any model that can open a URL can act.

The Playbook

Use the same path for every task: orient, ask, read, invoke, prove, repair.

Do not Guess

If the object key, argument shape, route, or permission is unclear, ask OIP for the object or read the object document. Guessing creates false work and bad receipts. For example, you can use the /api/dispatch route to invoke an object by sending a POST request with the object key and body, or a GET request with the invoke and body parameters. A server is a computer that hosts and manages resources, and in this case, it hosts the OIP objects. A token is not required for OIP, as it uses plain URLs and receipts.

Close the Loop

Every useful action ends with proof. Every failed action starts a repair path from the receipt. The receipt is stored in an append-only ledger, which is a record of all invocations, and can be accessed using the /api/dispatch?receipt=inv_ID URL. An endpoint is a URL that an object can be invoked at, and in this case, the endpoint is /api/dispatch. The ledger is a fundamental component of OIP, as it provides a record of all actions and allows for proof and repair.

Comparison to MCP

OIP differs from MCP (Model Context Protocol), an open standard where an AI model connects to an MCP server over a session, in that OIP uses plain URLs and receipts with no persistent session. MCP is not a content-management system, but rather a protocol that exposes tools, resources, and prompts that models can call. Directory rows are the objects in the OIP system, and they can be invoked using the /api/dispatch route. Tap & Go is not a relevant concept in this context.

Using the Playbook with Curl

The build operation can be performed using curl, by sending a POST request to the /api/dispatch route with the object key and body, or a GET request with the invoke and body parameters. For example, curl -X POST /api/dispatch -H 'Content-Type: application/json' -d '{"key":"object_key","body":"object_body"}' or curl -X GET '/api/dispatch?invoke=object_key&body=object_body'.

Subsidiary Concepts

Subsidiary concepts that need their own OIP articles include the MCP protocol, the concept of directory rows, and the use of receipts and ledgers in OIP.

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:59 · 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 protocol; directory rows; receipts and ledgers in OIP

  • 2026-07-02 23:35 · 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; Tap & Go; directory rows; dispatch

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 OIP Operating Playbook. 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
oip-operating-playbook · posted 2026-07-02 · updated 2026-07-02
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-02 23:05 · 0 tok · virtual-oip
verify chain →
Live ledger · 9 payloads · 6 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 02:59 · t_mzrgd5vk
PROTOCOL_RUN dispatch · 2026-07-03 02:59 · t_mzrgd5vk
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 02:59 · t_byqtmqzk
PROTOCOL_RUN dispatch · 2026-07-03 00:47 · t_u6i55ikk
PROTOCOL_RUN dispatch · 2026-07-03 00:47 · t_u6i55ikk
OIP_ARTICLE_REVISE oip-review · HTTP 200 · 2026-07-03 00:47 · t_ac17uwci
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-operating-playbook · GET /api/articles/oip-operating-playbook · GET /api/articles/oip-operating-playbook/bundle?format=markdown
root tree GET /api/dispatch?map=1&format=markdown
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}
ledger provenance · sources · voxels · live ledger
Loading more articles…