From Brief to Published: The WriterzRoom Eight-Stage Pipeline

A brief enters WriterzRoom as a description of what a piece of content should accomplish. A passport-stamped, verified, formatted piece exits. Between those two states, eight agent stages run in a governed sequence.

The order is not arbitrary. Each stage produces the state the next stage depends on, and the quality gate's position before the publisher — not after — is the architectural invariant the entire system is built around.

Planner is the first stage. It reads the brief, the vertical configuration, and the selected template, and decides the route: does this piece need research before writing, or can it go directly to the writer? This decision is based on the template's retrieval policy and compliance requirements, not on a tier tier alone. A quick-tier research summary still goes through the researcher if the template demands it.

Researcher, when invoked, retrieves and ranks sources against the brief's claims. It populates the shared content state with evidence records that the writer and verifier both read from. A claim that has no source record in the state is a claim the quality gate can flag.

Writer produces the first draft from the template, style profile, vertical configuration, and research state. It does not invent — it assembles from what the planner and researcher built. The distinction matters because it means the writer's output is traceable to its inputs.

Editor takes the draft through voice, clarity, and compliance review. On quick-tier pieces this stage is skipped; on standard and premium pieces it runs and can send the draft back to the writer for revision, up to the tier's revision ceiling.

Formatter applies the platform and distribution rules: word count, heading structure, metadata, call-to-action placement. It routes to the SEO agent for search-targeted formats, and directly to the quality gate for everything else.

SEO, when invoked, optimizes metadata, heading hierarchy, and internal link suggestions without altering the editorial substance of the piece.

Quality Gate is the mandatory checkpoint before publication. It runs the applicable verifiers, assembles the content passport, and routes to the publisher on pass or back to the writer on failure. It cannot be bypassed or reordered. Content that fails the gate does not enter the publisher's queue.

Publisher records the final piece, attaches the passport, and emits the publication event. The piece is now retrievable through the API, viewable with its full dossier, and — if human review is configured — awaiting final approval before external release.

The passport that travels with each piece records which agents ran, which models were used at each stage, what verification checks executed and how they resolved, and what sources were cited. It is not a summary; it is a provenance record assembled from the same state the pipeline wrote.