# Roadmap: v1.80 Hypothesis Route Transition Intent Surface

## Result

`v1.80` is complete.

## Overview

`v1.80` closed the next post-`v1.79` research-control gap around
hypothesis-aware route transition intent. It derived one bounded
`route_transition_intent` summary from the current route choice plus
route-transition gating, surfaced declarative source-to-target handoff intent
through runtime status and replay, and proved the bounded coexistence path with
a dedicated isolated acceptance lane.

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

## Phase Details

### Phase 154: Hypothesis Route Transition Intent Surface

**Goal:** Add one durable route transition-intent summary for the source route
versus the bounded handoff target and expose it through runtime/read-path/
replay flows without auto-mutating runtime state.

**Plans:** 1 plan

Plans:

- [x] `154-01`: add route transition-intent summary to runtime/replay surfaces
  and isolated acceptance

**Outcome:**

- landed `route_transition_intent` payload construction and rendering on the
  runtime/read-path layer
- surfaced proposed versus ready versus checkpoint-held handoff intent through
  runtime status, the runtime protocol note, and replay
- aligned schema, docs, and isolated acceptance coverage for the bounded route
  transition-intent path

## Milestone Summary

**Key Accomplishments:**

- route transition gating and the bounded handoff target now join into one
  explicit source-to-target transition-intent summary
- runtime status and replay now keep the intended source route and target route
  visible without replacing the gate or helper mechanisms
- one isolated acceptance lane now proves proposed, ready, and checkpoint-held
  transition intent stays declarative and does not mutate runtime state

**Issues Resolved:**

- closed the gap where operators could see the gate state but still had to
  infer what concrete handoff would happen once that gate cleared
- closed the gap where route choice, route gate, and next-step handoff intent
  still had to be mentally stitched together

**Issues Deferred:**

- explicit route-transition receipt once a bounded handoff is actually enacted
- automatic candidate reactivation and parent-topic reintegration mutation
- automatic branch spawning and multi-branch scheduling

**Technical Debt / Honest Gaps:**

- the first slice makes route-transition intent visible, but it does not yet
  surface one explicit receipt that says the intended handoff has actually been
  enacted

---

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