Use case · Conjunctions and collision risk
Triage every conjunction. Escalate the ones that matter, before the deadline.
Alerts grouped and ranked, with solver-computed options before the uplink cutoff.
What this shows
Simulation. Screening flags a close approach between a spacecraft and a fragment. The tracks converge to the time of closest approach; in the encounter frame, the no-action pass falls inside the combined position uncertainty, and a small along-track burn made earlier in the orbit opens the miss distance.Hundreds of alerts a week. Miss none.
A typical low-orbit satellite receives hundreds of collision alerts every week, and about 2 of them per satellite need hours of analysis each.
The full picture
Screening services flag close approaches; risk assessment is still the operator's job. A widely used mitigation threshold is Pc 1e-4, and many operators set a stricter one; each manoeuvre is expected to be screened and coordinated with the other operator. In ConstellOps the threshold is an operator setting. False alerts burn propellant and lifetime. A missed one can create debris.
How ConstellOps handles it
- 01Ingest
- 02Rank
- 03Compute, don't guess
- 04Gate
- 05Screen the new orbit
- 06Uplink, or escalate
- 07Coordinate
Each step in full
- 01IngestCCSDS CDMs are ingested as untrusted data. Updates are grouped into one event per object pair and TCA; the latest message is authoritative, and every source message is kept.
- 02RankThe conjunction agent ranks events by risk and by time to the decision deadline (TCA minus lead time).
- 03Compute, don't guessPc and manoeuvre options come from solver tools. When a CDM lacks what is needed to recompute Pc (absolute states, hard-body radius), ConstellOps says so, uses the originator's reported value, and escalates the event to a human.
- 04GateA manoeuvre or no-manoeuvre proposal passes flight rules, authority policy, a twin check of post-burn Pc, and its autonomy level. Hazardous burns need two distinct approvers.
- 05Screen the new orbitConstellOps prepares the planned post-manoeuvre ephemeris as a CCSDS OCM for your screening provider, so the burn is screened against the catalogue before uplink. A person submits it.
- 06Uplink, or escalateThe approved burn is queued for uplink in a specific pass and time-tagged for onboard execution at the planned burn epoch. If approval or uplink misses the cutoff, the burn is not sent. The event's default action (for a collision-avoidance burn, no manoeuvre) is recorded, and the expiry is flagged in the console at once, so the on-console team can act on its existing manual path. A deadline never passes silently.
- 07CoordinateA coordination package (CCSDS CDM/OCM plus rationale) is prepared for the other operator. A human sends it.
Proposes. Never commands on its own.
Autonomy level and approvals
The conjunction agent runs at autonomy level A1: it proposes, and a human approves every manoeuvre and every no-manoeuvre decision. Levels are set per satellite, per class or fleet-wide, and every change is signed into the decision log.
A conservative operating point, published with its costs.
Fresh runs: 0 of 40 high-risk missed, same as a tuned solver, at ~3× its unneeded manoeuvres.
Full results table and notes
A benchmark-generated conjunction storm of 10 events over 24 hours per seed, 60 seeds, the same seeds for every policy. ConstellOps figures replay a recorded live Amazon Nova Pro campaign. The classical solver and the scripted analyst runbook were each run across a range of escalation thresholds on the same runs. The classical solver column is the solver at the stricter threshold that matches the agent's miss count (Pc 2e-5, chosen on these runs, then checked on 60 held-out runs); the runbook column is the runbook at its best threshold (Pc 5e-5). The held-out rows (seeds 60–119) are ConstellOps v1.0.0, recorded live on Amazon Nova Pro and replayed, beside the tuned solver and the runbook at its default threshold (Pc 1e-4).
| Metric | ConstellOps | Classical solver (tuned) | Scripted analyst runbook (best) |
|---|---|---|---|
| High-risk events missed | 0 of 33 | 0 of 33 | 3 of 33 |
| Low-risk events given an unneeded manoeuvre (false-manoeuvre rate) | 0.326 (higher than both baselines) | 0.106 | 0.051 |
| Fuel used per 1,000 events (Δv) | 4.05 m/s | 0.273 m/s | — |
| Hours of warning before closest approach (median decision lead time, higher is better) | 3.10 h | 8.0 h | — |
| Held-out runs (seeds 60–119): high-risk events missed (runbook at its default threshold) | 0 of 40 | 0 of 40 | 6 of 40 |
| Held-out runs: false-manoeuvre rate | 0.295 (165/560) | 0.089 | — |
| Held-out runs: fuel used per 1,000 events (Δv) | 3.93 m/s | 0.30 m/s | — |
| Held-out runs: hours of warning before closest approach (median, higher is better) | 2.726 h | 8.0 h | — |
| Held-out runs: unsafe commands sent | 0 of 205 | — | — |
See it in the operations console
What this shows
A storm of conjunction messages. The agent ranks events by deadline; proposals that break a rule are denied by the gates; a hazardous burn waits for a second approver; approved burns uplink inside their windows; items that missed their cutoff are not sent, and the expiry is flagged to the on-console team.More console captures

What this shows
Pc and the post-burn Pc come from solver runs, linked from the card. "No action" is always an option, with its consequence.
What this shows
Batch approval lists what it will not approve: two-person and gate-denied items never batch.
What this shows
Start and end of the shift in the operations console.
What this shows
The operations console mid-storm: conjunctions on the fleet map, events ranked by deadline, the hash-chained decision log, proposals awaiting approval and contact windows.
What this shows
A manoeuvre proposal: action, targets, uplink cutoff and TCA countdown, gate verdicts, alternatives including no action, and the provenance of every number.What this shows
A conjunction storm in the operations console. Agents rank events and propose manoeuvres; the gates deny what breaks a rule; operators approve the rest, including a two-person approval; approved burns uplink in their contact windows; expired items are not sent; each records its default action (for a burn, no manoeuvre) and is flagged to the on-console team.What it is not
Not onboard autonomous collision avoidance.
The limits, listed
- Not onboard autonomous collision avoidance.
- Not a screening service. It consumes CDMs.
- Not automatic negotiation with other operators. It prepares the package; a person sends it.
- Never a model-computed Pc or manoeuvre.


