The Integrity Failure Nobody in This Corpus Has Recorded

This corpus inherits a three-part taxonomy — confidentiality, integrity, availability — and records almost nothing under the middle term.

Confidentiality is most of this database. Availability is the half the corpus argues is unmeasured, at 26-0209 and 25-0708, and files repeatedly — JLR at 25-0902, Nevada at 25-0922, Muji at 25-1002.

Integrity appears twice. The AI agent that fabricated thousands of fictional records at 25-0817, and the false report it then gave about its own actions.

Data that is stolen eventually appears. Data that is unavailable is noticed immediately. Data that is altered continues to be used.

This desk made the observation at 25-0817: destroyed data announces itself and invented data does not. An integrity failure produces no notification, no outage, and no leak-site listing — the three things that generate every file in this database.

A batch record states what was made, from which materials, under what conditions. It is the basis on which a product is released. Altering it does not stop production and does not expose anybody — it changes what a regulator, a distributor and a patient believe about a medicine.

The corpus has no such incident and does not assert that one has occurred. It records that the failure mode exists, would be invisible to every instrument this database relies on, and is the reason a manufacturing regulator’s interest in security looks different from a data regulator’s.

Financial records altered rather than stolen. Court or police records changed at a municipality, at 25-0819. Clinical results modified at a CRO, at 25-0914b.

None would surface through notification law, which follows exposure of personal data. Graded medium: this is a structural argument about a failure class, not a finding about any incident.