Simulation orchestration is still a placeholder, but the route is already fed by terrain and cascade contracts so boundary-condition summaries can be rendered before the GPU layer exists.
Phase 2 Operations
Adaptive operational intelligence for interacting mountain systems
A shared operational shell for cascading hazard intelligence, terrain state awareness, seismic trigger interpretation, simulation orchestration, and adaptive response workflows.
Cascade Simulation
Flood, debris, sediment, and blockage evolution
This view will orchestrate and compare ensemble runs for interacting cascade scenarios using GPU-ready flood and debris simulation services.
Scenario Trigger
seis-evt-0007
Current cascade source event for orchestration handoff.
Amplification
69%
Used to prioritize ensemble budget and execution urgency.
Terrain Instability
74%
One of the seed state variables for scenario generation.
Cascade cascade-003 in watch state
The current interaction chain has 3 ordered steps available to seed scenario generation.
Planned outputs
- Simulation run registry
- Scenario comparison panels
- Arrival-time and inundation products
- Blockage evolution and energy dissipation traces
Primary data sources
- Simulation service run manifests
- Terrain state and sediment inputs
- Cascade event boundary conditions
- Infrastructure exposure results
Implementation workstream
Define simulation request and result schemas first so the frontend can bind to stable contracts while the GPU orchestration layer is still being built.