CSE Roadmap

Specialist tier · about 3 hours · 12 parts

Part 9 of 12 · 2 min read

Regulation basics: common mistakes

Common mistakes, and what the example does not do.

Mistakes that turn a compliance gate into theatre

  • Treating compliance as a final-week task.
  • Self-classifying risk without legal review.
  • Hard-coding dates from a blog post.
  • Assuming "no EU users" or "no AI law" means nothing applies (GDPR, sector and state rules).
  • Paperwork that does not match behaviour: a model card nobody maintains.
  • No drift checks after the system gains a new domain or tool.
  • Believing a passing gate means legal compliance.

What the example does not do

About this example What the example does not do
  • No legal analysis: tier rules, obligation lists and the "prohibited" set are simplified; real definitions have exceptions and conditions.
  • Evidence is a boolean, not a reviewed document.
  • Sources are secondary (blogs, checked on one day); omnibus details may differ from the Official Journal.
  • GDPR, US and sector rules appear only as notes; the code covers the AI Act-style tiers.
  • No conformity assessment, registration, incident reporting or contract analysis.
  • Optional real experiment: take one real system, have counsel classify it, and compare their obligation list with the one required() generates; fix the gap in the code.

Check yourself

A new law sets a date for your obligations. Where should that date live?

Show answer

In configuration with a source and a read date, not in someone's memory. Annex III dates moved from 2 August 2026 to 2 December 2027 in the sources checked.

For the curious Engineering orientation, not legal advice

The example classifies 10 invented systems and 4 of 10 pass the gate; the failures name what is missing (disclosure, human oversight, two-person sign-off, a prohibited practice). The tiers and obligations are the simplification. Source: secondary law-firm summaries, checked 31 October 2026 (not the Official Journal); counsel decides the real classification.

What you will use daily at work

Practice What it looks like
Classify each system early And re-run when its domain, features or evidence change.
Keep an evidence manifest Model card, risk assessment, eval report, logs, oversight design, retention policy.
Put the checks in CI A gate that fails closed on missing evidence.
Date-stamp every legal claim Source, read date and who confirmed it.