miscsubjects.com
Object Invocation Protocol · protocol specification

OIP system: TASKS

#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-tasks
**Machine bundle:** https://miscsubjects.com/api/articles/oip-system-tasks/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.

TASKS

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

Operations

TASKS_ADD

Add a new task to the queue. $1=title/ask, $2=description/context, $3=priority(P0/P1/P2/P3), $4=assigned_to_agent/role. Stores a structured JSON job so the cron runner can execute it. Use when: queue work for the build to execute later (writer jobs, audits, fixes). Arguments: $1=title/ask, $2=description, $3=priority, $4=role/agent. Human article: /a/oip-capability-tasks-add. Machine doc: ?key=TASKS_ADD&format=markdown. Invocation history: /api/invocations?object_id=TASKS_ADD.

TASKS_ASSIGN

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

TASKS_SYNC_GOOGLE

Sync all unsynced open D1 tasks to Google Tasks. Call when asked to sync tasks to Google Tasks or when the admin Tasks tab shows unsynced items.\n# WHEN_TO_USE: user says sync tasks to Google Tasks, or admin page shows unsynced count.\n# ARGS: none.\n# EX: TASKS_SYNC_GOOGLE][/TASKS_SYNC_GOOGLE] Use when: user says sync tasks to Google Tasks, or admin page shows unsynced count.\n# ARGS: none.\n# EX: [TASKS_SYNC_GOOGLE][/TASKS_SYNC_GOOGLE] Arguments: none.\n# EX: [TASKS_SYNC_GOOGLE][/TASKS_SYNC_GOOGLE]. Human article: [/a/oip-capability-tasks-sync-google. Machine doc: ?key=TASKS_SYNC_GOOGLE&format=markdown. Invocation history: /api/invocations?object_id=TASKS_SYNC_GOOGLE.

TASKS_LIST

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

4
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: TASKS. 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-tasks · 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 23:01 · 0 tok · virtual-oip
verify chain →
OIP REST + ledger
read GET /a/oip-system-tasks · GET /api/articles/oip-system-tasks · GET /api/articles/oip-system-tasks/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…