miscsubjects.com
Object Invocation Protocol · protocol specification

Tap & Go

#oip#object-invocation-protocol#protocol-specification#machine-native-json#dynamic

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

Tap & Go is a way to invoke objects on miscsubjects.com using scoped drops. A drop is a small piece of data that can be used to invoke an object. An object is a thing that can be invoked, like a function or a piece of code. A server is a computer that hosts objects and handles invocations. A token is a special code that is used to authenticate and authorize invocations.

Why does the OIP build care about Tap & Go?

The OIP build cares about Tap & Go because it allows for easy and flexible invocation of objects. The OIP build uses a REST (Representational State of Resource) API, which is a way of interacting with servers using plain URLs. A URL (Uniform Resource Locator) is a web address that can be used to access a resource. The OIP build also uses JSON (JavaScript Object Notation), which is a way of formatting data as text.

How to see or use Tap & Go live with curl

To use Tap & Go with curl, you can send a POST request to /api/dispatch with a JSON body containing the key and body of the invocation. For example: curl -X POST -H 'Content-Type: application/json' -d '{"key":"my_key","body":"my_body"}' https://miscsubjects.com/api/dispatch This will invoke the object with the specified key and body, and return a receipt that can be used to verify the invocation.

How Tap & Go relates to MCP

Tap & Go is similar to MCP (Model Context Protocol), which is an open standard for connecting AI models to servers. However, unlike MCP, Tap & Go does not require a persistent session or a complex setup process. Instead, Tap & Go uses plain URLs and receipts to invoke objects, making it easier to use and more flexible. MCP is a more complex protocol that is designed for more advanced use cases, such as machine learning and natural language processing.

Where the proof lives

The proof of Tap & Go invocations lives in the ledger, which is a record of all invocations that have been made on the server. Each invocation is assigned a unique ID, which can be used to retrieve the receipt for that invocation. The receipt contains information about the invocation, such as the key and body that were used, and the result of the invocation. To retrieve a receipt, you can send a GET request to /api/dispatch with the receipt ID as a parameter. For example: curl -X GET https://miscsubjects.com/api/dispatch?receipt=my_receipt_id This will return the receipt for the specified invocation, which can be used to verify that the invocation was successful.

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:47 · 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: Detailed explanation of MCP; Comparison of OIP and MCP in different scenarios

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
version
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. 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-tap-and-go · 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:06 · 0 tok · virtual-oip
verify chain →
Live ledger · 8 payloads · 5 turns
recent activity · inspect
PROTOCOL_RUN dispatch · 2026-07-03 02:47 · t_fczqi6q4
PROTOCOL_RUN dispatch · 2026-07-03 02:47 · t_fczqi6q4
OIP_ARTICLE_REVIEW oip-review · HTTP 200 · 2026-07-03 02:47 · t_i9pugdya
PROTOCOL_RUN dispatch · 2026-07-03 00:30 · t_r1mf9hfz
PROTOCOL_RUN dispatch · 2026-07-03 00:30 · t_r1mf9hfz
OIP_ARTICLE_WRITE oip-review · HTTP 200 · 2026-07-03 00:30 · t_st3zx356
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-tap-and-go · GET /api/articles/oip-tap-and-go · GET /api/articles/oip-tap-and-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…