{"_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-cloudflare-pages","title":"Cloudflare Pages","body":"The `oip-cloudflare-pages` article defines the integration of Cloudflare Pages, a mechanism for deploying and serving Object Invocation Protocol (OIP) web content, within the OIP ecosystem. Object Invocation Protocol (OIP) specifies a standard for invoking work objects, ensuring verifiable execution and state management. The OIP unit is the work object. The OIP proof is the receipt. The OIP loop is object, invoke, ledger, receipt, replay, repair.\n\n## What Cloudflare Pages is\nCloudflare Pages is a web hosting service. It deploys web applications and serves web content. Cloudflare Pages operates as a content delivery network (CDN) for web assets.\n\n## Why OIP uses Cloudflare Pages\nOIP (Object Invocation Protocol) requires a web hosting mechanism for its web application and Application Programming Interface (API) endpoints. Cloudflare Pages provides this mechanism. Cloudflare Pages serves OIP content and exposes OIP API endpoints. The `miscsubjects.com` server uses Cloudflare Pages to host its OIP web application and API, fulfilling the requirement for public accessibility and content delivery.\n\n## How to see or use Cloudflare Pages live\nTo observe Cloudflare Pages serving OIP content, visit `https://miscsubjects.com`. This Uniform Resource Locator (URL) serves the OIP web application. Further OIP protocol documentation is available via `/api/articles`.\n\nThe `curl` Command Line Interface (CLI) tool performs OIP object invocations. An invocation uses either `POST /api/dispatch {key, body}` or `GET /api/dispatch?invoke=KEY&body=...`. Every invocation appends to the OIP ledger and returns a receipt.\n\nExample invocation:\n```bash\ncurl -X POST -H 'Content-Type: application/json' -d '{\"key\":\"example_object\",\"body\":\"example_body\"}' https://miscsubjects.com/api/dispatch\n```\nThis command invokes an OIP work object identified by `example_object` with `example_body` as its input. The `miscsubjects.com` server processes this invocation via its `/api/dispatch` endpoint. Cloudflare Pages serves the `/api/dispatch` endpoint. The invocation generates an OIP receipt.\n\n## Comparison to MCP\nCloudflare Pages provides a stateless web hosting mechanism. It processes requests over Representational State Transfer (REST) principles. Each request contains all necessary information for processing.\n\nThe Model Context Protocol (MCP) establishes a stateful session. An Artificial Intelligence (AI) model connects to an MCP server over a session. The MCP server exposes tools, resources, and prompts the model can call within that session context. Cloudflare Pages uses plain Uniform Resource Locators (URLs) for content delivery. MCP uses session-bound interactions for model-server communication.\n\n## Proof and receipts\nThe proof of deployment and management of OIP web applications using Cloudflare Pages resides in the OIP ledger and OIP receipts. An OIP receipt is a cryptographically verifiable record of an invocation.\n\nA receipt for an invocation is accessible at `/api/dispatch?receipt=inv_ID`. The `inv_ID` is the unique invocation identifier. This route retrieves the JavaScript Object Notation (JSON) receipt object. The receipt proves the invocation occurred and was processed by the OIP system hosted on Cloudflare Pages.\n\nFor further details on OIP ledger and receipts, consult `/a/oip-ledger-receipts`.\n\n## Receipt Rule\nAn OIP system hosted on Cloudflare Pages issues a receipt for every successful invocation. The receipt is a JSON object. The receipt contains the `inv_ID` and a cryptographic signature. The receipt is retrievable via `GET /api/dispatch?receipt=inv_ID`.\n\n## Conformance Rule\nA conformant OIP implementation serves its web application and OIP API endpoints through Cloudflare Pages. This implementation exposes the OIP invocation routes `POST /api/dispatch` and `GET /api/dispatch`. It also exposes the OIP receipt route `/api/dispatch?receipt=inv_ID`. The implementation ensures public accessibility of OIP content and verifiable invocation processing.\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 02:46 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 8/10 · English 9/10 · zero-context human 7/10\n  - gaps named: OIP protocol details; Cloudflare Pages integration\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","dynamic"],"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"}}