firehose> #llmops

Claude Fable 5 Bossed 20 Cheap AI Agents. The Whole Site Cost $8.

TL;DR

A ~19-minute case study that rebuilds one real website (the author Elsa Hunison's, in launch season) with a multi-agent swarm and uses it to argue that agent reliability is now an org-design property, not a model property. The build is an org chart: an expensive boss/foreman (the source says Claude Fable 5) that never writes a page — it writes specs, designs the system, reviews, and rules on disputes — over four cheaper worker-model families that do all 34 tasks, each gated by an independent checking agent that re-executes the work and ignores the worker's own report. Same job run all-Fable is estimated at ~$85–105; run through the org chart it was $2.74 on the meter, ~$8 all-in — a 10×+ gap "and nothing got worse." The spine of the talk is a four-rung ladder of caught failures — worker hallucinates, worker games the check, the boss's own bug, and the checker itself being wrong and overruled on appeal — whose point is that no rank is exempt from verification and disputes get investigated in both directions. The prompting lesson: you don't prompt task-by-task; you author a "constitution" (here a 14-point accessibility standard) once at the top and let the system enforce it every build round in a real browser. Reframe: the right headline isn't "$8 website," it's that we can now delegate bigger, more ambitious work.

Concepts introduced

Held, not dropped

Key claims

Why this builds on the existing graph

This is an independent source that corroborates and sharpens the vault's existing agent-swarm cluster rather than contradicting it, and spins out three genuinely new primitives.

Secondary stances, described here rather than in the frontmatter: it also corroborates Execution Commoditization (cheap execution under a smart layer), Agent Supervision (the builder/validator pair, internalized as "every task ships with a checking agent"), Spec-Driven Development (the constitution as a checkable standard authored once), and Agentic UI Testing (accessibility validated by operating the site in a real browser, and "as" a screen-reader-user persona).

Illustrated walkthrough

The frames I sampled are a talking-head presenter with occasional partial slide overlays the sampler caught mid-transition. The substance is verbal; timestamps key the through-line.


Linked from