# Requirements Archive: v2.8 Selected-Candidate Route Choice Closure

**Archived:** 2026-04-14
**Status:** SHIPPED

For current requirements, see `.planning/REQUIREMENTS.md`.

---

# Requirements: v2.8 Selected-Candidate Route Choice Closure

## Milestone Goal

Make post-selection continuation coherent enough that, once a selected staged
candidate becomes the selected route on a fresh topic, the loop derives one
bounded deeper route choice and advances beyond the candidate-summary
placeholder instead of stalling there forever.

## Active Requirements

### Route Choice Beyond Selected Candidate

- [x] `RCC-01`: once `selected_consultation_candidate_followup` is already the
  selected route and the operator continues again, the bounded loop derives one
  first deeper route choice from the selected staged candidate.

- [x] `RCC-02`: that deeper route choice is written as a durable runtime
  artifact rather than remaining only a transient queue guess.

### Public Post-Selection Advancement

- [x] `RCC-03`: public `next`, `status`, and equivalent dashboard surfaces stay
  aligned on the same first deeper route chosen after selected-candidate
  closure.

### Replayable Proof

- [x] `RCC-04`: one replayable fresh-topic proof shows the same topic can
  advance beyond selected-candidate summary into one bounded deeper route
  choice while the earlier staged-L2 and consultation-selection baselines still
  pass.
