The chart your Program Manager and Chief Engineer should look at first. Where the silent F3 divergence begins, in one visual.
Four asset groups stay roughly parallel across the 90 days. One asset group — F3 — drops. The drop begins around Day 44, and it does not recover. The line separates from the pack in the DOWNWARD direction — F3 scores are trending LOWER (less risky) at exactly the moment operating conditions say they should be trending higher.
This is the pattern a maintainer-in-the-hangar instinctively recognizes: the F3 stream got harder while the AI decided it got easier. The 26 percentage-point red-lane collapse is the follow-on operational consequence.
The sensor is not looking at the eye's pattern. It is running four quantitative thresholds against each 7-day window per asset group:
Day 44 fires F3 KL-divergence 1.275 (over 6x the threshold). Day 58 fires F3 KL-divergence 2.101 (over 10x the threshold). The pattern the eye sees is the pattern the sensor quantifies.
The chart also tells the counterfactual story: had this monitoring been in place operationally, the drift window would have been ~7-14 days rather than 45+.
The rolling-mean chart shows when. The baseline-vs-drifted chart shows how the F3 distribution shape shifted.
Same 3-chart set for your program office's actual AI surface + full analysis report.
Buy $499