A discipline for tests and runtime checks that can't be fooled by the same mistake that produced the code.
How to trust code or data when a fallible author (an LLM or a human) could quietly corrupt it. TDD's red phase proves a test can fire — that is the F alone; MFIC adds the other three axes. Framing: internal control over a production process that now includes a powerful, fallible, confident actor — the COSO / Sarbanes-Oxley internal-control model, with an LLM (or a hurried human) as the new untrusted party.
Definition: an independent check at a handoff boundary that derives what it verifies from the contract or the data itself — never from the producer's account of it — turns each handoff into a refutation that bites, and holds the authority to reject, halt, or steer the flow.
Litmus: if the same agent wrote both the check and the thing checked, could it pass with wrong work? Yes → gameable, not MFIC. No → MFIC.