The mapping
What this actually looks like
Article 12, in practice: open any certified release in Verdikt and you can see exactly what was known at the moment it shipped — every signal, every threshold, every value — frozen and unchangeable, even if your thresholds change later. Article 14, in practice: if a release ships despite failing signals, Verdikt requires a name, a role, and a reason before it certifies. That record cannot be edited, not even by an administrator. Article 73, in practice: Verdikt watches what happens after a release ships and links production incidents back to the specific release and the specific decision that shipped it — the starting point for any incident report.What this page is not
Verdikt covers parts of Article 12 and Article 14, and supports the evidence trail behind Article 73 reporting. It does not cover the full scope of any of these articles, and it does not cover risk management, technical documentation, data governance, or the other obligations under the Act. This page describes a mapping, not a compliance guarantee. Whether your specific system is in scope, and what your specific obligations are, is a legal question — talk to your own counsel.See how it works: request access or start with the product overview.