{"_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","title":"Cloudflare OS: what this build has not installed","body":"This build runs on Cloudflare. Not \"hosted on\" — runs on. The site is Cloudflare Pages. The content spine is D1. The ledger is D1 and R2. The agent memory is Durable Objects with SQLite. The models are called through Workers AI and the AI Gateway. Long jobs are Workflows. Fan-out is Queues. Page-fetching is Browser Rendering. Outbound mail is a `send_email` binding. Secrets are in Secrets Store.\n\nThat is thirteen Cloudflare products, bound and in production, doing real work every hour.\n\nIt is also less than a third of what the account can hold.\n\nThis series is the inventory of the rest: every Cloudflare product that is not installed here, what it would actually do for this specific build, and — this matters more — an honest verdict on whether it should be installed at all. A list of everything a vendor sells is a brochure. This is not that. Several entries below end in \"no\", and the reasons are given.\n\n## What is already here\n\nVerified against the account and every `wrangler.toml` in the repo on 6 August 2026, not from memory:\n\n| Product | State in this build |\n| --- | --- |\n| Workers + Pages | The site, the API, the admin surface |\n| D1 | 4 databases: content spine, shared events, storage index, previews |\n| KV | 1 namespace: settings, freeze flags, snapshots |\n| R2 | 2 buckets: ledger, store |\n| Durable Objects (SQLite) | 3 classes: DirectoryDO, ExpertDO, AgentDO |\n| Queues | 3: loop-tasks, loop-ingest, loop-ingest-dlq |\n| Workflows | 10, across two Workers |\n| Workers AI | Bound on Pages and on the sibling Worker |\n| AI Gateway | Every model call routes through it |\n| Browser Rendering | `MYBROWSER` binding on the sibling Worker |\n| Email (outbound) | `send_email` binding |\n| Secrets Store | Meta credentials, bound by reference |\n| Service bindings | STORE, META_BRIDGE |\n| Cron triggers | Every minute, and 04:00 daily |\n| Observability | Enabled on every Worker |\n\n## What is empty\n\nFour products were checked directly against the account rather than inferred from config. All four returned nothing:\n\n```\nwrangler vectorize list   →  You haven't created any indexes on this account.\nwrangler hyperdrive list  →  (empty)\nwrangler pipelines list   →  No pipelines found.\nwrangler containers list  →  No containers found.\n```\n\nEverything else in this series is absent by config scan: no binding, no route, no reference anywhere in the repo that does more than mention the name in a documentation row.\n\nThat distinction is worth stating plainly, because this build has a directory of roughly nine hundred callable rows and several of them *describe* products that are not installed. A row that documents Turnstile is not Turnstile. The inventory below counts bindings and provisioned resources, not documentation.\n\n## The ten parts\n\n**[Part 1 — Search and retrieval](/a/cloudflare-os-xl-01-search-and-retrieval)**\nVectorize, AI Search (formerly AutoRAG), and D1 read replication. The corpus is 1,171 articles and is queried with SQL `LIKE`. This is the largest single gap in the build.\n\n**[Part 2 — The ledger as a queryable table](/a/cloudflare-os-xl-02-ledger-as-a-table)**\nPipelines, R2 Data Catalog, R2 SQL, R2 event notifications, Analytics Engine. Audit questions are currently answered by pulling files and counting in a script.\n\n**[Part 3 — Running real code](/a/cloudflare-os-xl-03-running-real-code)**\nContainers, the Sandbox SDK, and Code Mode. Every heavy tool in this build shells out to the owner's laptop. That is the single biggest reliability liability in the system.\n\n**[Part 4 — Agents as infrastructure](/a/cloudflare-os-xl-04-agents-as-infrastructure)**\nThe Agents SDK, remote MCP servers with OAuth, hibernatable WebSockets. Two Durable Object classes already do a hand-rolled version of this.\n\n**[Part 5 — Media](/a/cloudflare-os-xl-05-media)**\nImages, Stream, Realtime. Hero images are generated externally and stored as raw R2 objects with no variants.\n\n**[Part 6 — The edge in front of the Worker](/a/cloudflare-os-xl-06-the-edge-in-front)**\nSnippets, the rate-limit binding, Turnstile, Cache Reserve. The admin key and the token-mint endpoint are rate-limited by nothing.\n\n**[Part 7 — Seeing what happened](/a/cloudflare-os-xl-07-seeing-what-happened)**\nLogpush, Log Explorer, Tail Workers, Workers Builds, gradual deployments. A Tail Worker is the missing mechanical link between \"it broke\" and \"a task row exists\".\n\n**[Part 8 — Reaching private things](/a/cloudflare-os-xl-08-reaching-private-things)**\nHyperdrive, Workers VPC, Tunnel, mTLS certificates. The honest fix for the local bridge.\n\n**[Part 9 — The security surface](/a/cloudflare-os-xl-09-the-security-surface)**\nAccess, WAF custom rules, inbound Email Routing, API Shield. Only half of email is installed.\n\n**[Part 10 — Hosting other builds](/a/cloudflare-os-xl-10-hosting-other-builds)**\nWorkers for Platforms, Terraform, Radar. The ceiling: the point where this stops being one site.\n\n## The two that fix existing failures\n\nEverything in this series is new capability except two entries, and those two are different in kind because they close failure classes already written into this build's failure vault.\n\n**Tail Workers** (Part 7). When a Worker throws, the trace goes to observability and a human has to go look. A Tail Worker is a Worker that consumes another Worker's invocation logs, so a thrown exception can *append a task row naming the failure class* without anyone reading a dashboard. This build's central rule is that a failure becomes a child task rather than a sentence in a report. Right now that rule depends on an agent noticing. A Tail Worker makes it mechanical.\n\n**Code Mode** (Part 3). A model calling nine hundred single-purpose tools spends most of its calls discovering contracts rather than doing work — measured on the `misc` agent, roughly fourteen of twenty calls. Code Mode inverts it: the model writes TypeScript against a generated API and runs it in a sandbox, so discovery happens once, at codegen time, instead of once per call.\n\nThose two are not enrichment. They are repairs.\n\n## How to read the verdicts\n\nEach part ends with a table of the same three columns: the product, what it would replace here, and a verdict of **install**, **later**, or **no**. \"No\" is used honestly — Waiting Room, Load Balancing and Spectrum are all real products that this build has no business installing, and saying so is more useful than listing them as opportunities.\n","register":"standard","hero":"https://miscsubjects.com/img/gen/arcads-gpt-image-bbbd28a7-826d-43a3-b84e-0503c33696f4.png","hero_brief":"A large industrial steel patch panel on a workshop wall, roughly a third of its sockets connected with neat coloured cables and the remaining two thirds empty and clearly labelled, one hand reaching toward an unused socket. Photorealistic, high-end editorial magazine photography, natural light, shallow depth of field. No readable text, no logos, no people facing camera.","editorial_review":{"headline_subject":"The Cloudflare platform this build has and has not installed","hero_subject":"An industrial patch panel with a third of its sockets connected and the rest empty","visual_action":"A hand reaching toward an unused socket","rationale":"The article is an inventory of what is plugged in versus what is available, and a patch panel is that distinction as a physical object.","inspected":true,"inspection_note":"A steel panel: five columns of sockets on the left carry neat coloured cables, the remaining twenty or so sockets are bare, and a hand is reaching for one of them. The proportion connected to empty matches the article argument.","hero_brief":"A large industrial steel patch panel on a workshop wall, roughly a third of its sockets connected with neat coloured cables and the remaining two thirds empty and clearly labelled, one hand reaching toward an unused socket. Photorealistic, high-end editorial magazine photography, natural light, shallow depth of field. No readable text, no logos, no people facing camera."},"tags":["cloudflare","infrastructure","inventory","workers","audit"],"category":"systems","style":{},"claims":[{"id":"c1","text":"Thirteen Cloudflare products are bound and running in this build: Workers, Pages, D1, KV, R2, Durable Objects, Queues, Workflows, Workers AI, AI Gateway, Browser Rendering, outbound email and Secrets Store.","tier":"definition","source_ids":[],"why_material":"It sets the baseline the rest of the series measures against."},{"id":"c2","text":"Four Cloudflare products were checked directly against the account on 6 August 2026 and returned nothing at all: Vectorize, Hyperdrive, Pipelines and Containers.","tier":"observational","source_ids":[],"why_material":"These are verified absences rather than inferred ones."},{"id":"c3","text":"A directory row that documents a Cloudflare product is not the same thing as that product being installed, and this inventory counts bindings and provisioned resources rather than documentation.","tier":"definition","source_ids":[],"why_material":"The build has roughly nine hundred documented rows, several of which describe uninstalled products."},{"id":"c4","text":"Only two items in the series repair failures already recorded in this build rather than adding new capability: Tail Workers and Code Mode.","tier":"expert","source_ids":[],"why_material":"It separates repair from enrichment, which changes the priority order."},{"id":"c5","text":"Several Cloudflare products carry a verdict of no for this account, including Waiting Room, Load Balancing and Spectrum, because the problems they solve do not exist here.","tier":"expert","source_ids":["s-wfp"],"why_material":"A complete inventory that lists every product as an opportunity is a brochure, not an assessment."}],"sources":[{"id":"s-d1","type":"documentation","url":"https://developers.cloudflare.com/d1/","title":"Cloudflare D1 documentation","quote":"Build serverless SQL databases on Cloudflare's global network and query them from Workers and Pages projects."},{"id":"s-queues","type":"documentation","url":"https://developers.cloudflare.com/queues/","title":"Cloudflare Queues documentation","quote":"Send and receive messages with guaranteed delivery using Cloudflare Queues integrated with Workers."},{"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."}],"prov":{"model":"Opus 5 (Claude Code)","action":"write"}}