{"slug":"oip-operating-model","title":"OIP operating model","body":"## Definition\n\nOIP (Object Invocation Protocol) governs remote execution through scoped, self-describing object contracts: a capable model operates external tools, models, devices, APIs, files, queues, and ledgers by resolving an object, invoking it within scope, and reading the receipt it produces, with replay and repair lineage on every action.\n\n## The operating model\n\nOIP governs remote execution through scoped, self-describing object contracts. A capable model operates external tools, models, devices, APIs, files, queues, and ledgers by resolving an object, reading its contract, invoking it within scope, and reading the receipt.\n\n## Invariants\n\n- An action is an object invocation. Proof: `POST /api/dispatch {key, body}` runs one object.\n- Authority equals the object scope carried by the credential. Proof: `GET /api/dispatch?explain=1&share=TOKEN` returns the exact scope.\n- Proof of an action is its receipt. Proof: `GET /api/dispatch?receipt=inv_ID` returns the request, the response, and the actor.\n- A correction is a repair linked to the receipt it fixes. Proof: `POST /api/dispatch {key, body, repairs:inv_ID}` writes lineage in both directions.\n\nThe model is a temporary operator over scoped machinery. Its scope is stated in the credential and enforced at the dispatch boundary.\n\n## Operating loop\n\n1. Resolve the object: `?ask=<plain language>` or `?key=<KEY>`.\n2. Read the object contract.\n3. Confirm the credential scope permits the object: `?explain=1&share=TOKEN`.\n4. Invoke the object.\n5. Return the receipt: `proof.say_to_user`.\n6. Correct a wrong result by repairing from the receipt.\n\nEach step completes before the next. The first incomplete step is the stopping point, and it names what it requires.","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","primer"],"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"}}