## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `cloudflare-community`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/cloudflare-community/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/cloudflare-community/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/cloudflare-community/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/cloudflare-community/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/cloudflare-community/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/cloudflare-community/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `cloudflare-community` v2 · content_hash `38ae65ec05af9230…` · thread_head genesis
- **thesis (c1):** Cloudflare publishes a repository named cloudflare-os, created on 15 April 2026 and last pushed on 5 August 2026, describing an agent workspace built on Workers for running agents with a company context.
  - c2 [expert/active] On any Cloudflare question this build agents should fetch the product llms-full.txt before answering, and should never answer a platform question from a model p
  - c3 [expert/active] Where the documentation and the runtime disagree, workerd is the authority, because it is the runtime that actually executes the code.
  - c4 [observational/active] Cloudflare publishes its own instructions for teaching coding agents to build on the platform, in a repository with 2,558 stars as of 6 August 2026.
  - c5 [observational/active] Sunil Pai has 917 commits to the Cloudflare Agents SDK and is also a contributor to the sandbox SDK, Wrangler and the OAuth provider library.
  - c6 [observational/active] The official Cloudflare Developers Discord had 94,307 members at the time this page was written, and is where Cloudflare staff answer questions in public.
  - c7 [observational/active] This build has thirteen Cloudflare products bound in production and four products verified empty on the account: Vectorize, Hyperdrive, Pipelines and Containers
  - c8 [expert/active] The two decisions this build most wants challenged are that a Tail Worker should be what turns a production failure into a task row, and that Code Mode is the c
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/cloudflare-community/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/cloudflare-community/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `cloudflare-community`
- **title:** Cloudflare Community: who this build should defer to
- **url:** https://miscsubjects.com/a/cloudflare-community
- **register:** standard
- **updated:** 2026-08-06T03:35:24.668Z
- **tags:** cloudflare, community, research-hub, agents, open-source

## Body

> **This page is a research hub, not an essay.** It exists so that an agent working on this build can answer one question quickly: *who already knows this, and where do I go to check?* Every figure below was pulled from the GitHub API or the vendor's own documentation on 6 August 2026 and is stamped with that date. Anything not verified is marked UNKNOWN rather than estimated.

This build runs on Cloudflare. Thirteen products are bound and in production, and the [Cloudflare OS series](/a/cloudflare-os-xl) inventories the rest. That inventory was produced by reading the account and the docs. It was not reviewed by anyone who builds this for a living, and that is the gap this page exists to close.

## The finding that reframes the rest

Cloudflare ships a repository called **cloudflare-os**.

