# Roadmap: v1.74 Hypothesis Branch Routing Surface

## Result

`v1.74` is complete.

## Overview

`v1.74` closed the next post-`v1.73` research-control gap around explicit
hypothesis routing. It extended each competing hypothesis with branch-routing
metadata, surfaced the active local branch plus parked routes through runtime
status and replay, and proved the bounded coexistence route with a dedicated
isolated acceptance lane.

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

## Phase Details

### Phase 148: Hypothesis Branch Routing Surface

**Goal:** Add durable branch-routing intent per competing hypothesis and expose
it through runtime/read-path/replay flows without replacing steering, deferred
parking, or follow-up subtopics.

**Plans:** 1 plan

Plans:

- [x] `148-01`: add hypothesis branch-routing metadata to question/runtime
  surfaces and isolated acceptance

**Outcome:**

- landed normalized branch-routing support on each `competing_hypotheses` row
- surfaced the active branch hypothesis plus parked-route ids/counts through
  runtime status, runtime protocol, and replay
- aligned schemas, docs, and isolated acceptance coverage for the bounded
  routing/coexistence path

## Milestone Summary

**Key Accomplishments:**

- each competing hypothesis can now declare whether it stays local, parks in
  deferred storage, routes to a follow-up branch, or remains excluded
- runtime status and replay now keep hypothesis branch intent visible without
  reconstructing it from separate surfaces
- one isolated acceptance lane now proves routing coexists with steering,
  deferred parking, and follow-up subtopics

**Issues Resolved:**

- closed the gap where operators could see competing hypotheses but not their
  intended branch destination
- closed the gap where active local versus parked hypotheses had to be inferred
  from separate runtime artifacts

**Issues Deferred:**

- automatic branch spawning and multi-branch scheduling
- hypothesis auto-adjudication heuristics
- broader action-queue activation from the new routing surface

**Technical Debt / Honest Gaps:**

- the first slice makes route intent durable and visible, but it does not yet
  convert those routes into first-class route-activation summaries or automatic
  execution helpers

---

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