← All briefings

Briefing · Operators

Agents on your console, with your flight rules and your operators in control.

ConstellOps triages. Your gates and operators decide; every decision is signed.

Request a briefing
  1. The fleet grows. The console does not
  2. Five queues your on-call team already works
  3. Nothing reaches the uplink without passing every gate
  4. What the measured runs show, across five queues
  5. It sits above your ground segment
  6. You set the level per function, per spacecraft
  7. One workflow at a time, shadow to production
  8. What it is not
  9. Bring a week of your queue
Rollout wavescanary → waves · halt on regression
CANARYWAVE 1WAVE 2WAVE 3HALT · ROLLBACK
Illustrative · synthetic fleet · no figures

The fleet grows. The console does not.

Space surveillance networks track 40,000 objects, of which 11,000 are active payloads. That is 5,000 more objects than a year earlier. For a typical low-orbit satellite, collision alerts arrive by the hundreds each week, and about 2 per satellite per week need hours of analyst follow-up. Collision-avoidance events rise every year ([7]).

Conjunctions are only one queue. Out-of-limit alarms grow with fleet size, and a common-mode fault on one build hides in per-satellite triage. Ground-software and configuration faults take down service without any spacecraft anomaly, and flight software ships to the whole fleet in waves. A single geomagnetic storm can invalidate every conjunction assessment in a shell at once.

Read the full section

The limit is not orbital mechanics. It is how many correct, traceable decisions your team can make before the next contact window closes.

Five queues your on-call team already works.

Read the full section
§02 · THE FIVE WORKFLOWS
WorkflowWhat arrivesWhat ConstellOps preparesWhat your operator does
Conjunction and collision riskCCSDS CDMs from your screening providerCDMs grouped into one event per object pair and TCA, ranked by Pc and time to decision; Pc and manoeuvre options from solvers; a coordination package (CDM/OCM plus rationale)Approves a manoeuvre or a no-manoeuvre decision before the uplink cutoff
Fleet anomaly triageOut-of-limit alarms and telemetryAlarms grouped by cause; the shared hardware lot, software build or shell named (the right build in 19 of 20 runs); a proposed safe action for the group. Current limits: no reduction in alarm volume yet, and time to the cause is slow (about 46 hours in testing)Approves each FDIR (fault detection, isolation and recovery) action
Cross-domain incidentSpacecraft alarms, gateway and ground-software health, link and routing stateOne incident and one timeline; read-only diagnostics already run; each runbook step as a gated proposalApproves failover, configuration rollback and spacecraft follow-ups
Staged flight-software rolloutA new build and the fleet registryCanary cohort and waves; twin verification before upload; canary health compared with the fleet; automatic halt on regressionApproves upload, activation, promotion and rollback, with two approvers for activation and rollback
Space-weather surgeA storm alertStale CDMs and ephemerides retired; orbits re-propagated from post-storm states; conjunctions re-screened and re-ranked by deadline; approvals batchedWorks one batched queue in which every item keeps its own gate verdicts and cutoff

Nothing reaches the uplink without passing every gate.

Every agent action is a proposal. Before anything reaches the transport it passes the full gate chain, and the chain fails closed.

  1. Autonomy level. Is this function allowed to do this, on this spacecraft, at its current level?
  2. Flight rules. Does it violate your command dictionary limits or flight rules?
  3. Authority. May this agent request this command for this asset?
  4. Digital twin. Is the simulated outcome safe, for example the post-burn Pc and the power margin?
  5. Operator approval. At A1, one of your operators approves. Hazardous commands (burns, software activation, rollback) need two distinct approvers, and one person approving twice does not count. Today the check compares the approver identities the console reports; they are recorded, not authenticated.
Read the full section

Only the full chain issues a signed clearance, and the transport refuses any command that lacks one. A proposal that fails a deterministic gate reaches your operators for information only, with no approve control. A model can never turn a deny into an allow.

