miscsubjects.com
Object Invocation Protocol · protocol specification

Machine-native JSON

#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-machine-json
**Machine bundle:** https://miscsubjects.com/api/articles/oip-machine-json/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 Machine-native JSON

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

Why JSON matters

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

Prose and JSON

The prose article helps a human understand the system. The JSON bundle lets a model operate the same system. Both describe the same object.

Rule

If a machine has to infer a route, key, argument shape, or proof path from vibes, the object is not self-explaining enough.

What is MCP?

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 vs MCP

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

Using OIP with curl

The build operation can be performed using curl, with the exact route shape being POST /api/dispatch or GET /api/dispatch?invoke=KEY&body=....

Subsidiary Concepts

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

Conclusion

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

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:36 · 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: API; CLI; REST; JSON

  • 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

- gaps named: MCP explanation; Detailed comparison between OIP and MCP

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 Machine-native JSON. 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-goOip 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-machine-json · 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:59 · 0 tok · virtual-oip
verify chain →
Live ledger · 9 payloads · 6 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 02:36 · t_a4dst25j
PROTOCOL_RUN dispatch · 2026-07-03 02:36 · t_a4dst25j
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 02:36 · t_2q55qekx
PROTOCOL_RUN dispatch · 2026-07-03 00:13 · t_iauelr6b
PROTOCOL_RUN dispatch · 2026-07-03 00:13 · t_iauelr6b
OIP_ARTICLE_REVISE oip-review · HTTP 200 · 2026-07-03 00:13 · t_eb5qhv1r
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-machine-json · GET /api/articles/oip-machine-json · GET /api/articles/oip-machine-json/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…