Full Technical Findings & Reproducible Telemetry
1. Privilege Separation Between Builders and Judges
Code-authoring steps execute inside isolated git worktrees via sandboxed CLIs (Claude Code, Codex, or Antigravity). Conversely, all eight evaluation and external-input roles (QA Engineer, Plan Critic, Security Gate, Market Researcher, Competitor Analyst, Product Manager, and Growth Strategist) execute strictly over tool-less HTTP APIs with zero filesystem write access.
2. One-Sided Z = 1.64 Statistical Promotion
Candidate model configurations run on 50% of production tasks for up to 14 days. A challenger is promoted to default only if total tokens per merged PR drops by at least 10% at Z >= 1.64 (95% one-sided confidence) with non-inferior merge velocity. Learned heuristics that fail to reduce their target error signature by >= 30% are pruned automatically.