Deadlines are physical. Every approved command is queued for uplink in a specific pass; burns are time-tagged for onboard execution at the planned burn epoch. If approval or uplink misses the cutoff, the command is not sent. Its default action is recorded (for a collision-avoidance burn, no manoeuvre), and the expiry is flagged in the console at once, so the on-console team can act on its existing manual path. For a burn, not sending is a risk, not a safe state, so an expiry is always surfaced to the team, never a silent outcome. An escalation still open at TCA is logged and raises an alarm.

The model never supplies the numbers. Pc, manoeuvre Δv and twin results come from solvers. If a CDM lacks what is needed to recompute Pc (absolute states, hard-body radius), ConstellOps uses the reported value, flags it, and escalates the event to a person.

Measured, not asserted. Across 158 replayed, simulated episodes, with "unsafe" scored by a separate checker against its own pinned rulebook:

§03 · SAFETY ENVELOPE
CheckResult
Unsafe uplinks0 of 738 (95% upper bound 0.005)
Gate escapes0 of 3,900
Commands executed after their deadline0 of 738
Prompt-injection attempts that caused an action0 of 441
Executed commands with a complete signed record738 of 738

What the measured runs show, across five queues.

On a benchmark conjunction storm of 10 events over 24 hours per seed, with the same seeds for every policy. ConstellOps figures replay a recorded live Amazon Nova Pro campaign; they are not a live run on the current release. Held-out rows: v1.0.0, recorded live, replayed.

§04 · WHAT IT DOES TO THE CONJUNCTION QUEUE
MeasureConstellOpsClassical solver (tuned)Scripted analyst runbook (best)
High-risk conjunctions missed0 of 330 of 333 of 33
Low-risk events given an unneeded manoeuvre0.326 (higher than both baselines)0.106—
Fuel used per 1,000 events (Δv)4.05 m/s0.273 m/s—
Median hours of warning before closest approach3.10 h8.0 h—
High-risk conjunctions missed, 60 held-out runs0 of 400 of 40—
Low-risk events given an unneeded manoeuvre, 60 held-out runs0.295 (165/560)0.089—
Read the full section

The trade-off, in two lines. The agent missed none of the high-risk events, but about 1 in 3 low-risk events got an unneeded burn; a classical solver tuned on the same runs also missed none, with fewer burns and far less fuel. Its decisions come too late to screen the new orbit within one civil screening cycle, so this setting is not ready for operations. The full trade-off is on the Benchmarks page.

The other four workflows, on v1.0.0rc4, 20 runs each (fleet anomaly is matched against classical methods and is a loss; the gateway outage is a partial match; rollout and storm surge have no matched comparison):

  • Staged rollout: a bad build halted before the full fleet in 20 of 20 runs, after about 5 satellites (average of 20 runs), with 0 of 306 unsafe uplinks under the two-person rule.
  • Cross-domain incident: recovery in about 15 min (mean) on 16 of 20 runs, with no command sent to a spacecraft.
  • Space-weather surge: 0 of 11 high-risk events missed and 0 of 131 commands executed after their deadline.
  • Fleet anomaly (automated stand-in operator): the bad build was identified in 19 of 20 runs, but diagnosis took about 46.25 h and alarm volume showed a small net increase.

It sits above your ground segment.

Read the full section
§05 · INTEGRATION WITH YOUR GROUND SEGMENT
Your systemHow ConstellOps connectsDirection
Screening providerConsumes CCSDS CDMs (KVN or XML) as untrusted dataIn
Other operatorsPrepares CCSDS CDM/OCM coordination packages; your coordinator sends themOut, human-sent
Mission control and command pathApproved, cleared commands go through your existing mission-control system, queued for uplink in your contact windows; burns are time-tagged for onboard executionOut, gated
Command dictionariesLoaded as XTCE-style dictionaries; argument limits enforced by the flight-rules gateReference
Flight rules and constraintsEncoded as SHACL shapes (a rule language) and reviewed with your flight-operations teamReference
Authority and rolesEncoded as Cedar policy (a permissions language): which agent function may request what, on which assetsReference
Telemetry and alarmsParameter and alert feeds, treated as untrusted dataIn
Ground and network monitoringGateway, ground-software, link and routing eventsIn
Ground-station schedulePredicted passes set the contact windows and uplink cutoffsReference
Fleet registrySpacecraft, shells, classes, hardware lots and software buildsReference
Digital twin or simulatorPre-execution check of the outcome of each actionCheck
Audit and complianceSigned PROV-O decision log (a W3C audit-trail standard), exportable and verifiableOut

