{"slug":"oip-model-review-loop","title":"Models reviewing OIP articles","body":"## What this article explains\n\nThis article describes how an Artificial Intelligence (AI) model reviews content. The model reads an Object Invocation Protocol (OIP) article. OIP is a standard for invoking objects. It uses plain Uniform Resource Locators (URLs) and receipts. It does not use a persistent session. Any model that can open a URL can use OIP. The `miscsubjects.com` website uses OIP. Each row in its directory is an OIP object.\n\nThe AI model judges two things. First, it checks if the article's machine-readable JSON is clear. JSON stands for JavaScript Object Notation. Second, it checks if the English article explains the same JSON clearly. This explanation must be for a zero-context human reader. Even an autistic child should understand it end to end.\n\n## How OIP works\n\nOIP objects are invoked using the `/api/dispatch` route on `miscsubjects.com`. You can invoke an object with a `POST` request. For example, `POST /api/dispatch {key, body}`. You can also use a `GET` request. For example, `GET /api/dispatch?invoke=KEY&body=...`. An invocation is a call to an OIP object.\n\nEvery invocation is recorded. It lands in an append-only ledger. A ledger is a record of all past actions. Each invocation gets a receipt. A receipt is proof of the invocation. You can find a receipt at `/api/dispatch?receipt=inv_ID`. `inv_ID` is the unique identifier for that invocation.\n\n## Questions the model asks\n\nThe model scores several aspects of the article. It scores JSON clarity. It scores English clarity. It scores zero-context human clarity. It checks if the build operation can be performed with `curl`. `curl` is a command-line tool for transferring data with URLs. If yes, it names the exact route shape. If no, it names the missing shape.\n\nThe model also compares the OIP object to the Model Context Protocol (MCP). MCP is an open standard. An AI model connects to an MCP server over a session. A server is a computer program that provides services to other programs. The MCP server exposes tools, resources, and prompts. The model can call these. MCP is not a content-management system. OIP differs from MCP because OIP uses plain URLs and receipts. It has no persistent session. MCP uses a persistent session.\n\nThe model identifies missing subsidiary articles. These are concepts that need their own OIP documentation. It suggests concrete repair actions.\n\n## Output of the review\n\nThe model returns JSON. It does not return prose. The `miscsubjects.com` build stores this JSON. It becomes a ledger event. It is also a protocol invocation. Future agents can read this review history. They can then patch small gaps. These gaps can be in the article or in the machine contract.\n\n## Machine shape of the review result\n\nA review result includes these fields:\n*   `scores`: Numerical ratings for various aspects.\n*   `can_operate`: A boolean indicating if the described operation is possible.\n*   `missing_concepts`: A list of concepts needing further explanation.\n*   `subsidiary_articles`: A list of suggested new OIP articles.\n*   `concrete_fixes`: Specific changes to text or JSON fields.\n*   `followup_questions`: Questions for further review.\n*   `pass`: A boolean indicating overall success or failure.\n*   `urls`: A list of relevant URLs. Each URL would include a descriptive comment. For example, a URL for an invocation receipt would be commented as \"URL to retrieve the invocation receipt for this review.\" A URL for a related OIP article would be commented as \"URL to the related OIP article being reviewed.\"\n## Latest clarity reviews (live)\n\nFresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.\n\n- 2026-07-03 00:04 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 6/10\n  - gaps named: MCP; directory rows; dispatch; ledger\n\nHow the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.","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"}}