An overview of regulation is worth only as much as its upkeep. Every change to the rule set is therefore recorded here, with a version number, a date, the regime affected and, where a change in the law is involved, the source. The same entries sit in machine-readable form in the data file, from which CHANGELOG.md is generated.
Versions
Loading the change log
Planned
What is not yet covered and is on the list:
- loading
How the rule set is maintained
Thresholds and dates do not sit in the source code of the page but in a versioned data file. A change always runs through the same five steps:
- The source is checked and recorded with its date.
- The value is changed in the data file, not in the page code.
- The test suite runs; it checks every threshold at its boundary and the five example profiles against their expected outcome.
- The entry goes into the change log, with its type, the regime and the source.
- The version number rises: the last digit for wording, the middle one for new fields, the first for a change that moves existing results.
A change in the law is therefore a dated entry with evidence rather than a silent correction. Anyone holding an older result can tell from the version number which state of the rule set it was calculated against. That number appears on every record.
Review cycles
Not every regime moves at the same speed. The four currently being rewritten, that is the AI Act, the Deforestation Regulation, the CSRD and the CSDDD, are checked against their source monthly. The NIS2 Implementation Act and the Supply Chain Act are checked quarterly, the three stable ones twice a year. Which cycle applies to which source, and when it was last checked, is set out in the source list.
Legal position as of 12 October 2026To the method