5
Cluster routes
All secondary modes now grouped under one explicit scaffold.
3
Exploratory modes
Sandbox, map, console, and presentation routes for focused operator work.
2
Reference-adjacent
Curated feed and infrastructure-heavy routes kept secondary to the core reference stack.
I / N / R
Best exits
Return to Intelligence, Incidents, or Research once the question stops being specialist.
Exploratory specialist modes
Use these when you need depth, density, or experimentation
These routes are valuable precisely because they are not the default product entry. Use them for freeform scanning, dense console work, simulation, or presentation, then route back into the canonical stack once the output becomes a real object, evidence chain, or reference question.
Reference-adjacent specialist lanes
Keep these secondary, even when they matter
News, infrastructure, and cable context can be release-critical, but they should still read as disciplined supporting surfaces. This hub keeps them connected to the main reference and flagship hierarchy instead of letting them drift into parallel-product status.
Cluster discipline
Intelligence stays the flagship live operating surface.
Incidents keeps reviewed public evidence separate from exploratory specialist work.
Research remains the umbrella for comparison and reference context once the specialist route has done its narrow job.