[github.com/cloudflare/cloudflare-os](https://github.com/cloudflare/cloudflare-os) — 3,008 stars, created 15 April 2026, last pushed 5 August 2026. Its own description: "Agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company's context and systems."

That is, in one sentence, what this build is. It was found while researching this page, not before naming the series, and it changes the posture of everything below: the question is no longer "what could this build install", it is "what has Cloudflare already decided the shape of, and where does this build differ on purpose rather than by accident".

## The canonical surfaces an agent should defer to

Ranked by how much weight to give them when they disagree with anything else, including this site.

| Rank | Surface | Why it wins |
| --- | --- | --- |
| 1 | `developers.cloudflare.com/<product>/llms-full.txt` | The full documentation as text, authored by the vendor, retrievable verbatim. Never summarise it from a search result. |
| 2 | [`cloudflare/workerd`](https://github.com/cloudflare/workerd) — 8,486 stars | The runtime source. When behaviour and documentation disagree, the runtime is right. |
| 3 | [`cloudflare/workers-sdk`](https://github.com/cloudflare/workers-sdk) — 4,397 stars | Wrangler itself. Config shapes, binding names and error strings originate here. |
| 4 | [`cloudflare/agents`](https://github.com/cloudflare/agents) — 5,371 stars | The reference implementation of an agent on this platform. |
| 5 | [`cloudflare/skills`](https://github.com/cloudflare/skills) — 2,558 stars | Cloudflare's own instructions for teaching coding agents to build here. Directly comparable to this build's skill rows. |
| 6 | [Cloudflare Developers Discord](https://discord.gg/cloudflaredev) — 94,307 members | Where staff answer in public. Searchable through Answer Overflow. |
| 7 | [community.cloudflare.com](https://community.cloudflare.com/) | The official forum. Slower, more durable, indexed. |
| 8 | [r/CloudFlare](https://www.reddit.com/r/CloudFlare/) — approximately 34,000 members | Operator-level reality: what breaks in production and what support actually said. |

**Standing rule for this build's agents:** on any Cloudflare question, fetch `llms-full.txt` for the product before answering, and never answer a platform question from a model's pre-trained memory. If the runtime and the docs disagree, cite the runtime.

## The repositories that define current practice

All counts verified 6 August 2026.

### Cloudflare's own

| Repository | Stars | Last push | What it settles |
| --- | --- | --- | --- |
| [moltworker](https://github.com/cloudflare/moltworker) | 9,928 | 2026-05-09 | Running a full agent harness on Workers |
| [workerd](https://github.com/cloudflare/workerd) | 8,486 | 2026-08-06 | The runtime itself |
| [agentic-inbox](https://github.com/cloudflare/agentic-inbox) | 6,736 | 2026-04-23 | An email client with an agent, entirely on Workers |
| [agents](https://github.com/cloudflare/agents) | 5,371 | 2026-08-05 | The Agents SDK |
| [workers-sdk](https://github.com/cloudflare/workers-sdk) | 4,397 | 2026-08-06 | Wrangler |
| [cloudflare-os](https://github.com/cloudflare/cloudflare-os) | 3,008 | 2026-08-05 | An agent workspace with company context |
| [skills](https://github.com/cloudflare/skills) | 2,558 | 2026-07-24 | Teaching agents to build here |
| [templates](https://github.com/cloudflare/templates) | 2,050 | 2026-08-05 | The starting shapes |
| [workers-oauth-provider](https://github.com/cloudflare/workers-oauth-provider) | 1,851 | 2026-08-05 | Authenticated remote MCP servers |
| [sandbox-sdk](https://github.com/cloudflare/sandbox-sdk) | 1,090 | 2026-08-05 | Isolated code execution |
| [actors](https://github.com/cloudflare/actors) | 414 | 2026-04-23 | A friendlier Durable Objects surface |

### The ecosystem

| Repository | Stars | Maintainer | Relevance here |
| --- | --- | --- | --- |
| [honojs/hono](https://github.com/honojs/hono) | 31,598 | Yusuke Wada | The router most Workers applications use |
| [opennextjs/opennextjs-cloudflare](https://github.com/opennextjs/opennextjs-cloudflare) | 1,848 | OpenNext | Framework-on-Workers, the hard edges |
| [nuxt-hub/core](https://github.com/nuxt-hub/core) | 1,279 | Sébastien Chopin | D1, KV, R2 and blob as one application layer |
| [outerbase/starbasedb](https://github.com/outerbase/starbasedb) | 1,161 | Brayden Wilmoth | SQLite on Durable Objects at scale |
| [panva/jose](https://github.com/panva/jose) | 7,735 | Filip Skokan | Token and signature primitives on Workers |

## The people

Public identities, taken from their own GitHub profiles on 6 August 2026. Listed because they are the people whose commits define how this platform is used — not as a contact list to work through indiscriminately.

**At Cloudflare**

- **Kenton Varda** — `kentonv`. Tech lead of Workers, author of Cap'n Proto. Top contributor to `cloudflare-os` and `workers-oauth-provider`. The final authority on runtime semantics.
- **Sunil Pai** — `threepointone`. 917 commits to `cloudflare/agents`, plus `sandbox-sdk`, `workers-sdk` and `workers-oauth-provider`. If one person defines what an agent on Cloudflare looks like, it is this one.
- **Brendan Irvine-Broque** — `irvinebroque`. Senior director of product for Workers.
- **Matt Silverlock** — `elithrar`. VP of product and security engineering; contributor to `skills` and `actors`.
- **Naresh** — `ghostwriternr`. 266 commits to `sandbox-sdk`; the person to ask about isolated execution.
- **Matt Carey** — `mattzcarey`. Agents and MCP.
- **Pete Bacon Darwin** — `petebacondarwin`, and **Somhairle MacLeòid** — `penalosa`. The two highest-volume contributors to Wrangler.
- **Brendan Coll** — `mrbbot`. Author of Miniflare.
- **Phillip Jones** — `jonesphillip`, and **Katrin** — `whoiskatrin`. `cloudflare-os` and the agent surface.

**Outside Cloudflare**

- **Yusuke Wada** — `yusukebe`. Hono.
- **Brayden Wilmoth** — `Brayden`, Outerbase. Durable Objects as a database.
- **Sébastien Chopin** — `atinux`, Nuxt. Bindings as an application layer.
- **Glen Maddern** — `geelen`. Contributor to `workers-oauth-provider`.
- **Kevin R. Whitley** — `kwhitley`. itty-router, itty-durable.
- **Luke Edwards** — `lukeed`. worktop.

## What this build is asking them

The solicitation sent alongside this page asks three questions, and they are the questions this page exists to get answered.

**1. Where should an agent defer?** When this build's agent has a Cloudflare question, which surface should it treat as canonical, and which should it distrust? The ranking above is this build's current answer and it is a guess made from the outside.

**2. What are the emergent practices?** Not the documented ones. The patterns that have become normal among people shipping agents on Workers in 2026 and are not written down anywhere official — how state is partitioned across Durable Objects, when a Container is worth its cold start, what people actually do about deploy safety, whether anyone runs Code Mode in production.

**3. What is obviously wrong here?** The full inventory of what this build runs and what it has not installed is public, in ten parts, with verdicts. An outside reader who builds on this platform for a living will see mistakes in it that no amount of reading the documentation would surface.

## What this build actually runs on Cloudflare

Stated in full, because a solicitation that asks for review without disclosing the object is asking for a favour rather than a critique.

**In production:** Workers and Pages; four D1 databases; one KV namespace; two R2 buckets; three Durable Object classes with SQLite; three Queues; ten Workflows across two Workers; Workers AI; AI Gateway on every model call; Browser Rendering; outbound email through a `send_email` binding; Secrets Store bound by reference; service bindings; cron triggers; observability on every Worker.

**What it does with them:** it is a public site of 1,183 articles where every article is the same object — atomized claims, each with an evidence tier and a source carrying that source's own verbatim words, rendered as addressable regions an outsider can challenge. Every action appends a hash-chained audit row. Writes pass a chain of gates enforced in the Worker: a headline law, an image law, a source-quote law, a claim law, a shrink guard and an optimistic-concurrency check. Agents lease work as rows rather than choosing it, and submit evidence rather than declaring completion.

**Verified empty on the account, 6 August 2026:** Vectorize, Hyperdrive, Pipelines, Containers.

**Not installed anywhere:** AI Search, Analytics Engine, Pipelines, R2 Data Catalog and R2 SQL, R2 event notifications, the Sandbox SDK, Code Mode, the Agents SDK, hosted MCP with OAuth, Images, Stream, Realtime, Snippets, the rate-limit binding, Turnstile, Cache Reserve, Logpush, Log Explorer, Tail Workers, gradual deployments, version metadata, Workers Builds, Tunnel, Workers VPC, mTLS bindings, Access, WAF custom rules, inbound Email Routing, API Shield, Workers for Platforms, Terraform.

The full reasoning for each, with a verdict of install, later or no, is in [the series](/a/cloudflare-os-xl).

## How to reply

Anything sent back becomes a public object here, attributed, or anonymous on request. Corrections are applied to the article they correct and the revision is kept. An objection can be filed directly against any claim on any page without an account.

The two items this build most wants challenged: that a Tail Worker is the right way to make a failure become a task row, and that Code Mode is the correct fix for an agent spending most of its calls discovering tool contracts rather than doing work.


## Claims (9)

- **c1** [observational w=?] Cloudflare publishes a repository named cloudflare-os, created on 15 April 2026 and last pushed on 5 August 2026, describing an agent workspace built on Workers for running agents with a company context.
  - sources: s-cfos
- **c2** [expert w=?] On any Cloudflare question this build agents should fetch the product llms-full.txt before answering, and should never answer a platform question from a model pre-trained memory.
- **c3** [expert w=?] Where the documentation and the runtime disagree, workerd is the authority, because it is the runtime that actually executes the code.
  - sources: s-workerd
- **c4** [observational w=?] Cloudflare publishes its own instructions for teaching coding agents to build on the platform, in a repository with 2,558 stars as of 6 August 2026.
  - sources: s-skills
- **c5** [observational w=?] Sunil Pai has 917 commits to the Cloudflare Agents SDK and is also a contributor to the sandbox SDK, Wrangler and the OAuth provider library.
  - sources: s-agents, s-sandbox, s-oauth
- **c6** [observational w=?] The official Cloudflare Developers Discord had 94,307 members at the time this page was written, and is where Cloudflare staff answer questions in public.
- **c7** [observational w=?] This build has thirteen Cloudflare products bound in production and four products verified empty on the account: Vectorize, Hyperdrive, Pipelines and Containers.
- **c8** [expert w=?] The two decisions this build most wants challenged are that a Tail Worker should be what turns a production failure into a task row, and that Code Mode is the correct fix for an agent spending most of its calls discovering tool contracts.
- **c9** [observational w=?] Hono, at 31,598 stars, is the routing layer most Workers applications are built on, which makes its maintainer a relevant authority on request handling patterns at the edge.
  - sources: s-hono

## Voxel graph (9 atoms · 7 edges)
- full graph: https://miscsubjects.com/api/articles/cloudflare-community/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (9)
- chain valid: yes · head: `28a17439ea64b23f`

### s-agents · repository
- title: cloudflare/agents on GitHub
- url: https://github.com/cloudflare/agents
- quote: Build and deploy AI Agents on Cloudflare
- hash: `36a4c602ca6969be`

### s-cfos · repository
- title: cloudflare/cloudflare-os on GitHub
- url: https://github.com/cloudflare/cloudflare-os
- quote: Agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company's context and systems.
- hash: `8f737d797719d85d`

### s-hono · repository
- title: honojs/hono on GitHub
- url: https://github.com/honojs/hono
- quote: It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, AWS Lambda, Lambda@Edge, and Node.js.
- hash: `4c470adeea8c6370`

### s-oauth · repository
- title: cloudflare/workers-oauth-provider on GitHub
- url: https://github.com/cloudflare/workers-oauth-provider
- quote: OAuth provider library for Cloudflare Workers
- hash: `30a458976ac743f4`

### s-sandbox · repository
- title: cloudflare/sandbox-sdk on GitHub
- url: https://github.com/cloudflare/sandbox-sdk
- quote: Run sandboxed code environments on Cloudflare's edge network
- hash: `5b6d15898288cccb`

### s-skills · repository
- title: cloudflare/skills on GitHub
- url: https://github.com/cloudflare/skills
- quote: Skills for teaching agents how to build on Cloudflare.
- hash: `0d6e72b15e356409`

### s-workerd · repository
- title: cloudflare/workerd on GitHub
- url: https://github.com/cloudflare/workerd
- quote: The JavaScript / Wasm runtime that powers Cloudflare Workers
- hash: `4033a6f7de8c0799`

### s-kentonv · profile
- title: Kenton Varda on GitHub
- url: https://github.com/kentonv
- quote: Tech lead of Cloudflare Workers, Cap'n Proto, Sandstorm.io.
- hash: `dd7b383f297bc690`

### s-starbase · repository
- title: outerbase/starbasedb on GitHub
- url: https://github.com/outerbase/starbasedb
- quote: HTTP SQLite scale-to-zero database on the edge built on Cloudflare Durable Objects
- hash: `28a17439ea64b23f`

## Provenance (0 model passes)
- chain valid: yes · head: `genesis`


## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/cloudflare-community/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/cloudflare-community/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"cloudflare-community","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest cloudflare-community|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim cloudflare-community|tier|assertion`
- **iMessage ask:** `cloudflare-community|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `cloudflare-community`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/cloudflare-community/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/cloudflare-community/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*