cloudflare-core

name	cloudflare-core
description	Shared reference for the Cloudflare cluster: the edge-compute + binding model every Worker turns on, wrangler.jsonc conventions, compatibility_date, the storage-primitive decision matrix (KV vs R2 vs D1 vs Durable Objects), secrets, and the auth-token gotcha. USE WHEN adding a binding, choosing a storage primitive, writing wrangler config, or debugging a Cloudflare deploy — the interlocking rules every Cloudflare spoke shares.
cluster	cloudflare
version	1.0.0

Cloudflare Core

Shared model for the cloudflare cluster. The compute, storage, and deploy spokes all depend on these interlocking concepts — keep them consistent here so no spoke contradicts another.

1. The compute + binding model (Cloudflare's defining shape)

Everything you ship is compute at the edge that reaches the rest of the platform only through bindings. There is no ambient global state and no import of a database client — a resource exists to your code only if it is declared as a binding:

Request ──> Worker / Pages Function ──binding──> KV · R2 · D1 · Durable Object · Queue · AI · send_email · Service
                                       (declared in wrangler.jsonc, injected on env)

• Worker — the unit of compute; a fetch/scheduled/email/queue handler running on every edge node. New code & reviews → ; deploys → .