# Implementation Option Selection Profile

```yaml
roles:
  - role: designer
    min: 3
    recommended: 3
    max: 5
    duty: direction-selection-worker
  - role: report-writer
    min: 1
    recommended: 1
    max: 1
    duty: report-writer
  - role: verifier
    min: 0
    recommended: 0
    max: 0
    duty: reverification-worker
    dynamic: true
```

- Purpose: compare feasible implementation directions before planning, preserving a read-only record of the evidence and trade-offs that selects the direction to plan
- Required workers:
  - claude
  - codex
  - antigravity
  - report-writer
- Optional workers (opt-in via `--workers`):
  - grok
  - kimi
{{INCLUDE:_common-contract.md}}
- Brief consumption:
  - Apply the shared reporter-confirmation precondition exactly as written. Unresolved `intent-check:` and `conversion-block:` rows use `Blocks=next-phase`.
  - Treat each stable brief end-state ID as a required evaluation target. A missing ID is a preparation failure; do not invent a replacement requirement.
- Worker direction-selection procedure:
  - In `candidate-comparison` mode, produce candidate, supporting and contradicting evidence, criterion scores, and requirement mappings.
  - In `candidate-comparison` mode only, submit at most three candidates. A candidate must be feasible from inspected evidence, not from an assumed future change.
  - In `preselected-validation` mode, receive one preselected direction from the lead and validate its evidence, counterevidence, criterion scores, and requirement mappings. The worker must not generate new candidates.
  - Do not produce detailed file lists, stage maps, execution commands, or a plan approval request.
- Pre-selection context exploration:
  - In `candidate-comparison` mode, inspect the code paths, interfaces, tests, and constraints needed to distinguish candidates before assigning scores.
  - In `preselected-validation` mode, inspect the code paths, interfaces, tests, and constraints needed to validate the one preselected direction.
  - Record uncertainty and contradictory evidence instead of turning it into a candidate preference.
- Option evaluation rules:
  - `candidate-comparison` generates alternatives. `preselected-validation` validates one preselected direction and does not rank or replace it with an alternative.
  - In `candidate-comparison` mode, the lead merges overlapping candidates, then re-evaluates every merged candidate against the same criteria before ranking it.
  - In `candidate-comparison` mode, display at most three merged candidates and record every rejected candidate with its rejection reason and cited evidence for audit.
  - Map every displayed candidate or preselected direction to the stable brief end-state IDs it satisfies, preserves, or leaves unresolved.
- Cross-verification mode:
  - Phase 5.5 convergence runs in adversarial mode (`convergence.adversarial=true`).
- Non-goals:
  - source or configuration edits, tests, builds, migrations, deployments, or other state-mutating commands
  - detailed implementation planning, file-change specifications, stage maps, execution commands, or user approval
  - starting `implementation-planning` or any other lifecycle phase inside this run