stillholds EU digital compliance

Method

Deterministic by construction, cited without exception, versioned so an assessment can be replayed. Everything below is checked by the build rather than promised here.

One wizard, many instruments #

The questions ask about your solution, never about a regulation: nobody should need to know that screening job applicants is Annex III point 4 before being told so. There are 30 facts, in 6 sections.

Each pack declares which facts it reads, and a gate fails the build if a pack reads a fact the wizard never asks, or if the wizard asks a fact no pack reads. That gate found two real faults the first time it ran.

Back to top

How a finding is reached #

Each rule is a plain condition over the facts, inspectable and arguable. There is no model, no score and no ranking. The same answers always produce the same findings, which a gate verifies across 768 fact profiles on every build.

Findings are ordered by severity and then by date: prohibited practices first, because nothing else matters until they are resolved, then classification, then obligations, cautions and notes.

Back to top

What it refuses to do #

It does not advise. A finding states what a provision requires and when it binds. The judgement stays with you and your advisers.

It does not assert national law. A directive binds through each Member State's transposing instrument, so the NIS2 pack states the directive's requirements and raises a caution rather than pretending to know what any given country enacted, particularly while transposition remains uneven.

It does not present proposals as law. Amendments still in negotiation are carried as watch items marked proposed, and the integrity gate rejects any watch item not so marked.

Back to top

Versions and replay #

Every assessment records the ruleset it was made under. Every release snapshots the whole ruleset, checksummed, and the build refuses to alter one already published: a version is raised instead.

That is what makes replay honest. Given the same answers and a later ruleset, the engine reports what changed for that solution: which findings appeared, which disappeared, which dates moved. The AI Act moved four dates and added two prohibitions six days before enforcement began, and nothing told the people who had assessed their systems that spring.

Published rulesets: v0.1.0 · v0.2.0 · v0.2.1 · v0.3.0 · v0.4.0 · v0.5.0 · v0.6.0

Back to top

What the build checks #

GateWhat it refuses
IntegrityA rule without a provision, a date, a severity or a check record; a watch item not marked proposed
Facts coverageA pack reading an undeclared fact; a question no pack consumes
Engine casesSixteen worked examples, including the deferred dates and the derogation
Invariants768 fact profiles: every finding cited, dated and attributable; determinism
SnapshotAny edit to a ruleset already published
Replay parityA snapshot that no longer reproduces the live ruleset, rule for rule and condition for condition
DesignA colour outside the token module; contrast below AA in either theme; a page that is not responsive
SiteA third-party script; a wizard that does not reach an assessment; a configuration that gains server code

Back to top