Proposer stage — produce ONE question worth answering plus the decisive test that would falsify it. Generate 5 mutually-distinct candidates grounded in the provided literature corpus and data description, each with surprise/risk/parent + nearest-priors, feasibility probes, and adversarial kill-tests, then pick the winner and write its pre-registered research arc to hypothesis.md. Topic-agnostic: the domain is set by the run-context topic brief. Carries the inputs, method, output contract, and constraints.
Planner stage — operationalize the decisive test into ONE flat, runnable item list plus a column-and-formula-precise plan + a metadata-feasibility verdict. Topic-agnostic; the data is whatever the data-metadata docs (data/INDEX.md + registers/<slug>.md) describe. Owns the group-free manifest contract (plan.md + manifest.json + feasibility.json) and the numbers-are-cited rule. Feasibility is metadata/design-level (no data bytes): confirm columns exist + a documented join path, never a measured rate.
The ReviewerCommittee gate — ONE gate-parameterized review skill. Convene the current gate's STATIC persona subset as parallel independent depth-1 sub-agents (fresh context each), then ASSEMBLE their scores into the machine-readable verdict.json the driver reads. Carries the per-gate persona subsets, each persona's lens, the flag vocabulary, and the EXACT verdict schema. Topic-agnostic. Must be invoked explicitly.