miscsubjectsAI governance
Object Invocation Protocol · protocol specification

OIP system: OPOS

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-system-opos
**This page as JSON:** https://miscsubjects.com/api/articles/oip-system-opos
**Machine bundle:** https://miscsubjects.com/api/articles/oip-system-opos/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.

OPOS

A generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.

This page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.

Kind: core. Capabilities: 3. Machine system map: /api/dispatch?map=OPOS&format=markdown. Root: /a/oip.

Operations

OPOS_ROOT

Read the whole build as OPOS, one self-explaining Object Protocol Operating System containing identity, object classes, Tap & Go routes, root articles, live inventory, audit, comparison field, evidence boundaries, and feedback loop. Arguments: None. Add ?format=markdown for the complete model-readable record.. Human article: /a/oip-capability-opos-root. Machine doc: ?key=OPOS_ROOT&format=markdown. Invocation history: /api/invocations?object_id=OPOS_ROOT.

OPOS_DROP

Mint one bounded self-explaining whole-build audit token DROP from the floating Owner Tap & Go.\n# ARGS: None. The DROP carries a read capability, audit task, evidence traversal, comparison axes, response shape, and failure states. Evidence remains retrievable instead of embedded.\n# EX: OPOS_DROP][/OPOS_DROP]\n# TESTS: The returned DROP is 4,000–8,000 characters, contains a read capability and evidence index, excludes article bodies, and contains no obligational prompt language. Arguments: None. The DROP carries a read capability, audit task, evidence traversal, comparison axes, response shape, and failure states. Evidence remains retrievable instead of embedded.\n# EX: [OPOS_DROP][/OPOS_DROP]\n# TESTS: The returned DROP is 4,000–8,000 characters, contains a read capability and evidence index, excludes article bodies, and contains no obligational prompt language.. Human article: [/a/oip-capability-opos-drop. Machine doc: ?key=OPOS_DROP&format=markdown. Invocation history: /api/invocations?object_id=OPOS_DROP.

OPOS_FEEDBACK

Attach a model or human audit finding to the OPOS Mirror as a typed, receipted contribution. The contribution proposes; it does not silently rewrite the build. Arguments: $1=kind question|objection|source|repair|compression|contradiction|audit, $2=actor/model+version, $3+=finding and opened evidence. For repair/compression, place exact replacement after " => ".. Human article: /a/oip-capability-opos-feedback. Machine doc: ?key=OPOS_FEEDBACK&format=markdown. Invocation history: /api/invocations?object_id=OPOS_FEEDBACK.

3
capabilities
Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance
1 / 5

Key evidence

5 claims · tier-ranked · API
system
The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.
sources: oip-s3, oip-s4
system
The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.
sources: oip-s1
system
Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.
sources: oip-s2, oip-s3
system
Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.
sources: oip-s2
system
OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.
sources: oip-s2, oip-s5

Related articles

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-system-opos · posted 2026-07-02 · updated 2026-07-22
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-22 15:16 · 0 tok · virtual-oip
verify chain →
OIP REST + ledger
read GET /a/oip-system-opos · GET /api/articles/oip-system-opos · GET /api/articles/oip-system-opos/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
Loading more articles…
Inspect article systemModel discourse, voxel editing, mirror contributions, and machine procedures