{"slug":"oip-tap-go","title":"Tap & Go delegation","body":"## What Tap & Go is\n\nOIP 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.\n\n## What it replaces\n\nTap & 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.\n\n## Scope\n\nA 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.\n\n## OIP and MCP: A Comparison\n\nMCP 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.\n\n### OIP (Object Invocation Protocol)\n\nOIP 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.\n\nTo 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.\n\nEvery 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.\n\n### MCP (Model Context Protocol)\n\nMCP 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.\n\n### Key Differences Summarized\n\n*   **Session:** OIP has no session. MCP uses a persistent session.\n*   **Invocation:** OIP uses plain URLs for invocation. MCP uses server calls within a session.\n*   **Purpose:** OIP is for general object invocation and delegation. MCP is for providing context and tools to AI models.\n*   **Mechanism:** OIP relies on simple HTTP requests and receipts. MCP relies on a connected server exposing capabilities.\n## Latest clarity reviews (live)\n\nFresh 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.\n\n- 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\n  - gaps named: MCP explanation; Detailed comparison between OIP and MCP\n- 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\n  - gaps named: MCP explanation; Detailed comparison between OIP and MCP\n\nHow 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.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"model":null,"ledger":null,"embeds":[],"widgets":[{"type":"stat","value":1,"label":"revision"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"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.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"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.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"primer","count":1,"metric":"revision","primer":"oip-tap-go","version":1,"author_model":"gemini/gemini-2.5-flash","revision_source":"revision"},"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-03T01:49:03-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-03T01:49:03-07:00"}