# Roadmap: v1.78 Hypothesis Route Choice Surface

## Result

`v1.78` is complete.

## Overview

`v1.78` closed the next post-`v1.77` research-control gap around
hypothesis-aware route choice visibility. It derived one bounded `route_choice`
summary from the current local route plus the primary parked-route handoff
candidate, surfaced stay-local versus yield-to-handoff choice through runtime
status and replay, and proved the bounded coexistence path with a dedicated
isolated acceptance lane.

**Phases:** 152
**Total Plans:** 1
**Total Tasks:** 2
**Shipped:** 2026-04-12

## Phase Details

### Phase 152: Hypothesis Route Choice Surface

**Goal:** Add one durable route choice summary for the current local route
versus the primary handoff candidate and expose it through runtime/read-path/
replay flows without auto-mutating runtime state.

**Plans:** 1 plan

Plans:

- [x] `152-01`: add route choice summary to runtime/replay surfaces and
  isolated acceptance

**Outcome:**

- landed `route_choice` payload construction and rendering on the
  runtime/read-path layer
- surfaced one stay-local versus yield-to-handoff summary through runtime
  status, the runtime protocol note, and replay
- aligned schema, docs, and isolated acceptance coverage for the bounded route
  choice path

## Milestone Summary

**Key Accomplishments:**

- the current local route and the primary handoff candidate now appear together
  in one hypothesis-aware route choice summary
- runtime status and replay now keep the stay-local and yield options visible
  without replacing current-route-choice or helper mechanisms
- one isolated acceptance lane now proves route choice visibility stays
  declarative and does not mutate runtime state

**Issues Resolved:**

- closed the gap where operators could see the handoff candidate but not one
  bounded choice summary between staying local and yielding
- closed the gap where the older current-route-choice surface and the newer
  hypothesis route surfaces still had to be mentally stitched together

**Issues Deferred:**

- explicit transition gating for when route mutation is allowed
- automatic candidate reactivation and parent-topic reintegration mutation
- automatic branch spawning and multi-branch scheduling

**Technical Debt / Honest Gaps:**

- the first slice makes stay-local versus yield choice visible, but it does not
  yet show the explicit gate that says when a route transition is allowed

---

For current planning state after `v1.78`, continue from the next fresh
milestone definition.
