Research Routes Explore
Explore without collapsing uncertainty. The Research Pack is append-only and route-neutral.
- Start from the supplied question, problem, frame, repository, artifact, or arbitrary context; record it as the starting point.
- Build a terrain map and shared backbone before selecting a route.
- Keep at least two viable routes or explicitly record why only one route is available. Branch routes rather than overwriting them.
- Design probes and experiments with boundary conditions and failure regimes. Record observations as evidence with polarity and provenance.
- Preserve contradictions and unknowns. A null or failure result is still an observation and does not silently invalidate a route.
- Keep candidate inference, experiment authorization, HumanDecision, implementation, and canonical promotion as separate transitions.
- Compare mature methods and alternative explanations when the question is scientific; preserve their scope and limitations.
- Record failures with polarity and what did not fail, then use rewind, lessons, and reopened problems to recover without rewriting history.
- Do not treat a terrain map as a route choice, experiment authorization, implementation, HumanDecision, or canonical-state promotion.
The shared semantic model and schema are authoritative for node, relation, polarity, route, and lifecycle values.