The quality mode chip in the composer — Fast, Reviewed, Council — decides what happens between the agent finishing the build and the result landing in front of you. It's a per-run switch: cheap drafts run Fast, the pass you mean to ship runs Council.
Fast
One agent, one pass, straight to the gate. Fast is for iteration — throwaway variants, exploratory steers, "what if we tried" runs. You still get the design-kit gate's checks, just no extra review on top. Most runs in a working session are Fast; the speed is the point.
Reviewed
The build finishes, then a review pass reads the result against the brief and the kit before it lands — catching the things a build can get subtly wrong: a section that answers the wrong question, a hierarchy that fights itself, copy that doesn't sound like the brief asked. Reviewed is the default choice for a run you're keeping but not sweating.
Council
Council fans the brief out to a panel of reviewers, each scoring a different domain — composition, type, color, responsiveness, the fit to the brief itself — then synthesizes the verdicts into one checked result. You see the review card in the transcript as it works: which reviewers ran, what each flagged, and the final call.
When it lands, the Reviewed note in the transcript reports the verdict — e.g. "all required domains passed" — and the design-checks panel shows any findings the council logged. Reviewers disagree, and that's the point: the synthesis resolves the disputes before they reach you.
Which mode when
- Fast — iterating, variants, exploratory steers
- Reviewed — a normal turn you're keeping
- Council — the final pass on work that ships: a landing page going live, a deck going to a client, a brand board going to print
Council costs more turns and takes longer — save it for the pass that matters rather than running everything through it.
Tip: Run variants Fast, blind-compare to pick the direction, then one Council pass on the winner. You get the panel's rigor where it counts without paying for it on drafts.