The Process

A roster of specialized agents, each with one job. Directors who own the story and the canon, a writer, a critic, a continuity auditor, specialists who make the art. One orchestrator runs the floor — it dispatches the right agent, routes the work through the gates, brokers disagreements, and logs every decision. It never writes a word of the book itself. The moment the conductor picks up an instrument, the orchestra falls apart.

Here is the part most people miss: the agents do not share memory. Each one runs in its own isolated context and forgets everything the moment it finishes. So they cannot talk — they communicate through artifacts. Task cards carry the handoffs. Canon is referenced by file, never pasted, so the world cannot drift. The governance logs are the project's memory, living outside any single agent. And every output is graded by a different agent before it counts.

Every chapter ran the same pipeline, ending where it mattered most: the gates. Before a chapter survived, it was attacked from every side — a critic held to a literary-award standard, a cold first-reader who was never allowed to see the rules, a continuity auditor, a risk audit, a read-aloud pass, a final ratification. The orchestrator brokered the verdicts. A chapter shipped only when every gate read clean. When the critic and the writer disagreed, it became a literal prosecution and defense.

Four things, if you want to build your own. Separate the maker from the judge — the agent that writes never grades its own work. Make memory external — agents forget, so the memory lives in files, not the chat. Route by cognitive load — the deepest model for judgment, the fastest for mechanical work. And gate everything with a hard verdict: pass, needs-fixes, or reject. “Looks good” is not a verdict.