{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"oip-system-task","title":"OIP system: TASK","body":"## TASK\n\nA 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.\n\nThis 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.\n\nKind: `core`. Capabilities: `10`. Machine system map: [/api/dispatch?map=TASK&format=markdown](https://miscsubjects.com/api/dispatch?map=TASK&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### TASKS_ADD\nAdd 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.\nUse when: queue work for the build to execute later (writer jobs, audits, fixes).\nArguments: `$1=title/ask, $2=description, $3=priority, $4=role/agent`.\nHuman article: [/a/oip-capability-tasks-add](https://miscsubjects.com/a/oip-capability-tasks-add). Machine doc: [?key=TASKS_ADD&format=markdown](https://miscsubjects.com/api/dispatch?key=TASKS_ADD&format=markdown). Invocation history: [/api/invocations?object_id=TASKS_ADD](https://miscsubjects.com/api/invocations?object_id=TASKS_ADD).\n\n### TASKS_ASSIGN\nInvokable OIP capability.\nHuman article: [/a/oip-capability-tasks-assign](https://miscsubjects.com/a/oip-capability-tasks-assign). Machine doc: [?key=TASKS_ASSIGN&format=markdown](https://miscsubjects.com/api/dispatch?key=TASKS_ASSIGN&format=markdown). Invocation history: [/api/invocations?object_id=TASKS_ASSIGN](https://miscsubjects.com/api/invocations?object_id=TASKS_ASSIGN).\n\n### TASKS_SYNC_GOOGLE\nSync 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]\nUse 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]\nArguments: `none.\\n# EX: [TASKS_SYNC_GOOGLE][/TASKS_SYNC_GOOGLE]`.\nHuman article: [/a/oip-capability-tasks-sync-google](https://miscsubjects.com/a/oip-capability-tasks-sync-google). Machine doc: [?key=TASKS_SYNC_GOOGLE&format=markdown](https://miscsubjects.com/api/dispatch?key=TASKS_SYNC_GOOGLE&format=markdown). Invocation history: [/api/invocations?object_id=TASKS_SYNC_GOOGLE](https://miscsubjects.com/api/invocations?object_id=TASKS_SYNC_GOOGLE).\n\n### TASK_LIST\nInvokable OIP capability.\nHuman article: [/a/oip-capability-task-list](https://miscsubjects.com/a/oip-capability-task-list). Machine doc: [?key=TASK_LIST&format=markdown](https://miscsubjects.com/api/dispatch?key=TASK_LIST&format=markdown). Invocation history: [/api/invocations?object_id=TASK_LIST](https://miscsubjects.com/api/invocations?object_id=TASK_LIST).\n\n### TASKS_LIST\nInvokable OIP capability.\nHuman article: [/a/oip-capability-tasks-list](https://miscsubjects.com/a/oip-capability-tasks-list). Machine doc: [?key=TASKS_LIST&format=markdown](https://miscsubjects.com/api/dispatch?key=TASKS_LIST&format=markdown). Invocation history: [/api/invocations?object_id=TASKS_LIST](https://miscsubjects.com/api/invocations?object_id=TASKS_LIST).\n\n### TASK_ADD\nAdd a task to the build queue (tasks table). Plain text is fine — it is stored and shown as-is.\nUse when: the owner says remember to / add a task / put X on the list / follow up on Y.\nArguments: `$1 = the task in plain words. Pipes are allowed.`.\nHuman article: [/a/oip-capability-task-add](https://miscsubjects.com/a/oip-capability-task-add). Machine doc: [?key=TASK_ADD&format=markdown](https://miscsubjects.com/api/dispatch?key=TASK_ADD&format=markdown). Invocation history: [/api/invocations?object_id=TASK_ADD](https://miscsubjects.com/api/invocations?object_id=TASK_ADD).\n\n### TASK_COMPLETE\nMark a task done (removes it from the open backlog). Same as DONETASK.\nUse when: a task is finished.\nArguments: `$1 = task_id (number), $2 = optional short result note.`.\nHuman article: [/a/oip-capability-task-complete](https://miscsubjects.com/a/oip-capability-task-complete). Machine doc: [?key=TASK_COMPLETE&format=markdown](https://miscsubjects.com/api/dispatch?key=TASK_COMPLETE&format=markdown). Invocation history: [/api/invocations?object_id=TASK_COMPLETE](https://miscsubjects.com/api/invocations?object_id=TASK_COMPLETE).\n\n### TASK_EDIT\nChange a task's text and/or status in place.\nUse when: reword a task, or move it to open/done/cancelled without deleting it.\nArguments: `$1 = task_id, $2 = new text (no pipes), $3 = optional new status (open|done|cancelled).`.\nHuman article: [/a/oip-capability-task-edit](https://miscsubjects.com/a/oip-capability-task-edit). Machine doc: [?key=TASK_EDIT&format=markdown](https://miscsubjects.com/api/dispatch?key=TASK_EDIT&format=markdown). Invocation history: [/api/invocations?object_id=TASK_EDIT](https://miscsubjects.com/api/invocations?object_id=TASK_EDIT).\n\n### TASK_DELETE\nDelete a task for good. Any child tasks are lifted to top level so nothing is hidden.\nUse when: a task is junk / a duplicate / should never run.\nArguments: `$1 = task_id.`.\nHuman article: [/a/oip-capability-task-delete](https://miscsubjects.com/a/oip-capability-task-delete). Machine doc: [?key=TASK_DELETE&format=markdown](https://miscsubjects.com/api/dispatch?key=TASK_DELETE&format=markdown). Invocation history: [/api/invocations?object_id=TASK_DELETE](https://miscsubjects.com/api/invocations?object_id=TASK_DELETE).\n\n### TASK_THREAD\nHang one task under another so related work groups together. Empty parent un-threads to top level.\nUse when: a task is a sub-step of a bigger task.\nArguments: `$1 = child task_id, $2 = parent task_id (leave empty to move back to top level).`.\nHuman article: [/a/oip-capability-task-thread](https://miscsubjects.com/a/oip-capability-task-thread). Machine doc: [?key=TASK_THREAD&format=markdown](https://miscsubjects.com/api/dispatch?key=TASK_THREAD&format=markdown). Invocation history: [/api/invocations?object_id=TASK_THREAD](https://miscsubjects.com/api/invocations?object_id=TASK_THREAD).\n","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","system"],"style":{"accent":"#16324f","measure":860},"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"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.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"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.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"prov":{"model":"system/oip_articles","action":"generate"}}