The EU AI Act (Regulation 2024/1689) is one of the most complex pieces of technology legislation ever written. This report quantifies — from the source code and git history — exactly what it took to implement it inside Coach2Lead, and how that compares to every other module in the product.
Before a single line of code: the regulation itself. These are the structural facts of the legal text the module had to encode — underpinned by a Dutch / English glossary of AI-Act terminology, on a platform that runs in either language.
Each block is a part of the EU AI Act. Bigger blocks carry more legal weight — more obligations, multiplied by the size of the fine for getting them wrong. Green = built and enforced. Amber = built, enforced as guidance. Nothing is red: across all 113 articles, not one obligation is left unimplemented.
Process-Management is the backbone of Coach2Lead — the most-used module in the product. Here is AICMS beside it, measured the same way.
Every figure below is derived directly from the repository and independently verified (see §12). This is the data model and surface area of one module.
Each point is a database table. Each line is a foreign-key relationship between them. This is not a diagram we drew — it is extracted directly from the compiled entity model. Hover any node to trace its connections.
Coach2Lead has 21 modules built over a decade. Here is where AICMS sits — measured the same way for every module.
Measured by where the commits actually landed — not calendar span. Each bar is a module’s busiest 90 days, ever. AICMS packed 90% of its entire history into one such window.
The entities aren't arbitrary. Each functional group implements specific Articles and Annexes of the regulation. This is the work that has no equivalent in any other module: translating statute into a relational schema.
Some obligations are not just large — they are written to require human legal judgment. These resist being reduced to columns and rules at all, which is precisely what makes the work slow and exacting.
Volume is only half the story. These are the structural engineering problems that had to be solved — most of them unique to compliance software.
Compliance software that is merely "done" is worthless if it is wrong. A disproportionate share of the effort went into proving the implementation correct.
Reconstructed from git. Not estimates — the recorded history of the work.