# Roadmap: v1.71 Runtime Transition And Demotion History

## Result

`v1.71` is complete.

## Overview

`v1.71` closed the bounded runtime-history gap without widening into full
parallel-hypothesis management. It added structured transition history,
demotion-aware replay, and a dedicated isolated acceptance path.

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

## Phase Details

### Phase 145: Structured Transition And Demotion Trace

**Goal:** Add one structured runtime history path for forward/backward layer
transitions and make demotion reasons replayable.

**Plans:** 1 plan

Plans:

- [x] `145-01`: add runtime transition/demotion trace, replay surface, and isolated acceptance

**Outcome:**

- landed `transition_history.jsonl|json|md`
- wired rejection and resume-state backtracks into structured transition rows
- surfaced the history through runtime protocol notes and topic replay
- aligned docs and tests to the new transition/demotion lane

## Milestone Summary

**Key Accomplishments:**

- one structured runtime transition log now exists
- one explicit demotion-history surface now exists
- one replay/read path now explains what got sent backward and why

**Issues Resolved:**

- closed the gap where `resume_stage` and `last_materialized_stage` answered
  only the current state, not the bounded path that produced it
- closed the gap where promotion rejection was durable only as gate state/log,
  not as a replayable transition surface

**Issues Deferred:**

- human override modification capture in the promotion gate
- full competing-hypothesis modeling
- broader evaluator-divergence analytics

**Technical Debt / Honest Gaps:**

- the first slice records bounded transition history, but not yet the precise
  human content modifications that may have changed an approved L2 result

---

For current planning state after `v1.71`, continue from the next active
milestone and fresh requirements definition.
