miscsubjects.com
Object Invocation Protocol · protocol specification

OIP system: TRAIL

#oip#object-invocation-protocol#protocol-specification#machine-native-json#system

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

TRAIL

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=TRAIL&format=markdown. Root: /a/oip.

Operations

TRAIL_SAVE

Name a sequence of past invocations as a TRAIL - a named sequence of past calls you can run again as one unit (the trail itself carries no permissions). Stores each step's object key and recorded input in the current owner/capability/tenant namespace. Arguments: name|inv_ID1,inv_ID2,... (2-20 receipt ids, oldest first, comma-separated). Human article: /a/oip-capability-trail-save. Machine doc: ?key=TRAIL_SAVE&format=markdown. Invocation history: /api/invocations?object_id=TRAIL_SAVE.

TRAIL_RUN

Run a named TRAIL (a saved sequence of past calls). Every recorded step is checked again against the caller's own token, consumes that caller's use budget, and produces a receipt linked to the original invocation. Arguments: name (the trail name given to TRAIL_SAVE). Human article: /a/oip-capability-trail-run. Machine doc: ?key=TRAIL_RUN&format=markdown. Invocation history: /api/invocations?object_id=TRAIL_RUN.

TRAIL_LIST

List the trails in your own space - owner, token, or tenant; trails never cross spaces. Arguments: (none). Human article: /a/oip-capability-trail-list. Machine doc: ?key=TRAIL_LIST&format=markdown. Invocation history: /api/invocations?object_id=TRAIL_LIST.

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
Talk to this article
Tap a phone. Ask anything about OIP system: TRAIL. 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.

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-trail · posted 2026-07-02 · updated 2026-07-14
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-14 22:19 · 0 tok · virtual-oip
verify chain →
OIP REST + ledger
read GET /a/oip-system-trail · GET /api/articles/oip-system-trail · GET /api/articles/oip-system-trail/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…