# Requirements: v1.80 Hypothesis Route Transition Intent Surface

## Milestone Goal

Close the next post-`v1.79` research-control gap so AITP can turn
route-transition eligibility into one operator-visible transition intent,
instead of forcing operators to infer the concrete source-to-target handoff
after the gate becomes available.

## Completed Requirements

### Route Transition-Intent Surface

- [x] `REQ-HINTENT-01`: runtime surfaces can materialize a bounded route
  transition-intent summary from route choice plus route-transition gating.
- [x] `REQ-HINTENT-02`: replay/read paths expose the proposed source route,
  target route, and intent status instead of leaving that intent implicit.

### Coexistence Rule

- [x] `REQ-HINTENT-03`: the route transition-intent surface coexists cleanly
  with the current route_transition_gate surface and helper mechanisms instead
  of auto-triggering runtime mutation.

### Verification

- [x] `REQ-VERIFY-01`: the milestone closes with one bounded isolated
  route transition-intent acceptance path plus targeted regression coverage for
  the new intent surface.

## Requirement Outcomes

- `REQ-HINTENT-01`: validated through `route_transition_intent` payload
  materialization on the active research contract plus runtime protocol
  rendering.
- `REQ-HINTENT-02`: validated through replay visibility for proposed, ready,
  and checkpoint-held transition intent.
- `REQ-HINTENT-03`: validated through the bounded acceptance lane that keeps
  route transition intent, route transition gating, and helper mechanisms
  visible without automatic runtime mutation.
- `REQ-VERIFY-01`: validated through the dedicated isolated acceptance lane and
  targeted replay/schema/runtime regression slices.

## Traceability

| Requirement | Phase | Status |
|-------------|-------|--------|
| REQ-HINTENT-01 | Phase 154 | Complete |
| REQ-HINTENT-02 | Phase 154 | Complete |
| REQ-HINTENT-03 | Phase 154 | Complete |
| REQ-VERIFY-01 | Phase 154 | Complete |
