The thermal engineers and program management disagree
Thermal protection engineersEngineer entry
0.78
Anomaly score on heat shield sensor data. Logged on day 4 at 09:00, before program review.
Program managementManager entry
0.64
Reviewed on day 4 at 15:00 and summarized as within expected range. Simulated override.
The red tick marks the 0.7 threshold. The Risk Monitor Agent independently scores the same sensor data at 0.78.
Chosen:
Added to the audit log as entry #6, along with which evidence panels were open. The escalation status and divergence flag stay as logged.
Options are illustrative. A real deployment would draw them from the engineers and the mission rules.
Supporting evidence
Everything behind the decision is one click away. The log records which panels were open when a choice is made.
Thermal protection engineersEngineer entry
0.78
Day 4, 09:00. Before program review.
Program managementManager entry
0.64
Day 4, 15:00. Summarized as within expected range.
Spacecraft telemetryRisk Monitor Agent
0.78
Day 4, 09:02. Telemanom score, computed independently.
- Engineer signal above thresholdYes
- Program summary at or below thresholdYes
- Organizational boundary crossed[x]
When both conditions are true, escalation is triggered regardless of what the program summary says. Which boundary the signal crossed depends on how the Artemis teams are organized.
Trend detection
Looks for a rising signal across earlier flights and ground tests, including readings that stayed below threshold.
Slope [x], p [x], last [N] flights
Resolution audit
Counts how often a similar anomaly was resolved as acceptable, and what happened afterward. Add findings from post-flight inspection reports here.
Accepted [n] of [N], follow-up [x]
Bracketed values are placeholders for real Artemis flight and test data.