simmer-judge-boardlisted

# Simmer Judge Board Dispatch a panel of judges, let them score independently, deliberate, and converge on consensus scores + a single ASI. The board's output is identical to a single judge's output — the orchestrator can't tell the difference. ## Why a Board A single judge has blind spots. It anchors on whatever it notices first, and its ASI reflects one perspective. Three judges with different lenses catch different things and challenge each other. The ASI that emerges from deliberation is stronger because blind spots get surfaced. This matters most at plateaus — when a single judge keeps suggesting the same class of fix because it can't see the real bottleneck. ## Context You Receive The board receives the same context the single judge would receive (passed through from the orchestrator): - **Current candidate**: full artifact text or key workspace files - **Criteria rubric**: 2-3 criteria with descriptions of what 10/10 looks like - **Iteration number**: which round this is - **Seed calibration** (iteration 1+): original seed + iteration-0 scores - **Evaluator output** (if evaluator mode): stdout/stderr from evaluator command - **Context discipline extras** (code/pipeline only): previous ASI, iteration history, search space, exploration status Plus board-specific context: - **JUDGE_PANEL** (optional): custom judge definitions from setup brief - **Problem class**: text/creative, code/testable, or pipeline/engineering - **ARTIFACT_TYPE**: single-file or workspace —