Pink — Feedback, Alerts, and Retraining

Pink blocks close the loop — anomaly alerts, drift detection, and the retraining signals that keep the twin honest as the machines evolve.

What pink means

Pink marks the feedback role: the signals that flow back to correct and improve the system rather than forward to control it. Pink carries anomaly alerts up to operators, drift indicators to the MLOps pipeline, and labeled events back to the retraining substrate at L0.

What lives in pink

• Sub-threshold anomaly alerts from the L3 detection ensembles — quench precursors on the breeder, plug instabilities on the burner.
• Model drift and confidence degradation signals from monitored surrogates.
• Human corrections and confirmations captured for reinforcement learning from feedback.
• The batch-retraining trigger path from live operation back to L0.

Feedback is not control

Pink is deliberately distinct from the forward control colors. A pink alert can raise an operator's attention or schedule a retraining job, but it never actuates hardware directly. This keeps the improvement loop — which is slow and statistical — cleanly separated from the safety loop, which is fast and deterministic.

Closing the learning loop

Pink is what makes the architecture adaptive. As the breeder moves from first-of-a-kind toward NOAK and BOAK units, live behavior diverges from pre-build simulation. Pink signals capture that divergence, drive retraining, and update the twin — so the intelligence tracks the real machine rather than the design assumptions it started from.

Pink's destination is the feedback and retraining loop and the offline substrate of L0 Foundation.