# AI should do the implementation. You should own the decisions. > Source: > Published: 2026-06-13 09:59:45+00:00 The default for AI-assisted development is one of two failure modes. Either you're babysitting the agent line by line — approving each diff, re-explaining context it dropped three messages ago — or you've handed it the wheel and you're hoping the PR that lands at the end resembles what you asked for. **Son of Anton is neither.** It's a delivery orchestrator built on a single claim: there are exactly three moments where a developer's judgment is irreplaceable. The orchestrator owns everything in between. Every project moves through three human decision points. Nothing important happens without you signing off. **Gate 01 — Approve the WHAT** (`/soa plan` ) A grill-me session forces the AI to surface its assumptions, constraints, and scope decisions *back to you* before a single ticket exists. You say yes or you refine. It does not proceed until you have. **Gate 02 — Approve the HOW** (`/soa decompose` ) The approved plan becomes a ticket stack — ordered, dependency-aware, sized for review. Architectural judgment stays with you. Ticket authorship goes to the agent. **Gate 03 — Approve DONE** (`/soa closeout` ) An adversarial subagent reviews every ticket before its PR opens. When the phase is complete, *you* decide whether to accept. Closeout squash-merges the stack onto main. Nothing merges without you. That's the whole point. Once you've approved the plan and the tickets, the orchestrator runs the loop: