Role selection belongs to the run
A model choice is not a UI preference. The server checks the catalog and credentials before queueing. An unavailable role fails clearly instead of silently switching providers.
MODEL-SEPARATED REVIEW
Let one model build. Let another challenge it.
PiGO validates and pins separate provider/model choices for Developer and Reviewer when a run starts. The Reviewer receives a controlled snapshot and acceptance context, then returns structured findings.
Deterministic gates come before reviewer tokens
Type checks, lint, and tests produce cheaper, more stable facts. Only a passing result advances to diff, scope, and acceptance review.
Review findings become the next engineering round
Changes requested are not left as an unstructured reply. Scoped evidence returns to the Developer as a visible round; non-convergence creates a Decision Brief for a human.
IMPLEMENTED, NOT IMPLIED
The review path includes
- Independent provider/model selection
- Model and credential preflight
- Controlled reviewer snapshots
- Finding fingerprints and duplicate detection
- Repair rounds and convergence protection