# Phase 150: Hypothesis Route Re-entry Surface - Discussion Log

> **Audit trail only.** Do not use as input to planning, research, or execution agents.
> Decisions are captured in CONTEXT.md.

**Date:** 2026-04-12
**Phase:** 150-hypothesis-route-reentry-surface
**Areas discussed:** parked-route re-entry visibility, relation to deferred/follow-up mechanics, bounded scope

---

## Surface Placement

| Option | Description | Selected |
|--------|-------------|----------|
| extend parked-route metadata with re-entry summaries | preserves one visible hypothesis-level truth path | ✓ |
| invent a separate re-entry subsystem | would fragment the operator model | |

## Relation To Existing Mechanisms

| Option | Description | Selected |
|--------|-------------|----------|
| coexist with deferred reactivation and follow-up reintegration mechanisms | keeps current execution surfaces intact | ✓ |
| auto-trigger mutation from the new summary | widens scope too far | |

## Scope

| Option | Description | Selected |
|--------|-------------|----------|
| declarative route re-entry visibility | closes the immediate gap cleanly | ✓ |
| automatic reactivation or parent-topic patching | too wide for the immediate next milestone | |
