{"slug":"oip-system-work","title":"OIP system: WORK","body":"## WORK\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: `2`. Machine system map: [/api/dispatch?map=WORK&format=markdown](https://miscsubjects.com/api/dispatch?map=WORK&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### WORK_FEED\nThe shared work thread. THE FIRST THING ANY MODEL OR TOKEN-HOLDER READS. Aggregates the top priority, open tasks, open GitHub issues, the lead pipeline, and the recent model thread into one ranked view.\nUse when: at the start of ANY session, or when asked 'what should I work on', 'what is the state', 'catch me up', 'where are we'.\nArguments: `$1 = how many recent thread entries (default 15).`.\nHuman article: [/a/oip-capability-work-feed](https://miscsubjects.com/a/oip-capability-work-feed). Machine doc: [?key=WORK_FEED&format=markdown](https://miscsubjects.com/api/dispatch?key=WORK_FEED&format=markdown). Invocation history: [/api/invocations?object_id=WORK_FEED](https://miscsubjects.com/api/invocations?object_id=WORK_FEED).\n\n### WORK_APPEND\nAppend one entry to the shared append-only work thread. This is how every model records what it did, proposed, or audited so the next model continues from it (fixes short model memory).\nUse when: after you do, propose, or audit anything. Always append.\nArguments: `$1 = your model/agent name, $2 = kind (note|edit|proposal|audit|question|done), $3 = your entry. Prefix body with 'ref:task:12' or 'ref:lead:49' or 'ref:gh:7' to link it.`.\nHuman article: [/a/oip-capability-work-append](https://miscsubjects.com/a/oip-capability-work-append). Machine doc: [?key=WORK_APPEND&format=markdown](https://miscsubjects.com/api/dispatch?key=WORK_APPEND&format=markdown). Invocation history: [/api/invocations?object_id=WORK_APPEND](https://miscsubjects.com/api/invocations?object_id=WORK_APPEND).\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"}}