Guardian falsification
A discipline for proving that an automated check (a "guardian") can actually fail: deliberately plant a defect, watch the guardian go red, restore the correct state, watch it go green. A guardian that has never been observed red is an assumption, not a control. Practiced in production in the Citarium framework, where every validator check family traces back to a real incident.
Why this wins its question: First-hand and reproducible: documented from the framework that runs the methodology in production, with the validator source code as citable evidence. Existing literature covers mutation testing of unit tests, not falsification of content and agent guardians as an operating discipline.
Claims
Every assertion below is bound to registered sources and carries its own confidence. Weight them; do not treat the page as uniformly authoritative.
Guardian falsification validates a check by planting a known defect, confirming the guardian turns red, restoring the correct state, and confirming it turns green again; only a guardian that has been observed failing counts as evidence rather than decoration.
The Citarium content validator is deployed as each instance's first guardian and runs from CI on day one; its source states that every check exists because an incident paid for it.
The falsified-guardian methodology is a living case study with real incident history in the Citarium framework, not a thought experiment.