# Roadmap: v1.75 Hypothesis Route Activation Surface

## Result

`v1.75` is complete.

## Overview

`v1.75` closed the next post-`v1.74` research-control gap around explicit route
activation. It derived one bounded `route_activation` summary from explicit
hypothesis routes, surfaced the active local route plus parked-route
obligations through runtime status and replay, and proved the bounded
coexistence path with a dedicated isolated acceptance lane.

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

## Phase Details

### Phase 149: Hypothesis Route Activation Surface

**Goal:** Add one durable route-activation summary for the active local route
versus parked routes and expose it through runtime/read-path/replay flows
without replacing the action queue, deferred parking, or follow-up subtopics.

**Plans:** 1 plan

Plans:

- [x] `149-01`: add hypothesis route activation summary to runtime/replay
  surfaces and isolated acceptance

**Outcome:**

- landed `route_activation` payload construction and rendering on the
  runtime/read-path layer
- surfaced the active local action plus parked-route obligations through
  runtime status, the runtime protocol note, and replay
- aligned schema, docs, and isolated acceptance coverage for the bounded
  route-activation path

## Milestone Summary

**Key Accomplishments:**

- the active local hypothesis and its immediate bounded action are now visible
  directly on the runtime surface
- parked deferred and follow-up obligations now stay visible in runtime status
  and replay without reconstructing them from separate artifacts
- one isolated acceptance lane now proves route activation stays declarative and
  does not auto-spawn a follow-up topic directory

**Issues Resolved:**

- closed the gap where the concrete current-topic action still had to be
  inferred from separate route metadata plus queue artifacts
- closed the gap where parked-route obligations were split across deferred and
  follow-up runtime artifacts without one operator-visible summary

**Issues Deferred:**

- automatic branch spawning and multi-branch scheduling
- automatic route adjudication heuristics
- explicit parked-route re-entry summaries that lift deferred reactivation
  conditions and follow-up return contracts into the hypothesis route surface

**Technical Debt / Honest Gaps:**

- the first slice makes active-versus-parked route activation visible, but it
  does not yet surface exact deferred reactivation conditions or follow-up
  return readiness as first-class route summaries

---

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