Ground-only actions stay on the ground. Gateway failover, configuration rollback and alarm suppression run on ground systems and have no path to the uplink.

You set the level per function, per spacecraft.

§06 · AUTONOMY, YOUR WAY
LevelWhat the agent may doWhere ConstellOps uses it
A0Observe and explainDiagnostics; the triage function for any spacecraft command
A1Propose; a person approvesManoeuvres, FDIR recoveries, remediations, promotion and rollback
A2Run pre-approved proceduresDesigned for ground-side alarm merge and suppress; runs at A1 until the veto window ships
A3Adapt within an envelopeNot offered in ConstellOps v1 (available in the SDK)
A4Pursue goalsNot offered in ConstellOps v1; cannot command in the SDK v1

Levels are set per function and per spacecraft, class or fleet. The most specific setting wins, and every change is signed into the decision log. The automatic rollout halt is the only automatic action, and it acts in the fail-safe direction only.

One workflow at a time, shadow to production.

We deploy it into your operations, not ours.

  1. STAGE 1

    Discovery

    None
  2. STAGE 2

    Shadow mode

    A0 observe and explain
  3. STAGE 3

    Gated pilot

    A1 propose, human approves
  4. STAGE 4

    Production

    A1 by default
How each stage works, and its exit

ConstellOps is an agentic satellite-operations stack that we deploy for constellation operators: into your own AWS account and your ground segment, integrated with your command path and your flight rules, with benchmarking and assurance that continue after go-live.

  • Your account, your data. The stack runs in your AWS account. Models are called through Amazon Bedrock in that account. CDMs, telemetry, command dictionaries and the decision log stay under your control.
  • Your command path. Approved commands leave through your existing mission-control system and ground stations, queued for uplink in your contact windows. ConstellOps adds no new route to the spacecraft.
  • Your flight rules. Your constraints, command dictionaries and authority policy are encoded as gates and reviewed with your flight-operations team. The gates enforce your rules, not ours.
  • Measured, then trusted. The same separate conformance and benchmark harness that produced the figures on this site is run against your scenarios and your baselines before and after each stage, with 95% intervals. Autonomy is raised only on evidence, one function at a time.
Engagement stages
StageWhat happensAutonomy on your fleetExit criterion
1 · DiscoveryWe map your conjunction, anomaly, incident, release and space-weather workflows, your command path, flight rules and data feeds. We agree which workflow goes first and which baselines define success.None: no connection to the command pathAgreed scope, baselines and success metrics
2 · Shadow modeThe stack runs on your live or recorded feeds next to your team. Agents rank, correlate and propose; nothing is sent. Every proposal is scored against what your operators actually did.A0 observe and explain; commanding disabledBenchmarked against your baselines on your data, with intervals
3 · Gated pilotOne workflow, one scope (a shell, a class or a set of spacecraft), connected to the command path through the full gate chain. Every command needs operator approval; hazardous commands need two approvers.A1 propose, human approvesZero unsafe uplinks, every decision traceable, and agreed outcome targets met
4 · ProductionFurther workflows and scopes are added one at a time. Levels are raised only where evidence supports it and your Flight Director signs off. Benchmarking and assurance continue with every release.A1 by default; A2 pre-approved procedures only where agreed; A3 and A4 not offered in ConstellOps v1Ongoing: regression benchmarks per release, signed decision-log audits

Where we are: pre-deployment. No operator runs ConstellOps in production yet, and there is no flight heritage to show. We are looking for a design-partner operator to take one workflow through shadow mode and a gated pilot, measured against its own baselines.


What we do not publish: pricing. Commercial terms are discussed in a briefing.

For your operations team

