learning-it by example

#97 AI security and governance 5.4 min

EU AI Act for Developers: A Practical Tier Checklist

Before you read the EU AI Act, one question decides most of it: which tier is your app in?

1. Which four levels of risk does the European Commission describe for AI systems?
2. Six made-up apps were put into tiers with four yes or no questions. How many landed in each tier?
3. Why can four yes or no questions not decide a real case under the EU AI Act?
4. In the simplified Python tier rules of the EU AI Act checklist, which test comes first, and what follows for an app marked as banned?
5. On what date did the prohibitions and the AI literacy duty start to apply, according to the European Commission AI Act page (as it stood in November 2026)?

Practice only: nothing is saved and no score counts towards anything. Each answer comes with the reason.

  1. Make the spam filter produce content

    Copy the code folder first. In apps.py change makes_content to True for the spam filter and run compare.py. Predict which tier the spam filter moves to and which duty it gets. You should see it become limited with the duty to mark generated content as AI-made, and the totals become 2 high risk, 3 limited and 1 prohibited, with no minimal app left. Change makes_content back to False afterwards.

    A hint

    Look at the last two tests in the tier function in tiers.py.

  2. Remove the high risk area

    In apps.py change high_risk_area from 'employment' to None for the CV screener and run compare.py. Predict its tier and the totals. You should see the CV screener become minimal, and the totals become 2 minimal, 2 limited, 1 prohibited and 1 high risk (this assumes the spam filter is back to its original setting). Change high_risk_area back to 'employment' afterwards.

    A hint

    The high risk test only looks at whether high_risk_area is filled in.

  3. Add a seventh app that only talks

    Add a new app to APPS in apps.py that does not make content, is not banned and has no high risk area, but does talk to people. Give it any name. Run compare.py. You should see the app limited, with the duty to tell people they are talking to an AI as its only duty. Remove the new app again afterwards.

    A hint

    Use banned=False, high_risk_area=None, talks_to_people=True and makes_content=False.

  4. Ban a high risk app

    With apps.py back to the original, set banned to True for the CV screener, which is also in the employment area. Predict its tier before you run compare.py. You should see the CV screener become prohibited, and the totals become 2 prohibited, 2 limited, 1 minimal and 1 high risk. Then explain why, using the order of the tests in tier().

    A hint

    The test that comes first wins.

These tasks are for you to try on your own machine. Nothing is checked or saved.

What this does not show

Not legal advice. Six made-up apps and four yes or no questions; the rules do not decode the Annex III list, the exceptions, or the difference between a provider and a deployer. Dates are as shown on the European Commission page in November 2026 and have already changed once; check the current text.

Up next in AI security and governance

More in AI security and governance

All AI security and governance videos

Related videos