# Requirements: v1.75 Hypothesis Route Activation Surface

## Milestone Goal

Close the next post-`v1.74` research-control gap so AITP can turn explicit
hypothesis route metadata into an operator-visible route-activation surface,
instead of forcing operators to infer the concrete local-route versus
parked-route next steps from separate runtime artifacts.

## Completed Requirements

### Route Activation Surface

- [x] `REQ-HACT-01`: runtime surfaces can materialize a bounded activation
  summary from the declared route of each competing hypothesis.
- [x] `REQ-HACT-02`: replay/read paths expose the active local route action
  versus parked-route obligations directly instead of leaving activation state
  implicit.

### Coexistence Rule

- [x] `REQ-HACT-03`: the route-activation surface coexists cleanly with the
  current action queue, innovation-direction steering, deferred candidates, and
  follow-up subtopics instead of replacing those execution-level mechanisms.

### Verification

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

## Requirement Outcomes

- `REQ-HACT-01`: validated through `route_activation` payload materialization on
  the active research contract plus runtime protocol rendering.
- `REQ-HACT-02`: validated through replay visibility for active-local action and
  parked-route obligations.
- `REQ-HACT-03`: validated through the bounded acceptance lane that keeps the
  action queue, deferred buffer, and follow-up subtopics visible alongside the
  new activation surface.
- `REQ-VERIFY-01`: validated through the dedicated isolated acceptance lane and
  targeted replay/schema/runtime regression slices.

## Traceability

| Requirement | Phase | Status |
|-------------|-------|--------|
| REQ-HACT-01 | Phase 149 | Complete |
| REQ-HACT-02 | Phase 149 | Complete |
| REQ-HACT-03 | Phase 149 | Complete |
| REQ-VERIFY-01 | Phase 149 | Complete |
