Case studies
Most of these came out of actually running zz -- rehearsing a demo, hitting a real error, tracing it to a root cause, and writing it up with the evidence rather than a guess. Some are bugs in Cloudflare's own platform that zz works around; some are gaps in zz itself, fixed or still open. Three are a different kind of evidence: How zz is built on Cloudflare applies the same "here's the actual code and the actual tradeoff" treatment to the whole stack zz runs on rather than to one bug, Competition entrants applies it to other projects solving nearby problems, for whatever's actually worth synthesizing back in, and Designing on principle applies it to the design process itself -- what it actually takes to check a project's existing design against values stated only after most of that design already existed.
| Page | What it covers |
|---|---|
| Designing on principle | Writing Principles down made existing values checkable for the first time -- the checkpoint audit of everything designed before it existed, and why that audit has to repeat. |
| From a standing-ask Coordinator to directed selection | A real design mistake caught mid-flight: Charter's first draft modeled a privileged planning role on a misread of the Hugging Face incident's own coordinator, corrected only by actually reading the primary source instead of a confident secondhand summary. |
| How zz is built on Cloudflare | Workers, Durable Objects, and Artifacts as the real execution substrate -- the specific implementation choices each one forced, and the limitations that shaped them. |
| Corrupted incremental git fetch | A real fetch-pack: protocol error: bad band #78 bug in Cloudflare Artifacts' own git-upload-pack, root-caused with a full protocol trace and worked around in zz repo clone's defaults. |
| Conflict resolution silently drops tasks | A failed resolve_conflict gives up and denies with no retry and no visible signal -- a real gap in zz's own protocol logic, not yet fixed. |
| Concurrent coordinators corrupt a shared clone | Running two coordinator-scope zz work processes against the same repo races on one shared local git clone -- not yet fixed; run at most one coordinator per repo for now. |
| Competition entrants | Other entries in Cloudflare's "next git platform" competition, evaluated for ideas worth synthesizing back into zz. Grows as more turn up. |