How the cellar works.

A root cellar: open fields, a stone building off an unpaved road, good things kept in the dark. The mark is a beet in a double-ring seal — an almanac stamp. The palette is what a cellar holds: beet-skin maroon as primary, parchment grounds, sage and carrot and onion-amber in support, all under a film of dust — never a pure white or black.

Around that sit the working parts: fifteen React primitives (Button through Tooltip, styled entirely by rc-* classes and CSS tokens), seventeen guideline specimen pages, logo and avatar assets, a landing-page kit, and a written constitution — voice rules included. Sentence case everywhere. One pun per surface. No exclamation points, no emoji. This page is set in all of it, which is rather the point.

A single Cloudflare Worker in front of two stores: an R2 bucket holds every file, and a D1 database is the registry — three tables (brands, assets, revisions) that say what exists, what it means, and when it was frozen. The Worker reads both live, so publishing new content is an upload, not a deploy.

Everything answers a plain GET with CORS open — no auth handshakes for an agent to fumble. Tokens ship both ways: as the canonical CSS custom properties and as W3C Design Tokens JSON. And because the registry keys by brand slug, the next brand is a folder, three D1 rows, and a sync — the hub was built to hold several.

The one rule of the house: the Worker never lists the bucket. A file without a D1 asset row is fetchable but invisible to agents — so new files get registered, or they sit in the dark unannounced.

The design system's own landing kit, ported from React to plain HTML and served as a static Worker on the apex and www. No frameworks, no CDN scripts — the page is HTML, the system's verbatim CSS, and about thirty lines of JavaScript for the one interaction that matters: Knock opens the arch dialog with the keeper's address, and copying it earns a quiet "Copied." The footer's "lost?" leads to a genuine 404 — Nothing down here. That's rather the point.

Before it touched the apex, a dozen adversarial review agents went through it and confirmed seven findings — including a dialog that clipped on phone screens (a bug faithfully inherited from the React source) and a modal with no focus management. All seven were fixed and re-verified before launch. The DNS records it created are website-only; the planned Google Workspace MX setup is untouched.