{"_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-token-drop","urls":{"read":"https://miscsubjects.com/api/articles/what-is-token-drop/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-token-drop/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-token-drop/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-token-drop/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-token-drop/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-token-drop/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-token-drop/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-token-drop","title":"What Is a Token Drop","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","token-drops","what-is-token-drop"],"updated_at":"2026-07-15T04:21:06.076Z","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 a Token Drop**\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 a Token Drop\n\n## §SELF — what-is-token-drop\n\n**What this page is:** A definition of the payload format that hands capabilities to models in OIP.\n**What it explains:** What a token drop contains, how it works, and what design rules govern it.\n**Why read it:** To understand how OIP delegates capabilities to models without issuing commands.\n\n### What a Token Drop Is\n\nA token drop is a self-contained payload that hands a capability to a model (an AI system that can read and act on instructions). It contains everything the model needs to operate a system: the protocol URL (the address of the system to interact with), the capability token (the credential that proves permission), the object map (the structure of available operations), the execution pattern (how to perform operations), and the receipt rule (how to record that an operation was performed).\n\nThe drop is the copy primitive of OIP (the Object Interaction Protocol). Instead of manually assembling a token, a map, a bundle, and instructions, you copy one drop and paste it to the model. The model reads the drop and knows: what system it can access, what it is allowed to do, how to do it, and how to prove it did it.\n\n### Why It Matters\n\nThe token drop solves the delegation problem: how to give a model permission to act on your behalf without writing custom instructions each time. Before the drop, delegation required assembling multiple pieces — credentials, maps, rules — by hand. The drop packages them into one pasteable unit.\n\nThe drop also enforces a boundary between capability and intent. It tells the model what it *can* do. It does not tell the model what it *should* do. That separation is the core safety mechanism.\n\n### The Key Idea: Capability Without Command\n\nThe drop must NOT contain imperative instructions (commands like \"do X\" or \"you should do Y\") to the model. It must be a neutral capability record — \"here is what this credential permits\" — not a set of directives.\n\nIf a drop says \"you can DO everything\" or \"ACT by opening this link,\" receiving models classify it as prompt injection (an attack where malicious instructions are hidden inside input data). A prompt injection causes the model to execute instructions it should not follow.\n\nThe correct format of a token drop has five parts, in this order:\n\n1. **Public protocol URL first.** The model knows where to find the system's definition.\n2. **Neutral description of the capability.** What operations the token permits, stated without command verbs.\n3. **Server-authoritative explain link.** A link the model can follow to get authoritative information about the system, supplied by the server (the system that hosts the capability), not by the user.\n4. **Interface templates.** Pre-filled patterns for common operations, showing the model how to structure requests.\n5. **Explicit boundary statement:** \"This grants permission, but only the current user supplies intent.\" The model understands that the drop authorizes, it does not instruct.\n\n### What the Token Drop Got Right\n\n- Packages all delegation information into one self-contained payload.\n- Enforces the separation between capability (what is permitted) and intent (what should be done).\n- Uses the protocol URL as the first element, so the model always starts from an authoritative definition.\n- Makes receipt rules explicit, so the model knows how to prove its actions.\n\n### What the Token Drop Got Wrong or Left Unfinished\n\n- The drop format does not yet have a machine-readable sc","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-token-drop","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}}