miscsubjects.com
Object Invocation Protocol · protocol specification

Self-test and proof

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

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

Self-test

The self-test is the build's executable spec. It asks natural-language questions through the real route, such as POST /api/dispatch with a JSON (JavaScript Object Notation) body, and scores the actual answer. A server is a computer that provides services, and in this case, it processes the self-test requests. A token is not required for this process.

Proof

A feature is not proven by a description, a static page, or a successful syntax check. OIP proof is a real invocation, such as a GET request to /api/dispatch?invoke=KEY&body=..., and a real receipt or ledger line. A receipt is a confirmation of an invocation, and a ledger is a record of all invocations, which can be accessed through a URL (Uniform Resource Locator). An endpoint is a URL that an application can use to interact with a server, and in this case, /api/dispatch is the endpoint used for invocations.

Regression

If a change lowers the self-test score, the change is a regression. The score is tied to build version and commit history. Directory rows are the objects that can be invoked through the /api/dispatch endpoint, and they are used to organize and store the data. The build operation can be performed using curl, a command-line tool, by sending a POST request to /api/dispatch with the required key and body.

Comparison to MCP

While MCP requires a persistent session and a specific server setup, OIP uses plain URLs and receipts, making it more accessible and easier to use. MCP is not a content-management system, but rather a protocol for AI models to interact with servers. OIP, on the other hand, provides a simpler and more straightforward way of invoking objects and tracking changes through the ledger.

Subsidiary Concepts

Subsidiary concepts that need their own OIP articles include Tap & Go, which is not relevant in this context, and a more detailed explanation of the ledger and receipt system.

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:52 · model @cf/meta/llama-3.3-70b-instruct-fp8-fast · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 6/10

- gaps named: Tap & Go; ledger and receipt system

  • 2026-07-02 23:34 · model @cf/meta/llama-3.3-70b-instruct-fp8-fast · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 6/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 Self-test and proof. 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-self-test-proof · 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:01 · 0 tok · virtual-oip
verify chain →
Live ledger · 9 payloads · 6 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 02:52 · t_5g604hj9
PROTOCOL_RUN dispatch · 2026-07-03 02:52 · t_5g604hj9
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 02:52 · t_58s5kl9r
PROTOCOL_RUN dispatch · 2026-07-03 00:39 · t_jj8yjcsx
PROTOCOL_RUN dispatch · 2026-07-03 00:39 · t_jj8yjcsx
OIP_ARTICLE_REVISE oip-review · HTTP 200 · 2026-07-03 00:39 · t_sf9ceeu6
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-self-test-proof · GET /api/articles/oip-self-test-proof · GET /api/articles/oip-self-test-proof/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…