In EAB, a screening result cannot be edited after approval. Re-screening creates a new version. The history of every AI system — every classification, every legal source, every supervisor — is reconstructable at any point in time.
This is not a feature. It is the design principle that makes every other compliance record defensible.
“A record that can be edited is not a record. It is a current view — and current views do not survive the question: ‘what did it say on the date of the decision?’”
When a supervisor approves a screening result in EAB, the record is sealed. The risk classification, the applicable articles, the obligation derivation, the legal source version, the supervisor identity, and the UTC timestamp are locked into an immutable record. No actor — including system administrators — can modify an approved screening record. Changes require initiating a new screening session, which creates a new version.
Legal source anchoring means that each screening record carries a snapshot of the regulation version that was in force at the time of the determination. When CELEX 32024R1689 is updated and a system is re-screened, the new record references the updated version — while the previous record continues to reference the version under which it was originally classified. An auditor can verify the compliance state at any historical point without ambiguity about which version of the law applied.
The screening history of an AI system is the backbone of its audit trail. Every version — original classification, re-screening after a legal change, re-screening after a system modification — is preserved in sequence. The history only grows. Nothing is overwritten. Nothing is deleted. The reconstruction of any historical compliance state is always possible from the record as it exists today.
These are not policies. They are the structural properties of how EAB stores every screening result.
Approved screening records cannot be edited by any actor. A supervisor who made an error must initiate a new screening session. The incorrect record remains in the history — and the correction is visible as a new version, not as a modification of the old one.
Every screening record carries the CELEX 32024R1689 version that was in force when the supervisor approved the result. The obligation derivation is verifiable against that version — not against the current version of the regulation.
Every AI system has a screening history: the original classification, all re-screenings with their triggers (legal change, system modification, voluntary review), and the complete record of every version including the ones that were superseded. An auditor can reconstruct the compliance state at any date from the history alone.
When re-screening produces a different classification result, the new result is a new version — not a correction of the old one. The original record remains. An auditor can see not just what the current classification is, but what it was before the change and why it changed.
Where a re-screening produces a different obligation set, EAB shows the difference between versions — which obligations were added, which were removed, and what changed in the legal source. The diff is part of the re-screening record.
PDF export can be generated for any version of the screening record — not just the current one. An auditor export reflects the frozen state at the chosen version and reference date. Nothing is recalculated or reinterpreted.
Immutable, versioned, legally anchored — the screening record is the foundation of every audit-ready compliance position in EAB.
EU-hosted · Anchored to CELEX 32024R1689
Tell us about your organization and what you’re looking to address. We’ll follow up with the relevant information.
