Designer and Architect
Turns direction into a concrete plan, then has it reviewed.
Direction is not a plan.
The Analyst says what is wrong and roughly what should change. This stage decides what that actually means in your codebase: which components, which files, which copy, and in what order.
It is the one stage that is itself an orchestrator. The Architect plans, and sub-agents review what it planned before a single line gets written. Nothing here touches your repo. The output is still only a document.
In, and out.
Each stage takes one thing and produces one thing. Nothing runs in parallel, and nothing loops back.
High-level direction from the Analyst
A component-level change plan, signed off on brand and on risk
What it is good at.
Technical planning
Decides which components and files change, and how, before a line is written.
Design principles
The Designer sub-agent checks the plan against your existing design system.
Legal review
A Legal sub-agent runs a live search for current compliance rules. Conditional, not every run.
Who signs off.
The Architect does not get the last word on its own plan.
Designer
Reviews the plan against your existing design system, so a conversion win never arrives as something visually off-brand.
Legal
Runs a live search for current compliance rules touching the change. Claims, disclosures, and consent language get checked against what is true now, not what was true at training time.
Restrictive zones.
You can mark any component or file fully off-limits. Pricing tables, checkout, anything load-bearing enough that you would rather it never move. This stage will not plan a change that touches them, and no stage downstream can either.
Legal pages do not need marking. The Legal sub-agent already covers that risk.
Go touch grass.
Vivere is not open yet. Join the waitlist and we will come to you first.