Use case · Space-weather surge
After the storm, re-baseline the fleet without dropping a deadline.
Stale assessments retired, the fleet re-baselined, approvals batched by deadline.
What this shows
Simulation. A recorded severe storm builds. Surge mode marks pre-storm conjunction assessments stale, re-screening from post-storm states retires the invalidated ones and adds new events, and burns plus low-drag mode are uplinked inside their windows.A surge puts every decision on deadline.
Storm-enhanced drag moves every trajectory.
The full picture
In the May 2024 storm, thousands of satellites manoeuvred at once, and researchers questioned whether existing conjunction-assessment procedures cope in storm conditions [1]. Every assessment made before the storm is suspect, the backlog arrives all at once, and the deadlines do not move.
How ConstellOps handles it
- 01Surge mode
- 02Retire stale data
- 03Re-baseline
- 04Batch without blurring
- 05Keep service up
Each step in full
- 01Surge modeA storm alert puts the fleet supervisor into surge mode. It dispatches work; it never commands directly.
- 02Retire stale dataPre-storm CDMs and ephemerides are marked invalid and are not used for new decisions.
- 03Re-baselineOrbits are re-propagated from post-storm states by solvers, and conjunction assessment runs again.
- 04Batch without blurringProposals are batched for approval. Each keeps its own gate verdicts, deadline and default action, and anything that misses its cutoff is flagged to the on-console team at once.
- 05Keep service upThe network-incident agent tracks the capacity impact of manoeuvres and gateway effects.
One queue, same rules.
Autonomy level and approvals
Every agent in the surge runs at A1: a person approves every command. Batching groups items for review; it never changes what the gates allow.
Every deadline held through the surge.
Full results table and notes
20 runs of a recorded geomagnetic storm replayed over a synthetic fleet, on ConstellOps v1.0.0rc4. No matched classical comparison exists for this workflow.
See it in the operations console
What this shows
A recorded G5 storm. Pre-storm assessments are retired; the actionable events are re-proposed; burns and drag-mode commands are uplinked inside their windows.More console captures

What this shows
Storm onset and surge close in the operations console.What this shows
The operator's signed approval of a collision-avoidance burn during the surge: provenance, gate verdicts and the integrity block.
What this shows
Re-baseline on post-storm states: invalidated assessments are retired and new events appear.
What this shows
Conjunctions re-ranked on post-storm data, tagged RE-BASELINED or NEW.
What this shows
Storm alert: surge mode on, and pre-storm conjunction assessments marked stale.
What this shows
Surge batches keep the queue workable; each item is re-gated and signed.What it is not
Not a space-weather forecast. It consumes alerts.
The limits, listed
- Not a space-weather forecast. It consumes alerts.
- Not onboard drag response.


