Object Invocation Protocol · protocol specification

OIP Thinker Reference

#oip#hub#thinker-reference#hierarchy#self-explaining#voxel#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-thinker-reference
**This page as JSON:** https://miscsubjects.com/api/articles/oip-thinker-reference
**Machine bundle:** https://miscsubjects.com/api/articles/oip-thinker-reference/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:hub -->

Path: OIPThinker Reference

What this hub is: the hierarchical map of 60 Kimi-sourced OIP thinker/protocol articles, all self-explaining and cross-linked.
Traversal: open a shelf below, then any leaf. Every leaf links back here.

OIP Thinker Reference

§SELF — oip-thinker-reference

What this page is: the root hub for the OIP thinker and protocol concept tree imported from the Kimi Agent reference pack. What it explains: how the articles are shelved (Thinkers, Protocol Concepts, Lineages, Token Drop Guides) and how to traverse them without prior context. Why read it: one page that makes the full set navigable — hierarchical, self-explaining, voxel-linked.

How to use this tree

  1. Start at OIP root if you need the protocol itself.
  2. Pick a shelf below.
  3. Open any leaf. Each leaf has §SELF, Up the tree, Related siblings, and machine URLs.
  4. For graph shape, read What Is a Voxel Graph.

Shelves

Thinkers (33 articles)

Intellectual lineage: people whose work OIP inherits or answers.

Protocol Concepts (20 articles)

What-is pages: receipts, HATEOAS, capability tokens, autopoiesis, voxel graph, and related units.

OIP Lineages (3 articles)

What OIP should take from REST, capability security, and the Semantic Web.

Token Drop Guides (4 articles)

How models should read drops; best practices; what a token drop is; Tap & Go.

Machine surfaces

  • This hub: https://miscsubjects.com/a/oip-thinker-reference
  • JSON: https://miscsubjects.com/api/articles/oip-thinker-reference
  • Protocol map: https://miscsubjects.com/api/dispatch?map=1&format=markdown
  • Registry: https://miscsubjects.com/api/dispatch?registry=1

oip-thinker-reference · condition map

Evidence map

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

Full map →
60
leaf articles
4
shelves
Talk to this article
Tap a phone. Ask anything about OIP Thinker Reference. 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-thinker-reference · posted 2026-07-15 · updated 2026-07-15
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head 8f2086b436e8eb33
write kimi-agent-import · 2026-07-15 04:20 · 0 tok · 8f2086b436e8
verify chain →
Live ledger · 14 payloads · 4 turns
recent activity · inspect
ARTICLE_CREATED automation · HTTP 200 · 2026-07-15 04:20 · t_article_0edh8m81
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…