MissionOps AI tracks how operational state changes across mission days — not just what one report says.
It preserves weak signals, decisions, risks, procedure gaps, and handover actions across mission documents.

◈ Demo Scenario: Weak Signal → Incident → Handover Risk

WARNING
Mission Status
HIGH
Risk Level
4
State Changes
4
Active Risks

State Changes Since Previous Sol

CO2 Scrubber Unit 1
NOMINAL TEST MODE
Sol: 2 Impact: Redundancy degraded; EVA operations restricted
CO2 Scrubber Unit 2
BACKUP PRIMARY
Sol: 2 Impact: Single-point-of-failure for life support
EVA-01 Schedule
Sol 3 AM Sol 3 PM
Sol: 2 Impact: Schedule pressure on subsequent EVAs

Critical Systems Status

CO2 Scrubber Unit 1
TEST
Running in test mode after restart
CO2 Scrubber Unit 2
NOMINAL
Primary operational
Power Systems
NOMINAL
Solar array and battery backup OK
Communications
NOMINAL
Daily uplink window maintained

Weak Signal Escalation

◈ Early Warning → Operational Incident
Sol 1 — Signal
Amber warning observed on CO2 Scrubber Unit 1 at 14:32
Sol 2 — Incident
Unit 1 fault shutdown during diagnostic at 09:12; Unit 2 became primary
How Related
The amber warning on Sol 1 was an early indicator of sensor contamination that ultimately caused the Unit 1 shutdown on Sol 2
Escalation Pattern
Warning indicator → monitoring decision → overnight persistence → diagnostic attempt → complete failure
Potential Cascade
If Unit 2 has similar contamination, mission loses all EVA capability and faces life support emergency

Handover Risks

⚠ Unit 2 sensor inspection not completed
Why it matters
If Unit 2 has similar contamination, mission loses all EVA capability and faces potential life support emergency
Required before next Sol
Complete Unit 2 sensor inspection and document findings
⚠ Unit 1 test period must reach 24-hour stable operation
Why it matters
Unit 1 cannot return to primary status until test is complete; premature return could cause another failure
Required before next Sol
Monitor Unit 1 test mode through Sol 3 morning; document any anomalies

Mission Timeline

Sol 1

14:32
OBSERVATION
Unit 1 status indicator changed from GREEN to AMBER
CO2 Scrubber Unit 1
21:00
DECISION
Decision to continue monitoring Unit 1 instead of immediate troubleshooting
CO2 Scrubber Unit 1

Sol 2

08:15
OBSERVATION
Morning check confirms Unit 1 still showing AMBER warning
08:30
DECISION
Commander decision to conduct deeper troubleshooting before EVA prep
09:12
INCIDENT
Unit 1 fault shutdown during airflow sensor check
Complete loss of Unit 1; Unit 2 activated as primary
09:15
OBSERVATION
CO2 levels briefly elevated to 0.8% (nominal is 0.5%)
10:00
DECISION
Commander declares EVA-01 delayed pending resolution
10:30
MAINTENANCE
Improvised compressed-air cleaning performed on Unit 1 airflow sensor
11:00
ACTION
Third restart attempt - SUCCESS, Unit 1 in TEST MODE

Risk Register

R-001
Single-scrubber operation
HIGH OPEN
Mission currently operating with only Unit 2 for atmospheric CO2 processing. If Unit 2 fails, all EVA capability is lost and crew safety is compromised.
Systems: CO2 Scrubber Unit 1, Unit 2, Life Support First seen: Sol 2
Mitigation: Complete Unit 2 sensor inspection immediately; expedite Unit 1 return to operational status
R-003
Potential Unit 2 contamination
HIGH OPEN
If dust contamination affected Unit 1, the same environmental conditions may be affecting Unit 2. Unit 2 has not been inspected for similar contamination.
Systems: CO2 Scrubber Unit 2
R-002
Unvalidated improvised procedure
MEDIUM WATCH
Compressed-air sensor cleaning was performed as improvised workaround. This procedure is not formally validated.
R-004
Schedule pressure cascade
MEDIUM WATCH
EVA-01 delay creates schedule pressure on subsequent EVAs. If Unit 1 does not return to operational status, further delays are likely.

Decisions & Consequences

D-001 · Sol 1
Continue monitoring Unit 1 amber warning rather than immediate troubleshooting
Rationale: Filter appeared clean, no visible contamination. Airflow felt normal. Amber warning may be transient or sensor-related.
Observed consequence: Unit 1 shutdown during diagnostic on Sol 2 at 09:12. The amber warning was an early indicator of sensor contamination that was not addressed.
Owner: Commander Chen
D-002 · Sol 2
Conduct deeper troubleshooting before EVA prep
Rationale: Amber warning persisted overnight, indicating the issue is not transient
Observed consequence: Troubleshooting triggered Unit 1 fault shutdown, but also identified root cause (sensor contamination)
Owner: Commander Chen
D-003 · Sol 2
Delay EVA-01 pending CO2 scrubber resolution
Rationale: Mission plan requires dual-scrubber redundancy for EVA operations
Owner: Commander Chen

Procedure Gaps

G-001
CO2 Scrubber Maintenance Procedure
HIGH
Gap: No procedure for airflow sensor inspection or cleaning
Consequence: Crew used improvised compressed-air cleaning method without formal validation
Suggested fix: Add sensor cleaning procedure with specified tools, technique, and verification steps
G-002
CO2 Scrubber Maintenance Procedure
HIGH
Gap: No escalation criteria for persistent amber warnings
Consequence: Decision to monitor on Sol 1 rather than troubleshoot allowed the issue to escalate
Suggested fix: Define clear escalation criteria: amber warning persisting >4 hours should trigger troubleshooting

Action Board

1
Inspect Unit 2 for sensor contamination
Critical to verify Unit 2 is not affected by same contamination
Owner: Flight Engineer Due: Sol 3
2
Document improvised sensor cleaning procedure
Need formal record so it can be validated and potentially reused
Owner: Flight Engineer Due: Sol 3
3
Request sensor cleaning validation from ground support
Improvised procedure needs expert review before reuse
Owner: Communications Officer Due: Sol 3