qalisted

> **Model routing for this tool** (from `model-routing.data.yaml`, snapshot 2026-08-17): > `frontier` → **fable** · `workhorse` → **opus** · `standard` → **sonnet** · `utility` → **haiku** > Roles → tiers: ba-challenger: standard · ba-draft: standard · dev-r1: workhorse · dev-r2: standard (high-stakes: workhorse) · dev-r3: workhorse · explore: utility · qa-challenger: standard · sa-background: workhorse · sa-challenger: workhorse · sa-writer: workhorse > Resolve at runtime: `python3 .vteam/scripts/model_route.py <role> --tool claude-code [--high-stakes]` — high-stakes diffs (review.high_stakes_*) bump dev-r2 to the workhorse tier. > Spawning a subagent: pass the resolved name as the Agent tool's `model` parameter. # /qa — verify a delivered ticket against the spec (QA lane, no code) **What this workflow is NOT:** it never edits product code, never fixes anything, never expands the dev's scope. It answers ONE question with evidence: **does the app now behave the way the spec says it should, for the requirement this ticket describes — without breaking the rest of the screen?** **Immutable principles** (violation = the verification does not count): 1. **The spec is the oracle.** "Done" means the app matches the spec (+ the schema for data rules), NOT "matches the ticket prose" and NOT "no error appears". Every expected value cites its spec section / schema line. Ticket contradicts spec → spec wins; report the contradiction. Spec silent/self-contradictory → that T