miscsubjects.com
Object Invocation Protocol · protocol specification

OIP system: Agents

#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
## §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-agent
**Machine bundle:** https://miscsubjects.com/api/articles/oip-system-agent/bundle?format=markdown
**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.

Agents

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: model. Capabilities: 12. Machine system map: /api/dispatch?map=AGENT&format=markdown. Root: /a/oip.

Operations

AGENT_IMPORT

Cannibalize an agent definition (md frontmatter name/description/model/tools) into a proposed agent row. PROPOSE only Use when: you need to agent import Arguments: source(url|r2:key|raw)|category. Human article: /a/oip-capability-agent-import. Machine doc: ?key=AGENT_IMPORT&format=markdown. Invocation history: /api/invocations?object_id=AGENT_IMPORT.

AGENT_SPAWN

Spawn a resident agent that loops on a goal until done (durable, survives Mac sleep) Use when: you need to agent spawn Arguments: goal|brain|maxSteps. Human article: /a/oip-capability-agent-spawn. Machine doc: ?key=AGENT_SPAWN&format=markdown. Invocation history: /api/invocations?object_id=AGENT_SPAWN.

AGENT_LIST

List resident agents and their live status Use when: you need to agent list Arguments: none. Human article: /a/oip-capability-agent-list. Machine doc: ?key=AGENT_LIST&format=markdown. Invocation history: /api/invocations?object_id=AGENT_LIST.

AGENT

Control a resident agent Use when: you need to agent Arguments: op(status|send|pause|resume|kill|events)|id|msg. Human article: /a/oip-capability-agent. Machine doc: ?key=AGENT&format=markdown. Invocation history: /api/invocations?object_id=AGENT.

AGENT_LEARN

save a lesson/working pattern to an agent persistent memory. Args: agent|lesson. Use when: the user says something works, prefers a style, or gives feedback worth keeping. Human article: /a/oip-capability-agent-learn. Machine doc: ?key=AGENT_LEARN&format=markdown. Invocation history: /api/invocations?object_id=AGENT_LEARN.

AGENT_RECALL

load an agent saved lessons/patterns. Arg: agent. Use when: at the start of a creative job, to apply what worked before. Human article: /a/oip-capability-agent-recall. Machine doc: ?key=AGENT_RECALL&format=markdown. Invocation history: /api/invocations?object_id=AGENT_RECALL.

AGENT_BRIDGE

Invokable OIP capability. Human article: /a/oip-capability-agent-bridge. Machine doc: ?key=AGENT_BRIDGE&format=markdown. Invocation history: /api/invocations?object_id=AGENT_BRIDGE.

AGENT_TURNS

last N agent turns across all CLI agents (claude, codex, grok, …). $1 = agent id or "all", $2 = limit (default 5). Use when: "what did codex do", "show agent turns", cross-agent audit. Human article: /a/oip-capability-agent-turns. Machine doc: ?key=AGENT_TURNS&format=markdown. Invocation history: /api/invocations?object_id=AGENT_TURNS.

AGENT_TURNS_TRACE

agent turns linked to one ledger trace_id. $1 = trace_id, $2 = limit (default 20). Use when: "what CLI agents ran on this trace", incident/debug linkage. Human article: /a/oip-capability-agent-turns-trace. Machine doc: ?key=AGENT_TURNS_TRACE&format=markdown. Invocation history: /api/invocations?object_id=AGENT_TURNS_TRACE.

AGENT_TURNS_ISSUES

agent turns matching issue tags (risk, protected, file_edit, unaudited, audit_fail). $1 = tag, $2 = limit. Use when: "show risky agent turns", "unaudited codex turns", filterable issue triage. Human article: /a/oip-capability-agent-turns-issues. Machine doc: ?key=AGENT_TURNS_ISSUES&format=markdown. Invocation history: /api/invocations?object_id=AGENT_TURNS_ISSUES.

AGENT_TURNS_FILTER

multi-filter agent turn query. $1=agent|all, $2=tag|risk|all, $3=limit. Use when: cross-agent issue board, "gemini risk turns", audit backlog. Human article: /a/oip-capability-agent-turns-filter. Machine doc: ?key=AGENT_TURNS_FILTER&format=markdown. Invocation history: /api/invocations?object_id=AGENT_TURNS_FILTER.

AGENT_SPAWN_CLI

Invokable OIP capability. Human article: /a/oip-capability-agent-spawn-cli. Machine doc: ?key=AGENT_SPAWN_CLI&format=markdown. Invocation history: /api/invocations?object_id=AGENT_SPAWN_CLI.

12
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: Agents. 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 rootoipOIP 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-curlWhat is MCP?protocol comparisonoip-mcpWhat is GitHub?subsidiary conceptoip-github
oip-system-agent · posted 2026-07-02 · updated 2026-07-02
Ledger API & provenance
Provenance · 1 model pass · 0 tokens · $0 · 1 model
chain head virtual-oip
generate system/oip_articles · 2026-07-02 22:59 · 0 tok · virtual-oip
verify chain →
OIP REST + ledger
read GET /a/oip-system-agent · GET /api/articles/oip-system-agent · GET /api/articles/oip-system-agent/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…