Object Invocation Protocol · protocol specification

OIP — Token Drop Guides

#oip#shelf#token-drops#hierarchy#self-explaining#kimi-import

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification · traversal JSON in-band
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-token-drop-guides
**This page as JSON:** https://miscsubjects.com/api/articles/oip-token-drop-guides
**Machine bundle:** https://miscsubjects.com/api/articles/oip-token-drop-guides/bundle?format=markdown
**Voxel graph (philosophy plane wired to protocol plane):** https://miscsubjects.com/api/articles/oip/voxels
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

<!-- hierarchy:shelf -->

Path: OIPThinker ReferenceToken Drop Guides

Shelf size: 4 self-explaining articles

Token Drop Guides

§SELF — oip-token-drop-guides

What this page is: the shelf index for Token Drop Guides in the OIP Thinker Reference tree. What it explains: every article on this shelf, linked for traversal. Why read it: enter one conceptual neighborhood without scanning the full hub.

Articles on this shelf

Up the tree

Sibling shelves

oip-token-drop-guides · condition map

Evidence map

Hover a node — its path lights up. Click to open the article.

Full map →
4
articles
Talk to this article
Tap a phone. Ask anything about OIP — Token Drop Guides. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.
oip-token-drop-guides · posted 2026-07-15 · updated 2026-07-15
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head 1c1d4843979b3906
write kimi-agent-import · 2026-07-15 04:20 · 0 tok · 1c1d4843979b
verify chain →
Live ledger · 14 payloads · 4 turns
recent activity · inspect
ARTICLE_CREATED automation · HTTP 200 · 2026-07-15 04:20 · t_article_s4kc6gjk
delivery.delivered blooio · 2026-07-14 21:22
delivery.delivered blooio · 2026-07-14 21:22
delivery.sent blooio · 2026-07-14 21:22
delivery.sent blooio · 2026-07-14 21:22
BLOOIO_SEND_CHAT_MESSAGE blooio · 2026-07-14 21:22 · t_rjl5ybz7
view full ledger & cards →
OIP REST + ledger
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}
Loading more articles…