DevShiftRelay
Operational twin · fulfillment control room
Relay Command Deck
Diagnose a disruption, compare three feasible recovery plans, preview one on cloned state, then commit it to the live twin.
Static no-index control room. The live twin loads with JavaScript; without it, the network map and incident briefs below remain readable.
Active incident
Fulfillment-hub outageLoading the live twin…
Diagnosis
Central Hub is unavailable for the full planning horizon. North and South must absorb throughput, inventory, and outbound lanes.
Recovery plans
Generate plans to compare three feasible, materially different recoveries built from live allocations and routes.
Baseline network snapshot
Nine nodes and fourteen directed lanes. Hubs hold inventory, transfers move freight, demand regions consume orders. This drawing is the no-JavaScript record of the twin.
Fulfillment-hub outage
Central Hub is unavailable for the full planning horizon. North and South must absorb throughput, inventory, and outbound lanes.
Directed transport-lane closure
The West Transfer to Northwest Demand lane is closed. Northwest orders must reroute through East Transfer without reversing directed lanes.
Regional demand spike plus vision-kit shortage
Southeast vision-kit demand rises while every hub is capped at a thin vision-kit stock. Priority and SLA slack decide who is served.
Seeded sandbox
A visible seed closes one lane and raises one product’s demand in one region. Copy, replay, or reset the seed to reproduce the incident exactly.