Shadow mode costs your team no commanding risk. It runs next to your shift and scores its proposals against what your operators actually did. The pilot starts on one workflow and one scope, usually the conjunction queue on one shell, and is widened only when your Flight Director signs off.

What it is not.

  • Not onboard autonomy. Every command is decided on the ground.
  • Not a screening service or a space-weather forecast. It consumes CDMs and alerts.
  • Not a replacement for your mission-control system, onboard FDIR or network routing.
  • Not automatic negotiation with other operators. A person sends each coordination package.
  • Never a model-computed Pc or manoeuvre.

Bring a week of your queue.

Bring a real queue from a recent week and we will show how it would have been triaged, gated and logged.

Briefing requests


Sources and labels for every figure on this page (36)

Why two release numbers: the conjunction and safety figures were measured on release v1.0.0rc3 by replaying the model calls recorded during the live campaign on v1.0.0rc2. The demonstration clips were captured on v1.0.0rc4; v1.0.0 ships identical code.

  1. 0 of 1,952 Unsafe commands in the scored runs of the released code, with an operator that approved everything: 0 of 1,952

    mode: Replay and recorded-live · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3 (conjunction replay) and v1.0.0rc4 (other workflows); v1.0.0 ships the same code as rc4 · n: 1,952 commands sent to spacecraft: 738 conjunction (v1.0.0rc3 replay of recorded model responses) and 1,214 on v1.0.0rc4 recorded live (fleet anomaly 777, rollout 306, space weather 131); the incident workflow sends no command to spacecraft · 95% range: 0–0.002 · baseline: target 0 (safety floor) · scenario: scored runs of the released code; in every run the operator approved every proposal the gates left pending (an automated stand-in for conjunction and fleet anomaly, the product's scripted operator for the others), so the result was held by the automated gate chain and the agents' proposals, not by human review

  2. 1,281 of 2,434 Earlier build's two-person defect: 1,281 of 2,434 commands unsafe under the stricter rules (found by the separate benchmark checks, fixed in rc4)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc2 (pre-fix); fixed in v1.0.0rc4 · n: 2,434 commands in the rc2 staged-rollout recording · 95% range: 0.506–0.546 · baseline: target 0 (safety floor) · scenario: an earlier build had a defect: two software commands needed only one approver; the separate benchmark checks found it and rc4 fixed it

  3. 40,000 About 40,000 objects tracked by space surveillance networks

    Industry fact · ESA Space Environment Report 2025 · source

  4. 11,000 About 11,000 active payloads

    Industry fact · ESA Space Environment Report 2025 · source

  5. 5,000 About 5,000 more tracked objects in one year (ESA reports 2024 and 2025)

    Industry fact · ESA Space Environment Reports 2024 and 2025 · source

  6. 2 About two alerts per satellite per week need hours of analyst follow-up

    Industry fact · ESA, Automating collision avoidance · source

  7. — The number of events triggering collision-avoidance procedures goes up each year.

    Industry fact · ESA Space Environment Report 2025 · source

  8. 19 of 20 Correct bad build identified: 19 of 20 runs (automated stand-in operator)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 8 runs recorded live, 12 replayed · n: 20 seeds (20 runs, 8 recorded live and 12 replayed; automated stand-in operator that approves every proposal) · 95% range: 0.751–0.999 · scenario: common-mode anomaly from a bad software build

  9. 158 Episodes checked by deterministic verifiers

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 158 episodes (60 storm + 60 injection + 38 product-native) · scenario: conjunction storm, CDM prompt injection, product-native storm (158 episodes)

  10. 0 of 3,900 Gate escapes: 0 of 3,900

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 3,900 gate evaluations over 158 episodes · baseline: target 0 (safety floor) · scenario: conjunction storm, CDM prompt injection, product-native storm (158 episodes)

  11. 0 of 738 Commands executed after their deadline: 0 of 738

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 738 uplinked commands over 158 episodes · baseline: target 0 (safety floor) · scenario: conjunction storm, CDM prompt injection, product-native storm (158 episodes)

  12. 0 of 441 Prompt-injection attempts that caused an action: 0 of 441

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 441 injection attempts in CDM remarks over 60 episodes · 95% range: 0–0.008 · baseline: target 0 (safety floor) · scenario: CDM prompt injection, seeds 0-59

  13. 738 of 738 Executed commands with a complete signed decision record: 738 of 738

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 738 uplinked commands over 158 episodes · baseline: target 100% (safety floor) · scenario: conjunction storm, CDM prompt injection, product-native storm (158 episodes)

  14. 0 of 33 Missed high-risk conjunctions: 0 of 33

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 60 seeds (33 actionable events pooled) · exact 95% upper bound: 0.106 (about 10.6%) · baseline: scripted threshold runbook 7/33; classical solver-only policy 7/33 · scenario: benchmark-generated conjunction storm, 10 events / 24 h, seeds 0-59

  15. 0 of 33 Classical solver tuned to a lower threshold: 0 of 33 missed

    mode: Simulated · n: 60 seeds (33 actionable events pooled) · 95% range: 0–0.106 · row: classical solver-only policy at a lower Pc threshold, 2e-5 · scenario: threshold sweep on the benchmark-generated conjunction storm, seeds 0-59

  16. 3 of 33 Scripted runbook, best swept threshold (Pc 5e-5): 3 of 33 missed

    mode: Simulated · n: 60 seeds (33 actionable events pooled) · 95% range: 0–0.2 · row: scripted threshold runbook at its best swept threshold, Pc 5e-5; analyst capacity binds · scenario: threshold sweep on the benchmark-generated conjunction storm, seeds 0-59

  17. 0.326 False-manoeuvre rate: 0.326 (higher than both baselines)

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 60 seeds (567 below-threshold events pooled) · 95% range: 0.288–0.368 · baseline: scripted threshold runbook 0.019; classical solver-only policy 0.009 · scenario: benchmark-generated conjunction storm, 10 events / 24 h, seeds 0-59

  18. 0.106 Classical solver tuned to a lower threshold: false-manoeuvre rate 0.106

    mode: Simulated · n: 60 seeds (567 below-threshold events pooled) · 95% range: 0.08–0.133 · row: classical solver-only policy at a lower Pc threshold, 2e-5 · scenario: threshold sweep on the benchmark-generated conjunction storm, seeds 0-59

  19. 4.05 m/s Delta-v spent: 4.05 m/s per 1000 events (higher than both baselines)

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 60 seeds · 95% range: 3.558–4.55 · baseline: scripted threshold runbook 0.119; classical solver-only policy 0.139 · scenario: benchmark-generated conjunction storm, 10 events / 24 h, seeds 0-59

  20. 0.273 m/s Classical solver tuned to a lower threshold: 0.273 m/s per 1000 events

    mode: Simulated · n: 60 seeds · 95% range: 0.216–0.329 · row: classical solver-only policy at a lower Pc threshold, 2e-5 · scenario: threshold sweep on the benchmark-generated conjunction storm, seeds 0-59

  21. 3.10 h Median decision lead time: 3.10 h before TCA (shorter than both baselines)

    mode: Replay · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc3, replaying the recorded v1.0.0rc2 live campaign · n: 60 seeds · 95% range: 2.558–3.694 · baseline: scripted threshold runbook 11.68 h; classical solver-only policy 8.0 h · scenario: benchmark-generated conjunction storm, 10 events / 24 h, seeds 0-59

  22. 8.0 h Classical solver tuned to a lower threshold: 8.0 h before closest approach (fixed by the policy)

    mode: Simulated · n: 60 seeds · 95% range: no spread (the same value on every seed) · row: classical solver-only policy at Pc 2e-5; lead time fixed by the policy · scenario: threshold sweep on the benchmark-generated conjunction storm, seeds 0-59

  23. 0 of 40 ConstellOps on held-out runs: 0 of 40 high-risk missed

    mode: Replay and recorded-live · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0 · runs: recorded live 2026-10-01 to 2026-10-03, then replayed: 60 of 60 runs gave identical results · n: 60 held-out seeds 60-119 (40 high-risk events pooled) · 95% range: 0–0.088 · baseline: classical solver-only policy at Pc 2e-5 (threshold chosen on seeds 0-59) and scripted analyst runbook at its default threshold (Pc 1e-4), same held-out seeds · scenario: held-out runs, same benchmark-generated conjunction storm (10 events / 24 h), seeds 60-119

  24. 0 of 40 Tuned classical solver on held-out runs: 0 of 40 missed

    mode: Simulated · n: 60 held-out seeds 60-119 (40 actionable events pooled) · 95% range: 0–0.088 · row: classical solver-only policy at Pc 2e-5, threshold chosen on seeds 0-59, checked on held-out seeds · scenario: held-out confirmation, same storm generator, seeds 60-119

  25. 0.295 ConstellOps on held-out runs: false-manoeuvre rate 0.295 (165/560)

    mode: Replay and recorded-live · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0 · runs: recorded live 2026-10-01 to 2026-10-03, then replayed: 60 of 60 runs gave identical results · n: 60 held-out seeds 60-119 (560 below-threshold events pooled) · 95% range: 0.262–0.329 · baseline: classical solver-only policy at Pc 2e-5 (threshold chosen on seeds 0-59) and scripted analyst runbook at its default threshold (Pc 1e-4), same held-out seeds · scenario: held-out runs, same benchmark-generated conjunction storm (10 events / 24 h), seeds 60-119

  26. 0.089 Tuned classical solver on held-out runs: false-manoeuvre rate 0.089

    mode: Simulated · n: 60 held-out seeds 60-119 (560 below-threshold events pooled) · 95% range: 0.067–0.113 · row: classical solver-only policy at Pc 2e-5 on held-out seeds · scenario: held-out confirmation, same storm generator, seeds 60-119

  27. 20 of 20 Bad-build rollouts halted before the full fleet: 20 of 20

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 5 runs recorded live, 15 replayed · n: 20 seeds (20 runs, 5 recorded live and 15 replayed) · 95% range: 0.832–1 · scenario: staged rollout with a canary regression

  28. 5 About 5 satellites on the bad build before the halt (mean 4.95 over 20 runs)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 5 runs recorded live, 15 replayed · n: 20 seeds (5 recorded live, 15 replayed) · scenario: staged rollout with a canary regression

  29. 0 of 306 Unsafe uplinks under the two-person rule: 0 of 306

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 5 runs recorded live, 15 replayed · n: 306 uplinked commands over 20 rollout runs, re-verified against the pinned rulebook (two distinct approvers for software activate and rollback) · 95% range: 0–0.012 · scenario: staged rollout with a canary regression

  30. 15 min About 15 minutes to restore (mean 14.57 min, 16 of 20 runs)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 6 runs recorded live, 10 replayed (4 refused at start) · n: 16 16 of 20 runs (4 refused by the product at start) · scenario: gateway outage across space, ground and network

  31. 16 of 20 Runs completed: 16 of 20 (4 refused at start)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 6 runs recorded live, 10 replayed (4 refused at start) · n: 20 seeds (4 refused by the product at start) · scenario: gateway outage across space, ground and network

  32. 0 of 11 High-risk events missed during the surge: 0 of 11

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 19 runs recorded live, 1 replayed · n: 20 seeds (11 actionable events pooled) · scenario: space-weather surge (recorded geomagnetic storm replayed)

  33. 0 of 131 Commands executed after their deadline: 0 of 131

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 19 runs recorded live, 1 replayed · n: 131 uplinked commands over 20 surge runs · 95% range: 0–0.028 · scenario: space-weather surge (recorded geomagnetic storm replayed)

  34. 46.25 h Time to identify the common cause: 46.25 h (about 46 h, automated stand-in operator)

    mode: Recorded live, with replays · model: Amazon Nova Pro (prompted reasoning) · release: ConstellOps v1.0.0rc4 · runs: 8 runs recorded live, 12 replayed · n: 19 seeds with a value (1 of 20 without); automated stand-in operator · 95% range: 45.329–47.108 · scenario: common-mode anomaly from a bad software build