{"slug":"oip-system-governor","title":"OIP system: GOVERNOR","body":"## GOVERNOR\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: `3`. Machine system map: [/api/dispatch?map=GOVERNOR&format=markdown](https://miscsubjects.com/api/dispatch?map=GOVERNOR&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### GOVERNOR\nInvokable OIP capability.\nHuman article: [/a/oip-capability-governor](https://miscsubjects.com/a/oip-capability-governor). Machine doc: [?key=GOVERNOR&format=markdown](https://miscsubjects.com/api/dispatch?key=GOVERNOR&format=markdown). Invocation history: [/api/invocations?object_id=GOVERNOR](https://miscsubjects.com/api/invocations?object_id=GOVERNOR).\n\n### GOVERNOR_RUN\nRun the GOVERNOR — scan the last 48h of ledger turns into a deterministic digest (error streaks, file collisions, loop states, auth lockouts, cron noise, task flow, waste), have the GOVERNOR model write the brief, email it to Cyrus, text him the verdict, ledger everything as GOVERNOR_BRIEF.\nUse when: Cyrus asks \"whats going on with the build\", \"governor report\", \"run governor\", \"build brief\", \"what keeps breaking\" — or any model wants the standing manager's view before making structural changes. Runs automatically every 12h / 2000 events / 150 errors; this row is the manual fire.\nArguments: `mode — empty = full run (model + email + iMessage) · dry = digest JSON only, no model call, no delivery`.\nHuman article: [/a/oip-capability-governor-run](https://miscsubjects.com/a/oip-capability-governor-run). Machine doc: [?key=GOVERNOR_RUN&format=markdown](https://miscsubjects.com/api/dispatch?key=GOVERNOR_RUN&format=markdown). Invocation history: [/api/invocations?object_id=GOVERNOR_RUN](https://miscsubjects.com/api/invocations?object_id=GOVERNOR_RUN).\n\n### GOVERNOR_ASK\nAsk the GOVERNOR (build manager) a question. It answers from the live 24h digest + recurrence memory + charter — counts in parentheses, sized for iMessage.\nUse when: Cyrus texts \"governor <question>\" or \"ask the governor ...\", or any model wants the manager's evidence-grounded read on build health, conflicts, or what keeps recurring.\nArguments: `the question, verbatim`.\nHuman article: [/a/oip-capability-governor-ask](https://miscsubjects.com/a/oip-capability-governor-ask). Machine doc: [?key=GOVERNOR_ASK&format=markdown](https://miscsubjects.com/api/dispatch?key=GOVERNOR_ASK&format=markdown). Invocation history: [/api/invocations?object_id=GOVERNOR_ASK](https://miscsubjects.com/api/invocations?object_id=GOVERNOR_ASK).\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"}}