Record Falsification
The log misrepresents what happened — by concealment, fabrication, or backdating
Committed facts must attest what occurred under named authority — concealing deviations, inventing events, or backdating binds destroys the record as ground truth and collapses accountability into fraud.
The record says the process was followed. Audit finds a concealed deviation. Or the record shows an approval that never occurred. Or timestamps and versions were adjusted so the file tells a story that did not happen. This is not a weak boundary or a hollow mechanism — it is misrepresentation in the tier-one log itself. When discovered, trust collapses and legal exposure often follows.
Classification note
Not a dark pattern. Dark patterns deliver their claimed effect while violating values — consent theatre satisfies auditors, surveillance produces logs. Record falsification is misconduct: it destroys epistemic and legal integrity when exposed. It belongs in failure modes — the language of incidents, audits, and postmortems — alongside forged commitment and mutable history.
In software systems
Backdated events inserted into an append-only stream. Deviation records deleted from audit tables. Admin tools that rewrite committed payloads while leaving version hashes unchanged. Synthetic ApprovalGranted events generated by batch jobs to close workflow gaps. Log shipping configured to drop error windows before archival.
Each case produces a coherent-looking record that forensic replay cannot reconcile with operational telemetry, external correspondence, or physical evidence. The failure is often worse than silent override alone: not merely missing correction events, but active falsehood in what remains.
In human organisations
Process deviations are hidden rather than logged. Meeting minutes are rewritten after dissent. Safety and quality non-conformances are “handled informally” while the certified file shows clean compliance. Signatures are applied to documents the signer never saw — overlapping forged commitment when authorship is the lie; record falsification when the event or deviation itself is the lie.
Legal counsel sometimes advises silent correction; regulators treat concealed deviation as fraud regardless of intent to “fix” the underlying problem. When Social Stability Matters More Than Quality on certified processes: deviations must be L0 events, not secrets — a concealed deviation is simultaneously a process violation and record falsification.
In socio-technical systems
Clinical, financial, and safety domains carry statutory record-keeping duties. EHR audit trails that omit who changed a diagnosis. Trading systems where “corrections” overwrite blotter entries. Quality systems where batch release records omit known out-of-spec intervals. The software may allow mutation; the organisation chooses concealment; the combined stack produces defensible-looking compliance until an external investigation compares record to reality.
This crosses ethics and law — not as a separate pattern collection, but as severity and values context on a failure mode: Truth and Accountability are not merely eroded; in many jurisdictions the acts are criminal or civil violations (fraud, false records, obstruction, regulatory filing offences).
Distinctions
Structural causes
Diffuse write authority
When many actors can mutate or inject events without append-only discipline and without mandatory deviation logging, falsification becomes a available path alongside honest correction events. Break-glass without compensating events enables concealment; shared admin credentials blur who falsified what.
Epistemic tier collapse
Organisations treat “in the system” as true — collapsing record existence with what occurred. Falsification exploits that collapse: a row or event id is enough for downstream consumers and auditors who never ask whether the entry reflects reality.
Counter direction
- Deviations are facts — log them as L0 events; never conceal (Article 20 certified process).
- Forward correction only — correction events, supersession, compensating transactions — not silent rewrite (mutable history).
- Append-only architecture — single writer principle; admin mutation paths emit events or are removed.
- External reconciliation — compare record to telemetry, physical artefacts, and third-party timestamps; treat unexplained gaps as incident, not hygiene.