miscsubjects.com
Object Invocation Protocol · protocol specification

Tap & Go delegation

#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-tap-go
**Machine bundle:** https://miscsubjects.com/api/articles/oip-tap-go/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 Tap & Go is

OIP stands for Object Invocation Protocol. It lets any computer program act on objects. Tap & Go is the copy primitive for OIP. A 'drop' is a copied item. This drop carries everything needed to use an OIP object. It includes the credential. It holds the object map. It defines the search path. It sets the execute shape. It also includes the receipt rule.

What it replaces

Tap & Go makes things simpler. It replaces hand-assembling many parts. These parts include a token, a map, a bundle, and a link. A token is a small piece of data. It proves your identity or permission to do something. An AI model receives one drop. It reads the object map. It invokes only the object it needs for its task. It proves its work by showing a receipt.

Scope

A broad owner drop can operate the entire build. The build is miscsubjects.com. Directory rows are the objects. A row-scoped drop can operate only one specific capability. The link itself explains what actions it is allowed to do.

OIP and MCP: A Comparison

MCP stands for Model Context Protocol. It is an open standard. An AI model connects to an MCP server. A server is a computer program or device that provides a service to other computer programs or devices. The server gives the model tools, resources, and prompts. The model can use these to do its work. Both OIP and MCP help AI models interact with other systems. They do this in different ways.

OIP (Object Invocation Protocol)

OIP uses plain URLs. A URL (Uniform Resource Locator) is a web address, like https://miscsubjects.com/api/dispatch. It does not use a persistent session. This means there is no ongoing connection between the model and the server. Any model that can open a URL can act. It does not need a special connection.

To invoke an object, a model sends a request to a URL. For example, it can use POST /api/dispatch {key, body}. Or it can use GET /api/dispatch?invoke=KEY&body=.... The /api/dispatch part is an endpoint. An endpoint is a specific URL where a server receives requests. It is a specific address for a service. API stands for Application Programming Interface. It is a set of rules that lets different software programs talk to each other.

Every action creates a record. This record is called an invocation. All invocations land in an append-only ledger. A receipt is proof of an action. You can find a receipt at /api/dispatch?receipt=inv_ID. OIP is for invoking any kind of object. These objects are the directory rows on miscsubjects.com.

MCP (Model Context Protocol)

MCP uses a persistent session. An AI model connects to an MCP server. This connection stays open for a period. The MCP server exposes tools, resources, and prompts. The model can call these during its session. MCP is an open standard. It helps AI models get the context they need to work. MCP is NOT a content-management system. It does not store articles or files. It focuses on providing a dynamic environment for an AI model.

Key Differences Summarized

Session: OIP has no session. MCP uses a persistent session. Invocation: OIP uses plain URLs for invocation. MCP uses server calls within a session. Purpose: OIP is for general object invocation and delegation. MCP is for providing context and tools to AI models. Mechanism: OIP relies on simple HTTP requests and receipts. MCP relies on a connected server exposing capabilities.

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:36 · 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 explanation; Detailed comparison between OIP and MCP

  • 2026-07-02 23:25 · 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 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 Tap & Go delegation. 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-modelMachine-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-tap-go · posted 2026-07-02 · updated 2026-07-03
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-03 00:28 · 0 tok · virtual-oip
verify chain →
Live ledger · 21 payloads · 9 turns
recent activity · inspect
delivery.delivered blooio · 2026-07-03 02:52
PROTOCOL_RUN dispatch · 2026-07-03 02:52 · t_8w23bg1e
PROTOCOL_RUN dispatch · 2026-07-03 02:52 · t_8w23bg1e
delivery.delivered blooio · 2026-07-03 02:52
NOTIFY_OWNER dispatch · 2026-07-03 02:52 · t_5ryzkbs8
delivery.sent blooio · 2026-07-03 02:52
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-tap-go · GET /api/articles/oip-tap-go · GET /api/articles/oip-tap-go/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…