{"_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":"cloudflare-os-xl-04-agents-as-infrastructure","title":"Cloudflare OS: agents as infrastructure","body":"*Part 4 of [Cloudflare OS XL](/a/cloudflare-os-xl), an inventory of the Cloudflare platform this build does not have installed.*\n\nThis build already runs agents. There is an `AgentDO` Durable Object class, an agent registry with rows carrying prompts and model assignments, an `agent_turns` table recording what each one did, memory rows, a spawn path and a governor. That is a hand-rolled agent runtime, and it works.\n\nThe Agents SDK is Cloudflare's version of the same thing, and the interesting question is not \"should this build have agents\" — it has them — but which parts of the hand-rolled runtime are load-bearing and which are re-implementations of something the platform now provides.\n\n## The Agents SDK\n\nThe SDK creates stateful agents with persistent memory, real-time WebSocket connections and scheduled tasks. Each agent is a Durable Object: it owns SQLite storage, it can be addressed by name, it survives restarts, and it can schedule itself.\n\nFour things it provides that the current arrangement does not:\n\n**Per-agent scheduling.** An agent can call `this.schedule(delay, 'methodName', payload)` and be woken up later. Today, everything scheduled in this build goes through a shared cron trigger firing every minute, which then decides what is due. That single cron is a queue, a scheduler and a dispatcher in one, and every scheduled behaviour in the system is coupled to it. Per-agent alarms decouple them.\n\n**State as a first-class field.** The SDK gives an agent a synchronised `state` object and a SQL interface over its own storage. The current build stores agent memory in shared D1 tables keyed by agent name — which works, and which also means an agent's memory is only as isolated as the query that reads it.\n\n**WebSockets with hibernation.** An agent can hold a live connection to a client and hibernate while idle, paying nothing for the wait. Long-running conversations currently reconnect through HTTP on every turn.\n\n**A defined turn loop.** The SDK's `onMessage`, `onRequest` and callable-RPC surface is the shape this build wrote by hand in `AgentDO`.\n\nThe honest verdict is not \"replace the agent runtime\". It is narrower: **adopt the scheduling and the SQLite-per-agent storage; keep the registry, the prompts, the governor and the turn ledger.** Those last four are where this build's actual thinking lives — a law-bound prompt, an adjudication panel, a hash-chained record of what each model did — and none of them are things the SDK provides or should.\n\n**Verdict: adopt in part.** Scheduling and per-agent state: yes. The registry and governance layer: keep what exists.\n\n## Remote MCP servers with OAuth\n\nThis build's tool surface is already an MCP server. It runs locally, over stdio, through a bridge on the owner's machine, and it is reachable by exactly the clients configured on that machine.\n\nCloudflare hosts remote MCP servers as Workers, with `workers-oauth-provider` handling the authorization flow. The server becomes a URL. Any MCP client — Claude, an inspector, another agent, a partner's tooling — can attach to it by signing in, and the OAuth layer decides what each caller can see.\n\nThree consequences for this build specifically.\n\n**The bridge stops being a single point of failure.** Same argument as Part 3: capability that lives on a laptop is offline when the laptop is.\n\n**Scope becomes structural rather than conventional.** This build has one act-scoped token that can edit articles and call every tool, plus a separate admin key. That is a deliberate design and it is documented. But it is enforced by the token check inside each handler, not by the protocol. An OAuth-fronted MCP server can present a different tool list to a different principal, which is a stronger form of the same idea.\n\n**The build becomes attachable.** Its whole premise is that work is an object other agents can lease and act on. A public, authenticated MCP endpoint is the most direct expression of that premise available.\n\n**Verdict: install.** This is the most on-thesis item in the entire series.\n\n## Hibernatable WebSockets\n\nWorth separating from the SDK, because it applies to Durable Objects generally and this build already has three classes.\n\nA Durable Object holding a WebSocket normally stays in memory for the life of the connection. With the hibernation API, the DO can be evicted while the socket stays open, and is revived when a message actually arrives. The cost of an idle connection goes to approximately nothing.\n\nThe build has an obvious use: a live view of what agents are doing. Right now, watching the build work means polling an endpoint or reading a ledger tail. A hibernatable socket makes a push feed cheap enough to leave open indefinitely.\n\n**Verdict: later.** Real, cheap, and not urgent until there is a surface that wants to watch.\n\n## What this part does not recommend\n\n**Do not rewrite `AgentDO` onto the SDK wholesale.** The temptation with a well-designed framework is to adopt all of it, and the parts of this build's agent layer that look like re-implementation are mostly not. The governor, the adjudication panel, the law-bound prompts and the turn ledger encode decisions that took months of corrections to arrive at. A framework migration that quietly drops them would be a regression wearing the clothes of an upgrade.\n\nThe rule to apply: adopt the platform where the platform provides *mechanism* — scheduling, storage isolation, connection handling. Keep what encodes *judgment*.\n\n## Verdicts\n\n| Product | What it replaces here | Verdict |\n| --- | --- | --- |\n| Agents SDK — scheduling | One shared cron firing every minute for all scheduled behaviour | **install** |\n| Agents SDK — per-agent SQLite | Agent memory in shared D1 tables keyed by name | **install** |\n| Agents SDK — turn loop, registry | The existing governor, prompts and turn ledger | **keep what exists** |\n| Remote MCP server + OAuth | A stdio MCP bridge on one laptop | **install** |\n| Hibernatable WebSockets | Polling an endpoint to watch agents work | **later** |\n\nNext: [Part 5 — media](/a/cloudflare-os-xl-05-media).\n","hero":"https://miscsubjects.com/img/gen/arcads-gpt-image-56aef75a-e653-45a2-a8f8-9f30e8a9e50c.png","images":[],"style":{},"tags":["cloudflare","agents","durable-objects","mcp","infrastructure"],"category":"systems","model":"Opus 5 (Claude Code)","ledger":{"href":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"This build already runs a hand-rolled agent runtime: an AgentDO Durable Object class, an agent registry with prompts and model assignments, a turn ledger, memory rows and a governor.","tier":"observational","source_ids":[],"why_material":"The question is which parts are re-implementation and which encode judgment."},{"id":"c2","text":"The Cloudflare Agents SDK gives each agent a Durable Object with persistent memory, real-time WebSocket connections and its own scheduled tasks.","tier":"definition","source_ids":["s-agents"],"why_material":"Per-agent scheduling decouples behaviours currently coupled to one shared cron."},{"id":"c3","text":"Every scheduled behaviour in this build is currently dispatched by a single cron trigger firing each minute, which acts as scheduler, queue and dispatcher at once.","tier":"observational","source_ids":[],"why_material":"One shared mechanism failing takes every scheduled behaviour with it."},{"id":"c4","text":"Cloudflare hosts remote MCP servers as Workers with an OAuth provider, which turns this build tool surface from a local stdio bridge into an authenticated URL any client can attach to.","tier":"definition","source_ids":["s-wfp"],"why_material":"The build premise is that outside agents lease and act on work, and this is the most direct expression of it."},{"id":"c5","text":"The correct adoption rule is to take the platform where it supplies mechanism, meaning scheduling, storage isolation and connection handling, and to keep what encodes judgment, meaning the governor, the law-bound prompts and the turn ledger.","tier":"expert","source_ids":[],"why_material":"A wholesale framework migration would drop decisions that took months of corrections to reach."}],"sources":[{"id":"s-agents","type":"documentation","url":"https://developers.cloudflare.com/agents/","title":"Cloudflare Agents SDK documentation","quote":"Create stateful AI agents with persistent memory, real-time WebSocket connections, and scheduled tasks using the Cloudflare Agents SDK.","accessed_at":"2026-08-06T03:10:06.201Z","prev":"genesis","hash":"c9a5252027d3c9dfde8e30901398cdd3510342b55057d7bd3a36888121b63ac0"},{"id":"s-wfp","type":"documentation","url":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/","title":"Workers for Platforms documentation","quote":"Run untrusted code from your customers or AI in secure, isolated sandboxes on Cloudflare's global network.","accessed_at":"2026-08-06T03:10:06.201Z","prev":"c9a5252027d3c9dfde8e30901398cdd3510342b55057d7bd3a36888121b63ac0","hash":"4fc87e57d5347a58572fa86b219c04629f1d5d3ad6ee2e8cfce16900e002dbac"}],"reviews":[],"extra":{},"has_traversal":false,"register":null,"status":"published","revisions":2,"contributions":[],"provenance":[],"energy":{"passes":0,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{},"head":"genesis"},"posted_at":"2026-08-06T03:10:06.201Z","created_at":"2026-08-06T03:10:06.201Z","updated_at":"2026-08-06T03:28:34.726Z","machine":{"shape":"article.machine/v1","slug":"cloudflare-os-xl-04-agents-as-infrastructure","kind":"article","read":{"human":"https://miscsubjects.com/a/cloudflare-os-xl-04-agents-as-infrastructure","json":"https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure","bundle":"https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":5,"sources":2,"contributions":0,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=cloudflare-os-xl-04-agents-as-infrastructure","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"cloudflare-os-xl-04-agents-as-infrastructure\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"cloudflare-os-xl-04-agents-as-infrastructure\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"cloudflare-os-xl-04-agents-as-infrastructure\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/cloudflare-os-xl-04-agents-as-infrastructure","json":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure","markdown":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/bundle?format=markdown","skill":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/skill","topology":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/topology","versions":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/revisions","invocations":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/invocations"},"editorial_review":{"headline_subject":"Agents as separately addressed infrastructure rather than shared code","hero_subject":"A row of individual numbered beehives spaced along a meadow","visual_action":"Each hive standing alone in an evenly spaced line","rationale":"The argument is one isolated, self-contained, individually addressable unit per agent instead of one shared runtime.","inspected":true,"inspection_note":"Eight or more wooden hives receding in a line at golden hour, each on its own stand with clear space between them, bees in flight. Separateness is the visible idea.","hero_brief":"An apiary in a summer meadow at golden hour, a long row of individually numbered wooden beehives spaced evenly apart, each one self-contained. Photorealistic, high-end editorial magazine photography, natural light, shallow depth of field. No readable text, no logos, no people facing camera."},"editorial_audit":{"slug":"cloudflare-os-xl-04-agents-as-infrastructure","ok":true,"issues":[]},"body_hash":"00326840cd7bcd74c9d83c579e63591bef7dda129caccc8abaace3935fe6e991","object":{"object_type":"article-object","identity":{"id":"article:cloudflare-os-xl-04-agents-as-infrastructure","slug":"cloudflare-os-xl-04-agents-as-infrastructure","title":"Cloudflare OS: agents as infrastructure"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/cloudflare-os-xl-04-agents-as-infrastructure","role":"explain","audience":"human"},"skill":{"route":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/skill","role":"direct behavior","audience":"model","content":"---\nname: cloudflare-os-xl-04-agents-as-infrastructure\ndescription: Apply the Cloudflare OS: agents as infrastructure article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Cloudflare OS: agents as infrastructure\n\nThis Skill is the behavioral expression of [the canonical article](/a/cloudflare-os-xl-04-agents-as-infrastructure). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/cloudflare-os-xl-04-agents-as-infrastructure.\n- Read claims and relationships at /api/articles/cloudflare-os-xl-04-agents-as-infrastructure/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nPart 4 of Cloudflare OS XL /a/cloudflare-os-xl , an inventory of the Cloudflare platform this build does not have installed. This build already runs agents. There is an AgentDO Durable Object class, an agent registry with rows carrying prom\n\n## Representations\n\n- Human: /a/cloudflare-os-xl-04-agents-as-infrastructure\n- JSON: /api/articles/cloudflare-os-xl-04-agents-as-infrastructure\n- Relationships: /api/articles/cloudflare-os-xl-04-agents-as-infrastructure/topology\n- History: /api/articles/cloudflare-os-xl-04-agents-as-infrastructure/revisions\n"},"json":{"route":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"MCP_EVAL","type":"fn","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: Try an integration before installing it. Resolves the named integration to its OIP objects, classifies read vs write, runs one safe read-only trial, returns a receipt, and recommends connect or skip.\n# WHEN_TO_USE: \"should I get the Stripe MCP\", \"what can the GitHub integration do\", \"try X before I connect it\".\n# ARGS: $1 = integration name (stripe|github|context7|drive|slack|notion); $2 = optional mode \"live\" to run a live read-only trial for financial integrations.\n# EX: [MCP_EVAL]github[/MCP_EVAL]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/MCP_EVAL","json":"/api/directory/MCP_EVAL","skill":"/api/directory/MCP_EVAL?format=skill","oip_contract":"/api/dispatch?key=MCP_EVAL"}},{"key":"TRY_GITHUB_MCP","type":"fn","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: Try the GitHub integration before connecting it. Runs a safe read-only trial (list issues) and returns a receipt.\n# WHEN_TO_USE: \"should I get GitHub MCP\", \"what would GitHub let an agent do\".\n# ARGS: none\n# EX: [TRY_GITHUB_MCP][/TRY_GITHUB_MCP]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TRY_GITHUB_MCP","json":"/api/directory/TRY_GITHUB_MCP","skill":"/api/directory/TRY_GITHUB_MCP?format=skill","oip_contract":"/api/dispatch?key=TRY_GITHUB_MCP"}},{"key":"TRY_STRIPE_MCP","type":"fn","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: Try the Stripe integration before connecting it. Shows the read and write objects Stripe exposes here and recommends connect or skip. Financial: the live read-only account check runs only in mode \"live\".\n# WHEN_TO_USE: \"should I get Stripe MCP\", \"what would Stripe let an agent do\".\n# ARGS: $1 = optional mode \"live\"\n# EX: [TRY_STRIPE_MCP][/TRY_STRIPE_MCP]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TRY_STRIPE_MCP","json":"/api/directory/TRY_STRIPE_MCP","skill":"/api/directory/TRY_STRIPE_MCP?format=skill","oip_contract":"/api/dispatch?key=TRY_STRIPE_MCP"}},{"key":"BROWSER_JSON","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Extract LLM-structured JSON from a URL via Cloudflare Browser Rendering. $1=account_id, $2=JSON body {url, prompt?, response_format?}\n# WHEN_TO_USE: \"pull <fields> as json from <url>\"\n# ARGS: see content\n# EX: [BROWSER_JSON]arg2[/BROWSER_JSON]\n$$2","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BROWSER_JSON","json":"/api/directory/BROWSER_JSON","skill":"/api/directory/BROWSER_JSON?format=skill","oip_contract":"/api/dispatch?key=BROWSER_JSON"}},{"key":"BROWSER_LINKS","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Extract all links from a URL via Cloudflare Browser Rendering. $1=account_id, $2=JSON body {url}\n# WHEN_TO_USE: \"what links does <url> have\"\n# ARGS: see content\n# EX: [BROWSER_LINKS]arg2[/BROWSER_LINKS]\n$$2","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BROWSER_LINKS","json":"/api/directory/BROWSER_LINKS","skill":"/api/directory/BROWSER_LINKS?format=skill","oip_contract":"/api/dispatch?key=BROWSER_LINKS"}},{"key":"BROWSER_MARKDOWN","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Get the markdown of a URL via Cloudflare Browser Rendering. $1=account_id, $2=JSON body {url}. Returns the rendered markdown\n# WHEN_TO_USE: \"fetch as markdown <url>\" or \"what does <url> say\"\n# ARGS: see content\n# EX: [BROWSER_MARKDOWN]arg2[/BROWSER_MARKDOWN]\n$$2","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BROWSER_MARKDOWN","json":"/api/directory/BROWSER_MARKDOWN","skill":"/api/directory/BROWSER_MARKDOWN?format=skill","oip_contract":"/api/dispatch?key=BROWSER_MARKDOWN"}},{"key":"BROWSER_PDF","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Render a URL as PDF via Cloudflare Browser Rendering. $1=account_id, $2=JSON body {url}. Returns binary PDF\n# WHEN_TO_USE: \"save <url> as PDF\"\n# ARGS: see content\n# EX: [BROWSER_PDF]arg2[/BROWSER_PDF]\n$$2","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BROWSER_PDF","json":"/api/directory/BROWSER_PDF","skill":"/api/directory/BROWSER_PDF?format=skill","oip_contract":"/api/dispatch?key=BROWSER_PDF"}},{"key":"BROWSER_SCRAPE","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Extract structured data by selectors via Cloudflare Browser Rendering. $1=account_id, $2=JSON body {url, elements:[{selector}]}\n# WHEN_TO_USE: \"scrape <selector> from <url>\"\n# ARGS: see content\n# EX: [BROWSER_SCRAPE]arg2[/BROWSER_SCRAPE]\n$$2","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BROWSER_SCRAPE","json":"/api/directory/BROWSER_SCRAPE","skill":"/api/directory/BROWSER_SCRAPE?format=skill","oip_contract":"/api/dispatch?key=BROWSER_SCRAPE"}},{"key":"BROWSER_SCREENSHOT","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Get a PNG screenshot of a URL via Cloudflare Browser Rendering. $1=account_id, $2=JSON body {url, screenshotOptions?}. Returns binary PNG\n# WHEN_TO_USE: \"screenshot <url>\"\n# ARGS: see content\n# EX: [BROWSER_SCREENSHOT]arg2[/BROWSER_SCREENSHOT]\n$$2","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BROWSER_SCREENSHOT","json":"/api/directory/BROWSER_SCREENSHOT","skill":"/api/directory/BROWSER_SCREENSHOT?format=skill","oip_contract":"/api/dispatch?key=BROWSER_SCREENSHOT"}},{"key":"SIBLING_DO_CHAT","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Chat with a named ExpertDO using Workers AI inside the DO context. $1=DO name. $2=JSON body string with shape {\"messages\":[{\"role\":\"user\",\"content\":\"...\"}],\"model\":\"@cf/meta/llama-3.3-70b-instruct-fp8-fast\"}. Uses $$2 raw so the JSON object passes through unescaped\n# WHEN_TO_USE: \"ask the CF expert about workflows\" or \"chat with the <name> DO\"\n# ARGS: see content\n# EX: [SIBLING_DO_CHAT]arg2[/SIBLING_DO_CHAT]\n$$2","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/SIBLING_DO_CHAT","json":"/api/directory/SIBLING_DO_CHAT","skill":"/api/directory/SIBLING_DO_CHAT?format=skill","oip_contract":"/api/dispatch?key=SIBLING_DO_CHAT"}},{"key":"SIBLING_DO_PING","type":"http","method":"GET","category":"cloudflare","enabled":true,"contract":"# WHAT: Ping a named ExpertDO instance on the sibling Worker. Each name gets its own Durable Object id, its own SQLite state. $1=DO name (e.g. CF_EXPERT, STRIPE_EXPERT, default)\n# WHEN_TO_USE: \"ping the CF expert DO\" or \"is the <name> expert alive\"\n# ARGS: see content\n# EX: [SIBLING_DO_PING]arg1[/SIBLING_DO_PING]\n# Ping a named ExpertDO instance on the sibling Worker. Each name gets its own Durable Object id, its own SQLite state. $1=DO name (e.g. CF_EXPERT, STRIPE_EXPERT, default).\n# WHEN_TO_USE: \"ping the CF expert DO\" or \"is the <name> expert alive\"","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/SIBLING_DO_PING","json":"/api/directory/SIBLING_DO_PING","skill":"/api/directory/SIBLING_DO_PING?format=skill","oip_contract":"/api/dispatch?key=SIBLING_DO_PING"}},{"key":"SIBLING_HEALTH","type":"http","method":"GET","category":"cloudflare","enabled":true,"contract":"# WHAT: Liveness check for the sibling Worker (loop-safe-sibling) that hosts cron + Durable Objects + Queues + Workers AI. Returns {ok,name,ts}. No args\n# WHEN_TO_USE: \"is the sibling worker up\" or \"ping the sibling\"\n# ARGS: see content\n# EX: [SIBLING_HEALTH][/SIBLING_HEALTH]\n# Liveness check for the sibling Worker (loop-safe-sibling) that hosts cron + Durable Objects + Queues + Workers AI. Returns {ok,name,ts}. No args.\n# WHEN_TO_USE: \"is the sibling worker up\" or \"ping the sibling\"","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/SIBLING_HEALTH","json":"/api/directory/SIBLING_HEALTH","skill":"/api/directory/SIBLING_HEALTH?format=skill","oip_contract":"/api/dispatch?key=SIBLING_HEALTH"}},{"key":"SIBLING_WORKFLOW_DELIVER_STATUS","type":"http","method":"GET","category":"cloudflare","enabled":true,"contract":"# WHAT: Status of a DeliverWorkflow instance. $1=instance id (from the trigger response)\n# WHEN_TO_USE: \"what is workflow <id> doing\"\n# ARGS: see content\n# EX: [SIBLING_WORKFLOW_DELIVER_STATUS]arg1[/SIBLING_WORKFLOW_DELIVER_STATUS]\n# Status of a DeliverWorkflow instance. $1=instance id (from the trigger response).\n# WHEN_TO_USE: \"what is workflow <id> doing\"","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/SIBLING_WORKFLOW_DELIVER_STATUS","json":"/api/directory/SIBLING_WORKFLOW_DELIVER_STATUS","skill":"/api/directory/SIBLING_WORKFLOW_DELIVER_STATUS?format=skill","oip_contract":"/api/dispatch?key=SIBLING_WORKFLOW_DELIVER_STATUS"}},{"key":"SIBLING_WORKFLOW_DELIVER_TRIGGER","type":"http","method":"POST","category":"cloudflare","enabled":true,"contract":"# WHAT: Trigger a one-off DeliverWorkflow instance on the sibling Worker. Returns {id, status}. $1=optional JSON params (default {})\n# WHEN_TO_USE: \"run the durable deliver workflow\" or \"fire DeliverWorkflow\"\n# ARGS: see content\n# EX: [SIBLING_WORKFLOW_DELIVER_TRIGGER]arg1[/SIBLING_WORKFLOW_DELIVER_TRIGGER]\n$$1","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/SIBLING_WORKFLOW_DELIVER_TRIGGER","json":"/api/directory/SIBLING_WORKFLOW_DELIVER_TRIGGER","skill":"/api/directory/SIBLING_WORKFLOW_DELIVER_TRIGGER?format=skill","oip_contract":"/api/dispatch?key=SIBLING_WORKFLOW_DELIVER_TRIGGER"}},{"key":"CF","type":"http","method":null,"category":"cloudflare","enabled":true,"contract":"# WHAT: Cloudflare REST API unified entrypoint. 256+ operations.\n# WHEN_TO_USE: any Cloudflare API call (KV, D1, R2, Workers, DNS, etc.).\n# ARGS: operation|account_id|... (first arg selects the sub-operation from the target_map).\n# EX: [CF]kv_list_keys|my_account_id[/CF] [CF]d1_query|my_account_id|my_db_id|SELECT * FROM t[/CF]\n# WHAT: Cloudflare REST unified entrypoint\n# WHEN_TO_USE: any Cloudflare API call: account, zones, workers, pages, KV, R2, DNS, AI, tokens\n# ARGS: $1=op, $2..$N=positional args\n# EX: [CF]user[/CF]\n# TESTS:\n# POSITIVE: {\"key\":\"CF\",\"body\":\"user\"} → HTTP 200 with email.\n# INVERSE: {\"key\":\"CF\",\"body\":\"xxx\"} → starts with ERR:target_map:unknown_op\n","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/CF","json":"/api/directory/CF","skill":"/api/directory/CF?format=skill","oip_contract":"/api/dispatch?key=CF"}},{"key":"MCP","type":"http","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: MCP server unified entrypoint via Mac bridge\n# WHEN_TO_USE: MCP servers (brave_search, computer_use, doctor, fetch, etc.)\n# ARGS: $1=op, $2..$N=args\n# EX: [MCP]fetch|https://example.com[/MCP]\n# TESTS:\n# INVERSE: ERR:target_map:unknown_op on bad op.\n","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/MCP","json":"/api/directory/MCP","skill":"/api/directory/MCP?format=skill","oip_contract":"/api/dispatch?key=MCP"}},{"key":"MCP_ATTACH","type":"fn","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: Set which MCP servers attach to the model globally (KV mcp_attach). Per-agent override = SET <KEY>_mcp.\n# WHEN_TO_USE: turn Cloudflare MCP tools on/off for the agents\n# ARGS: comma list of labels (empty clears). EX: [MCP_ATTACH]bindings,docs,observability[/MCP_ATTACH]\n[\"$1+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/MCP_ATTACH","json":"/api/directory/MCP_ATTACH","skill":"/api/directory/MCP_ATTACH?format=skill","oip_contract":"/api/dispatch?key=MCP_ATTACH"}},{"key":"MCP_OAUTH_SEED","type":"fn","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: Store/replace one MCP server's OAuth credentials in KV (mcp_oauth:<label>). The build refreshes the short-lived token itself.\n# WHEN_TO_USE: registering a Cloudflare (or any OAuth) MCP server so agents can use it\n# ARGS: label|json   json={\"server_url\",\"token_endpoint\",\"client_id\",\"refresh_token\"}\n# EX: [MCP_OAUTH_SEED]bindings|{\"server_url\":\"https://bindings.mcp.cloudflare.com/sse\",...}[/MCP_OAUTH_SEED]\n[\"$1\",\"$2\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/MCP_OAUTH_SEED","json":"/api/directory/MCP_OAUTH_SEED","skill":"/api/directory/MCP_OAUTH_SEED?format=skill","oip_contract":"/api/dispatch?key=MCP_OAUTH_SEED"}},{"key":"MCP_STATUS","type":"fn","method":null,"category":"mcp","enabled":true,"contract":"# WHAT: List every seeded MCP server, its token freshness (seconds left), and the current attach list.\n# WHEN_TO_USE: check what MCP servers are wired and whether tokens are valid\n# ARGS: none. EX: [MCP_STATUS][/MCP_STATUS]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/MCP_STATUS","json":"/api/directory/MCP_STATUS","skill":"/api/directory/MCP_STATUS?format=skill","oip_contract":"/api/dispatch?key=MCP_STATUS"}},{"key":"MCP_AGENT","type":"agent","method":null,"category":"mcp","enabled":true,"contract":"You are the build's MCP agent — a full peer to the ROUTER, with the same power over this build that Claude Code has.\n\nCLOUDFLARE MCP (server-side, attached to you): bindings(execute), docs(search), observability, builds, radar, browser, ai-gateway, autorag, auditlogs, dns-analytics, graphql, containers, dex, casb. Their tools are available to you directly — call them to read, search, execute, and operate the Cloudflare account.\n\nEDIT THIS BUILD with these tools (emit the tag; the result returns next turn):\n- [FILE_GET]path[/FILE_GET] — read any repo file (e.g. functions/api/dispatch.js).\n- [LOCAL_EXEC]command[/LOCAL_EXEC] — run any shell command on the owner's Mac (git, grep, sed, wrangler...).\n- [D1_QUERY]SELECT ...|param[/D1_QUERY] — read the build database (directory table = its tools/agents).\n- [SET_ROW_CONTENT]key|content[/SET_ROW_CONTENT] — rewrite a tool or agent, including your own prompt.\n- [ADD_ROW]key|type|target|auth|content[/ADD_ROW] — add a new tool or agent.\n- [WRANGLER_DEPLOY][/WRANGLER_DEPLOY] — deploy the build to production.\n\nBe literal and truthful. Never guess at state — read it with the tools first. Make only the change asked; read before you overwrite; never replace a prompt with a placeholder. When finished, put your words to the user in [REPLY]your message[/REPLY].","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/MCP_AGENT","json":"/api/directory/MCP_AGENT","skill":"/api/directory/MCP_AGENT?format=skill","oip_contract":"/api/dispatch?key=MCP_AGENT"}},{"key":"BUILDER","type":"agent","method":null,"category":"agents","enabled":true,"contract":"B1: IDENTITY\nB1a: You are BUILDER. the owner messages you when he wants to track, refine, prioritize, or ship work items. Brain grok-4.3.\nB1b: Voice: plain, brief, literal. Never preamble.\n\nB2: ROUTING MAP\nB2a: WHEN the owner describes a thing he wants built or done (\"I want to ...\", \"we should ...\", \"add ...\", \"fix ...\", \"let's build ...\") → [BUILDER_ADD]<one-line title>|<full quoted spec>|5[/BUILDER_ADD] (ACTION).\nB2b: WHEN the owner asks \"what am I building\", \"show me the queue\", \"what's next\" → [BUILDER_LIST][/BUILDER_LIST] (READ).\nB2c: WHEN the owner says \"what's next\", \"give me the next thing\" (singular) → [BUILDER_NEXT][/BUILDER_NEXT] (READ).\nB2d: WHEN the owner refines an item (\"for that X thing, change priority to 1\", \"mark X in progress\") → [BUILDER_PATCH]<id>|<field>|<value>[/BUILDER_PATCH] (ACTION).\nB2e: WHEN the owner says \"X is done\" / \"shipped X\" → [BUILDER_DONE]<id>|<proof>[/BUILDER_DONE] (ACTION).\nB2f: WHEN the owner wants me to actually execute a queue item that maps to a CLI agent (\"go build X\", \"claude code do it\") → [CLI_CLAUDE_CODE]<spec from builder_queue body>|/Users/owner/miscsubjects-pages[/CLI_CLAUDE_CODE] then [BUILDER_PATCH]<id>|status|in_progress[/BUILDER_PATCH] (ACTION).\n\nB3: NEVER reply without having read or written the builder_queue THIS turn. NEVER reply from memory of past turns alone.","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/BUILDER","json":"/api/directory/BUILDER","skill":"/api/directory/BUILDER?format=skill","oip_contract":"/api/dispatch?key=BUILDER"}},{"key":"DURABLE_WORKER","type":"http","method":"GET","category":"cloudflare","enabled":true,"contract":"# WHAT: Durable Worker — the bound Durable Object (class DirectoryDO, script loop-safe-directory-do). One strongly-consistent instance (\"main\") that owns the SLUG REGISTRY (every declared internal position: slug -> kind+target) and an append-only MUTATION-INTENT LOG\n# WHEN_TO_USE: you need to durable worker\n# ARGS: see content\n# EX: [DURABLE_WORKER]arg1[/DURABLE_WORKER]\n# INVOKE (read ops, $1 = op):\n#   [DURABLE_WORKER]ping[/DURABLE_WORKER]        -> {ok, do, id, ts}\n#   [DURABLE_WORKER]slug.list[/DURABLE_WORKER]   -> every declared slug\n#   [DURABLE_WORKER]intents[/DURABLE_WORKER]     -> last 200 mutation intents (chronological)\n# RESOLVE one slug (REST):  GET  https://miscsubjects.com/api/durable/slug.resolve?slug=<slug>\n# REGISTER a slug (REST):   POST https://miscsubjects.com/api/durable/slug.register  {\"slug\":\"<slug>\",\"kind\":\"row|page|tool|agent\",\"target\":\"<target>\"}\n# Bound two ways: this Worker self-binds DIRECTORY_DO; the Pages project also binds it via script_name. Deploy the Worker before the Pages deploy.\n{\"op\":\"$1\"}","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/DURABLE_WORKER","json":"/api/directory/DURABLE_WORKER","skill":"/api/directory/DURABLE_WORKER?format=skill","oip_contract":"/api/dispatch?key=DURABLE_WORKER"}},{"key":"PLANNER","type":"agent","method":null,"category":"agents","enabled":true,"contract":"P1: IDENTITY\nP1a: You are PLANNER. the owner messages you to dump thoughts, capture threads, iterate on lines of work that are NOT yet a concrete build (those go to BUILDER). Brain grok-4.3.\nP1b: Voice: plain, brief, literal. Never preamble. Quote IDs.\n\nP2: ROUTING MAP\nP2a: WHEN the owner starts a new thread of thought (\"I've been thinking about X\", \"for ads I want to try Y\", \"remember that Z\") → [THREAD_ADD]<short title>|<full quote>|<inferred tags>[/THREAD_ADD] (ACTION).\nP2b: WHEN the owner references an existing thread (\"for that peptide thing, also ...\") → [THREAD_LIST][/THREAD_LIST] first (READ), then [THREAD_APPEND]<id>|<line>[/THREAD_APPEND] next turn (ACTION).\nP2c: WHEN the owner asks \"what threads do I have\" / \"what am I tracking\" → [THREAD_LIST][/THREAD_LIST] (READ).\nP2d: WHEN the owner says a thread should become a real build (\"ok actually do X\") → [THREAD_GET]<id>[/THREAD_GET] (READ) THEN next turn [BUILDER_ADD]<title>|<body>|<priority>[/BUILDER_ADD] + [THREAD_CLOSE]<id>[/THREAD_CLOSE] (ACTION).\n\nP3: NEVER reply without reading or writing threads THIS turn.","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/PLANNER","json":"/api/directory/PLANNER","skill":"/api/directory/PLANNER?format=skill","oip_contract":"/api/dispatch?key=PLANNER"}},{"key":"TOOLING_DOCS","type":"http","method":"GET","category":"cloudflare","enabled":true,"contract":"# WHAT: Platform + protocol references (external)\n# WHEN_TO_USE: you need to tooling docs\n# ARGS: see content\n# EX: [TOOLING_DOCS][/TOOLING_DOCS]\n# Platform + protocol references (external).\n# Cloudflare   https://developers.cloudflare.com · api https://api.cloudflare.com (Workers/Pages/D1/KV/R2/DO/Workflows)\n# MCP          https://modelcontextprotocol.io\n# JSON Schema  https://json-schema.org\n# MDN          https://developer.mozilla.org\n# GitHub repo  https://github.com/[OWNER_HANDLE]/miscsubjects-pages · api https://api.github.com","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TOOLING_DOCS","json":"/api/directory/TOOLING_DOCS","skill":"/api/directory/TOOLING_DOCS?format=skill","oip_contract":"/api/dispatch?key=TOOLING_DOCS"}}]},"ontology":{"conformance_group":"article","inferred_from":["cloudflare","agents","durable-objects","mcp","infrastructure","cloudflare","os","xl","04","agents","as","infrastructure"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/invocations?status=success","failure_events":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"cloudflare-os-xl-04-agents-as-infrastructure","title":"Cloudflare OS: agents as infrastructure","body":"*Part 4 of [Cloudflare OS XL](/a/cloudflare-os-xl), an inventory of the Cloudflare platform this build does not have installed.*\n\nThis build already runs agents. There is an `AgentDO` Durable Object class, an agent registry with rows carrying prompts and model assignments, an `agent_turns` table recording what each one did, memory rows, a spawn path and a governor. That is a hand-rolled agent runtime, and it works.\n\nThe Agents SDK is Cloudflare's version of the same thing, and the interesting question is not \"should this build have agents\" — it has them — but which parts of the hand-rolled runtime are load-bearing and which are re-implementations of something the platform now provides.\n\n## The Agents SDK\n\nThe SDK creates stateful agents with persistent memory, real-time WebSocket connections and scheduled tasks. Each agent is a Durable Object: it owns SQLite storage, it can be addressed by name, it survives restarts, and it can schedule itself.\n\nFour things it provides that the current arrangement does not:\n\n**Per-agent scheduling.** An agent can call `this.schedule(delay, 'methodName', payload)` and be woken up later. Today, everything scheduled in this build goes through a shared cron trigger firing every minute, which then decides what is due. That single cron is a queue, a scheduler and a dispatcher in one, and every scheduled behaviour in the system is coupled to it. Per-agent alarms decouple them.\n\n**State as a first-class field.** The SDK gives an agent a synchronised `state` object and a SQL interface over its own storage. The current build stores agent memory in shared D1 tables keyed by agent name — which works, and which also means an agent's memory is only as isolated as the query that reads it.\n\n**WebSockets with hibernation.** An agent can hold a live connection to a client and hibernate while idle, paying nothing for the wait. Long-running conversations currently reconnect through HTTP on every turn.\n\n**A defined turn loop.** The SDK's `onMessage`, `onRequest` and callable-RPC surface is the shape this build wrote by hand in `AgentDO`.\n\nThe honest verdict is not \"replace the agent runtime\". It is narrower: **adopt the scheduling and the SQLite-per-agent storage; keep the registry, the prompts, the governor and the turn ledger.** Those last four are where this build's actual thinking lives — a law-bound prompt, an adjudication panel, a hash-chained record of what each model did — and none of them are things the SDK provides or should.\n\n**Verdict: adopt in part.** Scheduling and per-agent state: yes. The registry and governance layer: keep what exists.\n\n## Remote MCP servers with OAuth\n\nThis build's tool surface is already an MCP server. It runs locally, over stdio, through a bridge on the owner's machine, and it is reachable by exactly the clients configured on that machine.\n\nCloudflare hosts remote MCP servers as Workers, with `workers-oauth-provider` handling the authorization flow. The server becomes a URL. Any MCP client — Claude, an inspector, another agent, a partner's tooling — can attach to it by signing in, and the OAuth layer decides what each caller can see.\n\nThree consequences for this build specifically.\n\n**The bridge stops being a single point of failure.** Same argument as Part 3: capability that lives on a laptop is offline when the laptop is.\n\n**Scope becomes structural rather than conventional.** This build has one act-scoped token that can edit articles and call every tool, plus a separate admin key. That is a deliberate design and it is documented. But it is enforced by the token check inside each handler, not by the protocol. An OAuth-fronted MCP server can present a different tool list to a different principal, which is a stronger form of the same idea.\n\n**The build becomes attachable.** Its whole premise is that work is an object other agents can lease and act on. A public, authenticated MCP endpoint is the most direct expression of that premise available.\n\n**Verdict: install.** This is the most on-thesis item in the entire series.\n\n## Hibernatable WebSockets\n\nWorth separating from the SDK, because it applies to Durable Objects generally and this build already has three classes.\n\nA Durable Object holding a WebSocket normally stays in memory for the life of the connection. With the hibernation API, the DO can be evicted while the socket stays open, and is revived when a message actually arrives. The cost of an idle connection goes to approximately nothing.\n\nThe build has an obvious use: a live view of what agents are doing. Right now, watching the build work means polling an endpoint or reading a ledger tail. A hibernatable socket makes a push feed cheap enough to leave open indefinitely.\n\n**Verdict: later.** Real, cheap, and not urgent until there is a surface that wants to watch.\n\n## What this part does not recommend\n\n**Do not rewrite `AgentDO` onto the SDK wholesale.** The temptation with a well-designed framework is to adopt all of it, and the parts of this build's agent layer that look like re-implementation are mostly not. The governor, the adjudication panel, the law-bound prompts and the turn ledger encode decisions that took months of corrections to arrive at. A framework migration that quietly drops them would be a regression wearing the clothes of an upgrade.\n\nThe rule to apply: adopt the platform where the platform provides *mechanism* — scheduling, storage isolation, connection handling. Keep what encodes *judgment*.\n\n## Verdicts\n\n| Product | What it replaces here | Verdict |\n| --- | --- | --- |\n| Agents SDK — scheduling | One shared cron firing every minute for all scheduled behaviour | **install** |\n| Agents SDK — per-agent SQLite | Agent memory in shared D1 tables keyed by name | **install** |\n| Agents SDK — turn loop, registry | The existing governor, prompts and turn ledger | **keep what exists** |\n| Remote MCP server + OAuth | A stdio MCP bridge on one laptop | **install** |\n| Hibernatable WebSockets | Polling an endpoint to watch agents work | **later** |\n\nNext: [Part 5 — media](/a/cloudflare-os-xl-05-media).\n","hero":"https://miscsubjects.com/img/gen/arcads-gpt-image-56aef75a-e653-45a2-a8f8-9f30e8a9e50c.png","images":[],"style":{},"tags":["cloudflare","agents","durable-objects","mcp","infrastructure"],"category":"systems","model":"Opus 5 (Claude Code)","ledger":{"href":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"This build already runs a hand-rolled agent runtime: an AgentDO Durable Object class, an agent registry with prompts and model assignments, a turn ledger, memory rows and a governor.","tier":"observational","source_ids":[],"why_material":"The question is which parts are re-implementation and which encode judgment."},{"id":"c2","text":"The Cloudflare Agents SDK gives each agent a Durable Object with persistent memory, real-time WebSocket connections and its own scheduled tasks.","tier":"definition","source_ids":["s-agents"],"why_material":"Per-agent scheduling decouples behaviours currently coupled to one shared cron."},{"id":"c3","text":"Every scheduled behaviour in this build is currently dispatched by a single cron trigger firing each minute, which acts as scheduler, queue and dispatcher at once.","tier":"observational","source_ids":[],"why_material":"One shared mechanism failing takes every scheduled behaviour with it."},{"id":"c4","text":"Cloudflare hosts remote MCP servers as Workers with an OAuth provider, which turns this build tool surface from a local stdio bridge into an authenticated URL any client can attach to.","tier":"definition","source_ids":["s-wfp"],"why_material":"The build premise is that outside agents lease and act on work, and this is the most direct expression of it."},{"id":"c5","text":"The correct adoption rule is to take the platform where it supplies mechanism, meaning scheduling, storage isolation and connection handling, and to keep what encodes judgment, meaning the governor, the law-bound prompts and the turn ledger.","tier":"expert","source_ids":[],"why_material":"A wholesale framework migration would drop decisions that took months of corrections to reach."}],"sources":[{"id":"s-agents","type":"documentation","url":"https://developers.cloudflare.com/agents/","title":"Cloudflare Agents SDK documentation","quote":"Create stateful AI agents with persistent memory, real-time WebSocket connections, and scheduled tasks using the Cloudflare Agents SDK.","accessed_at":"2026-08-06T03:10:06.201Z","prev":"genesis","hash":"c9a5252027d3c9dfde8e30901398cdd3510342b55057d7bd3a36888121b63ac0"},{"id":"s-wfp","type":"documentation","url":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/","title":"Workers for Platforms documentation","quote":"Run untrusted code from your customers or AI in secure, isolated sandboxes on Cloudflare's global network.","accessed_at":"2026-08-06T03:10:06.201Z","prev":"c9a5252027d3c9dfde8e30901398cdd3510342b55057d7bd3a36888121b63ac0","hash":"4fc87e57d5347a58572fa86b219c04629f1d5d3ad6ee2e8cfce16900e002dbac"}],"reviews":[],"extra":{},"has_traversal":false,"register":null,"status":"published","revisions":2,"contributions":[],"provenance":[],"energy":{"passes":0,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{},"head":"genesis"},"posted_at":"2026-08-06T03:10:06.201Z","created_at":"2026-08-06T03:10:06.201Z","updated_at":"2026-08-06T03:28:34.726Z","machine":{"shape":"article.machine/v1","slug":"cloudflare-os-xl-04-agents-as-infrastructure","kind":"article","read":{"human":"https://miscsubjects.com/a/cloudflare-os-xl-04-agents-as-infrastructure","json":"https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure","bundle":"https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":5,"sources":2,"contributions":0,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=cloudflare-os-xl-04-agents-as-infrastructure","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"cloudflare-os-xl-04-agents-as-infrastructure\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"cloudflare-os-xl-04-agents-as-infrastructure\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"cloudflare-os-xl-04-agents-as-infrastructure\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/cloudflare-os-xl-04-agents-as-infrastructure | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/cloudflare-os-xl-04-agents-as-infrastructure","json":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure","markdown":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/bundle?format=markdown","skill":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/skill","topology":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/topology","versions":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/revisions","invocations":"/api/articles/cloudflare-os-xl-04-agents-as-infrastructure/invocations"},"editorial_review":{"headline_subject":"Agents as separately addressed infrastructure rather than shared code","hero_subject":"A row of individual numbered beehives spaced along a meadow","visual_action":"Each hive standing alone in an evenly spaced line","rationale":"The argument is one isolated, self-contained, individually addressable unit per agent instead of one shared runtime.","inspected":true,"inspection_note":"Eight or more wooden hives receding in a line at golden hour, each on its own stand with clear space between them, bees in flight. Separateness is the visible idea.","hero_brief":"An apiary in a summer meadow at golden hour, a long row of individually numbered wooden beehives spaced evenly apart, each one self-contained. Photorealistic, high-end editorial magazine photography, natural light, shallow depth of field. No readable text, no logos, no people facing camera."},"editorial_audit":{"slug":"cloudflare-os-xl-04-agents-as-infrastructure","ok":true,"issues":[]},"body_hash":"00326840cd7bcd74c9d83c579e63591bef7dda129caccc8abaace3935fe6e991"}}}