miscsubjects.com
Object Invocation Protocol · protocol specification

OIP Object Model

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

What an OIP Object Is

An OIP (Object Invocation Protocol) object is one thing the miscsubjects.com build can read or do. Think of it as a row in a directory. Directory rows are the objects. A content article is an object. A prompt row is an object. A shell command row is an object. A deploy row is an object. A receipt is an object.

OIP and MCP

OIP (Object Invocation Protocol) helps systems talk to each other. It lets you use simple web links to make things happen. This is like "Tap & Go". You just use a link and it works. OIP differs from MCP (Model Context Protocol).

MCP is an open standard. An AI model connects to an MCP server over a session. A server is a computer program that provides services to other programs. The MCP server exposes tools, resources, and prompts. The model can call these. MCP is not a content-management system.

OIP uses plain URLs (Uniform Resource Locators). A URL is a web address. OIP has no persistent session. Any model that can open a URL can act. OIP uses receipts to confirm actions. MCP provides a structured environment for AI actions. It allows models to access specific tools through a persistent connection.

What Every Object Must Explain

Every OIP object needs a clear contract. This contract explains what the object is. It tells you when to use it. It shows what input it accepts. It explains how to run it. It describes what output proves it worked. It also tells you where to look when it fails.

Human and Machine Views

An OIP object has two main views. The human view is an article. It explains the object in simple words. The machine view is a document. It gives the exact invocation shape. This includes the URL to call it. For example, a machine document might list /api/dispatch as the endpoint. An endpoint is a specific web address for a server to receive requests. A JSON (JavaScript Object Notation) bundle gives a model this same map. JSON is a way to store and exchange data. It uses structured data. This structured data can include a URL for comparing OIP to MCP, such as /a/oip-vs-mcp.

How to Use an OIP Object

You invoke an OIP object. To invoke means to call or activate it. You can use a POST request to /api/dispatch. A POST request sends data to a server. You send a key and a body in this request. Or, you can use a GET request to /api/dispatch. A GET request asks for data from a server. For GET, you add invoke=KEY and body=... to the URL.

The Ledger and Receipts

Every time an OIP object is invoked, the action is recorded. This record goes into an append-only ledger. An append-only ledger is a list of records that only grows. New records are added to the end. You cannot change old records. After an invocation, you get a receipt. A receipt is proof that your action happened. You can find your receipt at /api/dispatch?receipt=inv_ID. inv_ID is the unique identifier for your invocation.

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 00:41 · 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; ledger

  • 2026-07-02 23:17 · 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; ledger

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 Object Model. 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-object-model · 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 22:57 · 0 tok · virtual-oip
verify chain →
Live ledger · 21 payloads · 10 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 02:54 · t_jlv771h0
PROTOCOL_RUN dispatch · 2026-07-03 02:54 · t_jlv771h0
delivery.delivered blooio · 2026-07-03 02:54
delivery.delivered blooio · 2026-07-03 02:54
NOTIFY_OWNER dispatch · 2026-07-03 02:54 · t_50mbyjkw
delivery.sent blooio · 2026-07-03 02:54
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-object-model · GET /api/articles/oip-object-model · GET /api/articles/oip-object-model/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…