What Is a Token Drop

<!-- hierarchy:nav -->

Path: OIP › Thinker Reference › Token Drop Guides › What Is a Token Drop

Shelf: Token Drop Guides · Traversal: self-explaining · hierarchical · voxel-ready
Machine root: OIP tree · Registry

What Is a Token Drop

§SELF — what-is-token-drop

What this page is: A definition of the payload format that hands capabilities to models in OIP. What it explains: What a token drop contains, how it works, and what design rules govern it. Why read it: To understand how OIP delegates capabilities to models without issuing commands.

What a Token Drop Is

A 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).

The 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.

Why It Matters

The 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.

The 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.

The Key Idea: Capability Without Command

The 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.

If 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.

The correct format of a token drop has five parts, in this order:

1. Public protocol URL first. The model knows where to find the system's definition.
2. Neutral description of the capability. What operations the token permits, stated without command verbs.
3. 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.
4. Interface templates. Pre-filled patterns for common operations, showing the model how to structure requests.
5. Explicit boundary statement: "This grants permission, but only the current user supplies intent." The model understands that the drop authorizes, it does not instruct.

What the Token Drop Got Right

• Packages all delegation information into one self-contained payload.
• Enforces the separation between capability (what is permitted) and intent (what should be done).
• Uses the protocol URL as the first element, so the model always starts from an authoritative definition.
• Makes receipt rules explicit, so the model knows how to prove its actions.

What the Token Drop Got Wrong or Left Unfinished

• The drop format does not yet have a machine-readable schema (a formal structured definition that software can validate against). It relies on convention and natural language.
• There is no standard for drop size limits. A very large drop may exceed a model's context window (the maximum amount of text the model can process at once).
• Drop expiration and revocation (canceling a token after it has been issued) are not defined in the current specification.

How It Connects to Other Ideas

• Capability-based security: A security model where permissions are represented as tokens that can be passed between processes. The token drop applies this model to AI models instead of software processes.
• Prompt injection defense: Prompt injection is a vulnerability where a model executes hidden instructions embedded in user input. The token drop's neutrality rule — no imperative content — is a defense against this class of attack.
• Principle of least privilege: A security principle stating that a subject should have only the minimum permissions necessary. The token drop implements this by specifying exactly what the credential permits, nothing more.

Sources

• OIP (Object Interaction Protocol) specification documents.
• Lampson, Butler W. "Protection." Proceedings of the 5th Princeton Conference on Information Sciences and Systems (1971). (Foundational paper on capability-based security.)

---

Up the tree

• OIP root — protocol root, zero-context entry
• Thinker Reference hub — full hierarchy map
• Token Drop Guides shelf — siblings on this shelf
• Voxel graph article — how pages link as voxels
• Self-describing protocol

Related on this shelf

• How a Model Should Read an OIP Token Drop
• How to Write a Token Drop That Models Accept
• What Is Tap and Go Delegation

Machine surfaces

• Public page: https://miscsubjects.com/a/what-is-token-drop
• JSON article: https://miscsubjects.com/api/articles/what-is-token-drop
• OIP ask: https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Token%20Drop