miscsubjectsAI governance
Object Invocation Protocol · protocol specification

OIP Thinker Reference

· · 3 min read

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: OIP › Thinker 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.

§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
60
leaf articles
4
shelves

Latest from the journal

Most recent pieces, site-wide

All articles →
What $10.75 bought: 43 owned business records, five receipts, and the…posted 2026-07-28federated-object-proofThe meter reads $0.00 on 168,852 of 170,317 invocations. That is the w…posted 2026-07-28buy-outcomes-not-subscriptionsPalantir Foundry's Ontology and Object Models: A Canonical Surveyposted 2026-07-28palantir-foundry-ontology-modelsFederated objects as a metered utility: the product specposted 2026-07-28federated-objects-as-metered-utilityThe object ledger: one grammar for every record, a signed receipt for…posted 2026-07-28object-ledger-evidence-graph-spec

Related articles

oip-thinker-reference · condition map

Open evidence map →
Oipprotocol rootoipPhilosophy Protocolfoundation protocolphilosophy-protocolPhilosophy Source Documentationsource corpusphilosophy-source-documentationOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curl
oip-thinker-reference · posted 2026-07-15 · updated 2026-07-17 · kimi-agent-import
Ledger API & provenance
Provenance · 2 model passes · tokens/cost unrecorded · 2 models
chain head ba2e8276d424ac6b
write kimi-agent-import · 2026-07-15 04:20 · tokens unrecorded · 8f2086b436e8
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · ba2e8276d424
verify chain →
Live ledger · 46 payloads · 0 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 01:04
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 17:50
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 17:50
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 05:46
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 03:49
JCI_TRAFFIC jci · HTTP 200 · 2026-07-27 22:14
view full ledger & cards →
OIP REST + ledger
read GET /a/oip-thinker-reference · GET /api/articles/oip-thinker-reference · GET /api/articles/oip-thinker-reference/bundle?format=markdown
root tree GET /api/dispatch?map=1&format=markdown
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"}
ledger provenance · sources · voxels · live ledger