{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"what-is-tap-go","urls":{"read":"https://miscsubjects.com/api/articles/what-is-tap-go/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/what-is-tap-go/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-tap-go/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-tap-go/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/what-is-tap-go/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-tap-go/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/what-is-tap-go/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"what-is-tap-go","title":"What Is Tap and Go Delegation","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","token-drops","what-is-tap-go"],"updated_at":"2026-07-15T04:21:05.376Z","body_excerpt":"<!-- 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 c","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"what-is-tap-go","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":0,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}