Ava intakes. Oliver plans and writes the score.
Ava is the intake: she captures what Mike said, structures it, and handles the recurring EA work herself. Anything that is a new build, a multi-step project, or touches client deliverables gets handed to Oliver, who understands intent, plans the work, and writes the score.
- Ava captures the ask and handles routine EA work directly.
- Oliver takes anything that needs planning or a build.
- Mike gives GO on the score Oliver writes.
Oliver writes the score and gets approval
Oliver understands the intent behind the request, plans the work, and writes the score, pulling in Dan and the accountable domain leads for the sections they own. Mike reviews that score and gives GO before any build begins.
- Oliver drafts the blueprint and reconciles every section.
- Dan and domain leads contribute the sections they own.
- Mike gives GO on the finalized score.
Dan and Cody dual signoff locks the score
Before build starts, Dan (head developer, the Claude coding lane) and Cody (the Codex coding lane) both review the approved score and sign off on it. That dual signoff is today's real gate ahead of execution, not a single reviewer's call.
- Dan signs off from the Claude coding lane.
- Cody signs off from the Codex coding lane.
- Only a score both have signed becomes bounded work.
Carlos conducts the leads
After dual signoff, Carlos dispatches the approved score to the accountable domain leads, sequences dependencies, collects evidence, and routes findings back to whoever owns them. Carlos never performs the implementation, the fix, the output QA, or the process QA himself.
- Required reads and mutation boundaries travel with each task.
- Domain leads implement and correct their own sections.
- Carlos coordinates dependencies and evidence only.
Queen does the independent QA
Queen owns output QA, verifying visible changes with real evidence: screenshots, browser tests, and accessibility checks against what the score actually asked for. Carlos waits for Queen's verdict and routes any correction back to the accountable owner before the work goes out.
- Queen records expectations before observing results.
- Queen returns an evidence-backed pass or fail verdict.
- Carlos routes every finding to its accountable owner.
Petey reviews process after delivery. Oliver delivers.
Once Queen's verdict passes, Dan completes final engineering review and proof, and Oliver confirms the result against the score and delivers to Mike. Only after that delivery does Petey step in, independently reviewing whether the score, prompts, skills, workflows, agents, validators, hooks, routing, or SOPs need to improve for next time.
- Dan's final review and proof happen after Queen's pass.
- Oliver confirms against the score and delivers to Mike.
- Petey reviews process only after delivery, never as a gate.