6 guidelines, live from D1
Brand guidelines
Every row cites a real source. Filter with ?section=voice_traits (or tone_do, tone_dont, terminology, example_good, example_bad). See how these were discovered.
Voice traits Voice traits
Terse, technical, evidence-first
Short declarative sentences. No marketing superlatives. States plainly what is real versus what is planned. Cites exact file paths, grep results, or curl output as evidence rather than making unverified claims.
source: observed across workers/subagentcache, workers/subagentidentities, workers/subagentcitations READMEs
Do Do
Do
State provenance explicitly, for example manual_dashboard_paste versus graphql_api, or grounded-in-docs versus invented. Cite the exact source file or quote. Write "not yet built" or "documented, not done" rather than implying completeness that does not exist.
source: observed across subagentcache.com and subagentcontracts.com concept pages
Don't Don't
Do not
Do not use marketing language such as revolutionary, seamless, or cutting-edge. Do not invent example data to fill a schema. Do not claim automation exists before it is actually built.
source: inferred from the absence of such language across all shipped sites in this family
Terminology Terminology
Canonical terms
primitive: a D1-backed durable concept generalized from a real schema (Contract, Task, Identity, Citation, Cache, Rubric, Outcome, Evaluation, Brand). dogfood: a contract or task on subagentcontracts.com or subagenttasks.com that tracks this repository's own use of its own primitive. grounded: content traceable to a real, cited source rather than invented. provenance: a field or column that honestly distinguishes how a piece of data arrived, such as source on cache_snapshots.
source: CLAUDE.md and workers/subagentcache/src/index.ts
Good example Good example
A real example of the voice
The row above is not a live API call, it is manual_dashboard_paste: the account owner opened their own Cloudflare Analytics dashboard, read the Cache widget, and pasted the exact figures in on 2026-07-01. That is a deliberate, load-bearing design choice, not a shortcut.
source: workers/subagentcache/src/index.ts homepage()
Bad example Bad example
The anti-pattern this family avoids
Powered by cutting-edge real-time analytics and seamless AI-driven insights! This is the hypothetical anti-pattern: it claims automation (real-time, AI-driven) that was not actually built, and it uses marketing adjectives (cutting-edge, seamless) instead of a plain, checkable statement of what is real.
source: hypothetical contrast, written for this guideline only