{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"what-is-tap-go","title":"What Is Tap and Go Delegation","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Token Drop Guides](https://miscsubjects.com/a/oip-token-drop-guides) › **What Is Tap and Go Delegation**\n>\n> **Shelf:** Token Drop Guides · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is Tap and Go Delegation\n\n## §SELF — what-is-tap-go\n\n**What this page is:** A technical description of OIP's one-action delegation mechanism.\n**What it explains:** How Tap and Go delegation works, what it copies, and what security properties it guarantees.\n**Why read it:** To understand how OIP gives models system access without manual configuration or key management.\n\n### What Tap and Go Delegation Is\n\nTap and Go is OIP's (Object Invocation Protocol) delegation mechanism. The name comes from transit cards: you tap your card on a reader and you go through. There is no setup, no configuration, and no login. It is one action.\n\nOIP Tap and Go works the same way: a single copy action gives a model everything it needs to operate a system. The model receives a data drop, reads the capability record inside it, and knows what it can access, what it can do, how to do it, and how to prove it did so. No human is required in the loop.\n\n### Why It Matters\n\nThe problem Tap and Go solves is: how do you give a model access to a system without compromising security? Traditional methods require API keys, manual permission configuration, or shared credentials. Each of these creates risk: keys can leak, permissions are often too broad, and credentials shared between humans and machines are hard to revoke cleanly.\n\nTap and Go replaces all of this with a single, self-describing, scoped, temporary data drop.\n\n### The Key Idea\n\nA Tap and Go drop contains five components:\n\n1. **Object map** — a directory of all available objects. This tells the model what resources exist in the system.\n\n2. **Capability token** — a scoped, expiring proof of permission. The token is unforgeable and carries authority only for specific objects and actions. It is not a master key.\n\n3. **Execution pattern** — the URL patterns for invocation. This tells the model how to construct requests to operate each object.\n\n4. **Receipt rule** — how to prove an action was performed. This defines what evidence the model must produce to demonstrate it executed an invocation.\n\n5. **Protocol bundle** — the full OIP specification in machine-readable form. This lets the model verify that it understands the protocol correctly.\n\nWhen a model receives a Tap and Go drop, it can:\n- Read the object map to discover what objects exist.\n- Read the capability token to learn what it is permitted to do.\n- Read the execution patterns to learn how to invoke objects.\n- Read the receipt rule to learn how to prove its actions.\n- Read the protocol bundle to verify its understanding of OIP.\n\n### What It Guarantees\n\nA Tap and Go drop has four security properties:\n\n- **Self-describing.** The drop contains an explain URL where the model can verify exactly what the token permits. The model does not need external documentation.\n\n- **Scoped.** The token carries limited authority. It grants access only to specific objects and actions, not to the entire system.\n\n- **Temporary.** The token expires. It cannot be used indefinitely.\n\n- **Audited.** Every use of the token is logged. The system records every invocation, when it happened, and by whom.\n\n### Limitations\n\n- The model must be capable of reading and understanding the OIP protocol bundle. A model without this capability cannot use the drop.\n- The drop is only as secure as the channel it travels on. If an attacker intercepts the drop, they gain the token's authority.\n- Revocation requires the system to check token validity on each use. If the system caches token checks, a revoked token may remain usable until the cache clears.\n- There is no guarantee the model will act correctly — only that its actions are scoped, logged, and provable.\n\n### How It Connects to Other Ideas\n\n**Capability-based security.** Tap and Go follows the KeyKOS model: capabilities are unforgeable, scoped, and delegable. A Tap and Go drop is a portable capability bundle.\n\n**Zero-trust architecture.** Tap and Go implements zero-trust principles: never trust, always verify. Every invocation is scoped, logged, and expires. There is no standing authorization.\n\n**API key management.** Tap and Go replaces API keys. An API key grants broad, long-lived access. A Tap and Go token grants narrow, short-lived access with built-in proof of action.\n\n### Sources\n\n- Object Invocation Protocol (OIP) Specification — delegation and capability sections.\n- Hardy, Norman, et al. \"KeyKOS: A Commercially Successful, Capability-Based, Persistent Operating System.\" *Proceedings of the 12th ACM Symposium on Operating Systems Principles*, 1989. (factory pattern and capability model)\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Token Drop Guides shelf](https://miscsubjects.com/a/oip-token-drop-guides) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [How a Model Should Read an OIP Token Drop](https://miscsubjects.com/a/model-reads-token-drop)\n- [How to Write a Token Drop That Models Accept](https://miscsubjects.com/a/token-drop-best-practices)\n- [What Is a Token Drop](https://miscsubjects.com/a/what-is-token-drop)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-tap-go`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-tap-go`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20Tap%20and%20Go%20Delegation`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: conditional orientation + credential last; no execute-mandate inventory.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","token-drops","what-is-tap-go","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-tap-go/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Token Drop Guides (oip-token-drop-guides). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":4,"label":"Token Drop Guides on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: conditional orientation + credential last; no execute-mandate inventory."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:05.376Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"98dccf73c903faef5f02755968e03fb82d9dc9453e4d8139c37d9307c689bfea"},{"ts":"2026-07-15T06:24:53.571Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"98dccf73c903faef5f02755968e03fb82d9dc9453e4d8139c37d9307c689bfea","hash":"a07b844fe46450d9ee6ab422661d63470d5f287088ffc67cdadedf6d2a68b067"},{"ts":"2026-07-17T02:43:40.248Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-tap-go","response":"44 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"a07b844fe46450d9ee6ab422661d63470d5f287088ffc67cdadedf6d2a68b067","hash":"3332095cd4e915600cb1130d1ce5a6b3b9e36948bea84600b80890bc4f3c7ec3"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"3332095cd4e915600cb1130d1ce5a6b3b9e36948bea84600b80890bc4f3c7ec3"},"posted_at":"2026-07-15T04:21:05.376Z","created_at":"2026-07-15T04:21:05.376Z","updated_at":"2026-07-17T02:43:40.248Z","machine":{"shape":"article.machine/v1","slug":"what-is-tap-go","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-tap-go","json":"https://miscsubjects.com/api/articles/what-is-tap-go","bundle":"https://miscsubjects.com/api/articles/what-is-tap-go/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-tap-go/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-tap-go","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-tap-go\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-tap-go\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-tap-go/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"what-is-tap-go\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-tap-go | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-tap-go","json":"/api/articles/what-is-tap-go","markdown":"/api/articles/what-is-tap-go/bundle?format=markdown","skill":"/api/articles/what-is-tap-go/skill","topology":"/api/articles/what-is-tap-go/topology","versions":"/api/articles/what-is-tap-go/revisions","invocations":"/api/articles/what-is-tap-go/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-tap-go","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"b0982a5b639bb975a74750671209c847045adfcb29af30224c596d30e69f346d","object":{"object_type":"article-object","identity":{"id":"article:what-is-tap-go","slug":"what-is-tap-go","title":"What Is Tap and Go Delegation"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/what-is-tap-go","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-tap-go/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-tap-go\ndescription: Apply the What Is Tap and Go Delegation article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is Tap and Go Delegation\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-tap-go). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-tap-go.\n- Read claims and relationships at /api/articles/what-is-tap-go/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\n<!-- hierarchy:nav -- Path: OIP https://miscsubjects.com/a/oip › Thinker Reference https://miscsubjects.com/a/oip-thinker-reference › Token Drop Guides https://miscsubjects.com/a/oip-token-drop-guides › What Is Tap and Go Delegation Shelf: \n\n## Representations\n\n- Human: /a/what-is-tap-go\n- JSON: /api/articles/what-is-tap-go\n- Relationships: /api/articles/what-is-tap-go/topology\n- History: /api/articles/what-is-tap-go/revisions\n"},"json":{"route":"/api/articles/what-is-tap-go","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-tap-go/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","kimi-import","self-explaining","voxel","token-drops","what-is-tap-go","objection-7","oip-edge","what","is","tap","go"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-tap-go/invocations?status=success","failure_events":"/api/articles/what-is-tap-go/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"what-is-tap-go","title":"What Is Tap and Go Delegation","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Token Drop Guides](https://miscsubjects.com/a/oip-token-drop-guides) › **What Is Tap and Go Delegation**\n>\n> **Shelf:** Token Drop Guides · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is Tap and Go Delegation\n\n## §SELF — what-is-tap-go\n\n**What this page is:** A technical description of OIP's one-action delegation mechanism.\n**What it explains:** How Tap and Go delegation works, what it copies, and what security properties it guarantees.\n**Why read it:** To understand how OIP gives models system access without manual configuration or key management.\n\n### What Tap and Go Delegation Is\n\nTap and Go is OIP's (Object Invocation Protocol) delegation mechanism. The name comes from transit cards: you tap your card on a reader and you go through. There is no setup, no configuration, and no login. It is one action.\n\nOIP Tap and Go works the same way: a single copy action gives a model everything it needs to operate a system. The model receives a data drop, reads the capability record inside it, and knows what it can access, what it can do, how to do it, and how to prove it did so. No human is required in the loop.\n\n### Why It Matters\n\nThe problem Tap and Go solves is: how do you give a model access to a system without compromising security? Traditional methods require API keys, manual permission configuration, or shared credentials. Each of these creates risk: keys can leak, permissions are often too broad, and credentials shared between humans and machines are hard to revoke cleanly.\n\nTap and Go replaces all of this with a single, self-describing, scoped, temporary data drop.\n\n### The Key Idea\n\nA Tap and Go drop contains five components:\n\n1. **Object map** — a directory of all available objects. This tells the model what resources exist in the system.\n\n2. **Capability token** — a scoped, expiring proof of permission. The token is unforgeable and carries authority only for specific objects and actions. It is not a master key.\n\n3. **Execution pattern** — the URL patterns for invocation. This tells the model how to construct requests to operate each object.\n\n4. **Receipt rule** — how to prove an action was performed. This defines what evidence the model must produce to demonstrate it executed an invocation.\n\n5. **Protocol bundle** — the full OIP specification in machine-readable form. This lets the model verify that it understands the protocol correctly.\n\nWhen a model receives a Tap and Go drop, it can:\n- Read the object map to discover what objects exist.\n- Read the capability token to learn what it is permitted to do.\n- Read the execution patterns to learn how to invoke objects.\n- Read the receipt rule to learn how to prove its actions.\n- Read the protocol bundle to verify its understanding of OIP.\n\n### What It Guarantees\n\nA Tap and Go drop has four security properties:\n\n- **Self-describing.** The drop contains an explain URL where the model can verify exactly what the token permits. The model does not need external documentation.\n\n- **Scoped.** The token carries limited authority. It grants access only to specific objects and actions, not to the entire system.\n\n- **Temporary.** The token expires. It cannot be used indefinitely.\n\n- **Audited.** Every use of the token is logged. The system records every invocation, when it happened, and by whom.\n\n### Limitations\n\n- The model must be capable of reading and understanding the OIP protocol bundle. A model without this capability cannot use the drop.\n- The drop is only as secure as the channel it travels on. If an attacker intercepts the drop, they gain the token's authority.\n- Revocation requires the system to check token validity on each use. If the system caches token checks, a revoked token may remain usable until the cache clears.\n- There is no guarantee the model will act correctly — only that its actions are scoped, logged, and provable.\n\n### How It Connects to Other Ideas\n\n**Capability-based security.** Tap and Go follows the KeyKOS model: capabilities are unforgeable, scoped, and delegable. A Tap and Go drop is a portable capability bundle.\n\n**Zero-trust architecture.** Tap and Go implements zero-trust principles: never trust, always verify. Every invocation is scoped, logged, and expires. There is no standing authorization.\n\n**API key management.** Tap and Go replaces API keys. An API key grants broad, long-lived access. A Tap and Go token grants narrow, short-lived access with built-in proof of action.\n\n### Sources\n\n- Object Invocation Protocol (OIP) Specification — delegation and capability sections.\n- Hardy, Norman, et al. \"KeyKOS: A Commercially Successful, Capability-Based, Persistent Operating System.\" *Proceedings of the 12th ACM Symposium on Operating Systems Principles*, 1989. (factory pattern and capability model)\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Token Drop Guides shelf](https://miscsubjects.com/a/oip-token-drop-guides) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [How a Model Should Read an OIP Token Drop](https://miscsubjects.com/a/model-reads-token-drop)\n- [How to Write a Token Drop That Models Accept](https://miscsubjects.com/a/token-drop-best-practices)\n- [What Is a Token Drop](https://miscsubjects.com/a/what-is-token-drop)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-tap-go`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-tap-go`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20Tap%20and%20Go%20Delegation`\n\n\n---\n\n## Where OIP does this differently (required edge)\n\nOIP difference: conditional orientation + credential last; no execute-mandate inventory.\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","token-drops","what-is-tap-go","objection-7","oip-edge"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-tap-go/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Token Drop Guides (oip-token-drop-guides). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":4,"label":"Token Drop Guides on shelf"},{"type":"note","title":"OIP edge","text":"OIP difference: conditional orientation + credential last; no execute-mandate inventory."}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":1,"contributions":[],"provenance":[{"ts":"2026-07-15T04:21:05.376Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"98dccf73c903faef5f02755968e03fb82d9dc9453e4d8139c37d9307c689bfea"},{"ts":"2026-07-15T06:24:53.571Z","model":"grok-build","action":"objection-patch","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"98dccf73c903faef5f02755968e03fb82d9dc9453e4d8139c37d9307c689bfea","hash":"a07b844fe46450d9ee6ab422661d63470d5f287088ffc67cdadedf6d2a68b067"},{"ts":"2026-07-17T02:43:40.248Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-tap-go","response":"44 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"a07b844fe46450d9ee6ab422661d63470d5f287088ffc67cdadedf6d2a68b067","hash":"3332095cd4e915600cb1130d1ce5a6b3b9e36948bea84600b80890bc4f3c7ec3"}],"energy":{"passes":3,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"grok-build":1,"owner":1},"head":"3332095cd4e915600cb1130d1ce5a6b3b9e36948bea84600b80890bc4f3c7ec3"},"posted_at":"2026-07-15T04:21:05.376Z","created_at":"2026-07-15T04:21:05.376Z","updated_at":"2026-07-17T02:43:40.248Z","machine":{"shape":"article.machine/v1","slug":"what-is-tap-go","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-tap-go","json":"https://miscsubjects.com/api/articles/what-is-tap-go","bundle":"https://miscsubjects.com/api/articles/what-is-tap-go/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":1,"objections_url":"https://miscsubjects.com/api/articles/what-is-tap-go/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-tap-go","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-tap-go\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-tap-go\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-tap-go/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"what-is-tap-go\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-tap-go | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-tap-go","json":"/api/articles/what-is-tap-go","markdown":"/api/articles/what-is-tap-go/bundle?format=markdown","skill":"/api/articles/what-is-tap-go/skill","topology":"/api/articles/what-is-tap-go/topology","versions":"/api/articles/what-is-tap-go/revisions","invocations":"/api/articles/what-is-tap-go/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-tap-go","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"b0982a5b639bb975a74750671209c847045adfcb29af30224c596d30e69f346d"}}}