AI Platform and Security · Module 1 · Foundations

Regulatory Requirements as Engineering Constraints

The lesson shows how to read European regulation as an engineer. Each obligation is followed from its instrument and article to the shared platform capability that satisfies it, the codified artefact that configures it and the evidence it produces. Participants apply the three keys that decide which requirements apply, work with the requirements-to-capability matrix and the platform requirements catalogue, and run two systems of the fictional organisations through it. All content is architectural implication, not legal advice.

Lesson 3 of 25Chapter 390 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Platform and Security / Module 1 / Chapter 3

Learning objectives

After the lesson the participant can:

Key concepts

The four-link chain
Every requirement is written as legal source, platform capability, codified artefact and evidence produced. A requirement that cannot be written as all four links is not ready to be built; the missing link is usually the evidence.
Three keys
The result of risk classification reaches the platform as data in three keys: the risk tier, the role under Article 3 of the AI Act, and whether the system integrates a general-purpose AI model.
Article 25 trigger
The clause the chapter says platform teams most often miss: a deployer that makes a significant change to a high-risk AI system, or repurposes a system into a high-risk use, inherits the provider's obligations.
Platform requirements catalogue
One artefact the pipeline reads: each entry names an article, its control, the condition under which it applies and the gate that blocks a release when the evidence is missing. A full catalogue runs to some sixty entries.
Incident pipeline
The capability for Article 73 of the AI Act: it classifies each AI-related incident against every regime that may apply at once, starts the right clocks and assembles the report from logs and the evidence store.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Match

From article to platform capability

Match each provision of the AI Act with the shared platform capability the chapter's matrix assigns to it.

Interactive exercise 2 · Scenario

Logs in the supplier's environment

Apply the chapter's reading of Article 26 to a procurement at a public authority like Nordvik Region.

Teaching plan

10 minThe teacher reads Article 12 of the AI Act as an engineer would: an append-only event store with a retention policy, a schema that identifies the system version and an access path for readers.
25 minWork through the three keys and Table 3.1, pausing on Articles 9 to 15 as shared capabilities, the deployer duties of Article 26 and the transparency duties of Article 50.
15 minCover the general layer beneath: the Cyber Resilience Act, NIS 2, DORA and the GDPR as constraints on the same pipelines, and the catalogue excerpt.
30 minExercise: groups derive the requirements of one system and write catalogue entries; two groups present and the room tests each entry for a missing link.
10 minCompare the two worked examples: for Nordvik Region the leverage is the contract, for Hansa Mutual the platform and its market overlay.

Discussion

  1. Which obligation in your organisation is met today by a project-built substitute instead of a shared platform capability, and what does that cost?
  2. Hansa Mutual applied the Article 12 logging profile and the Article 14 oversight binding to an agent that its classification record places outside the high-risk tier. When should policy go beyond what the law requires?
  3. For which of your requirements is the evidence link the one that is missing, and who would have to produce that evidence by hand today?

Written exercise

Exercise · 30 minutes

Derive the platform requirements for a new system

Take Nordvik Region's benefits-triage system, or a planned system of your own. Follow the practical guide: write the intended purpose in two or three sentences, record the risk tier and the AI Act role and test the Article 25 triggers, then set the flags for general-purpose model use, personal data, decisions about individuals, sector and markets. Write five catalogue entries, each with source, the condition under which it applies, the control, the evidence and the gate. For every entry say whether the capability exists on your platform or is a gap, and set the retention period with the reasoning the guide gives.

Deliverable: A requirements profile with five catalogue entries written as four-link chains, plus a gap list with an owner and a date for each gap.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. When a requirement cannot be written as all four links of the chain, which link does the chapter say is usually missing?

    Show the answer

    C. The evidence produced
    The chapter states that a requirement lacking one of the four links is not ready to be built, and that the missing link is usually the evidence.

  2. Article 26 of the AI Act requires deployers of high-risk AI systems to keep the logs under their control. What architectural consequence does the chapter draw?

    Show the answer

    B. The contract should require the logs to land on the deployer's platform, since logs kept only by the supplier cannot be retained
    If a procured system writes logs only to the supplier's environment the deployer cannot retain them, so the phrase matters architecturally and belongs in the contract.

  3. Why did Hansa Mutual add the Article 12 logging profile and the Article 14 oversight binding to its claims-triage agent?

    Show the answer

    A. As group policy: an agent with write access to production needs action-level logs and a stop control whatever its legal tier
    The agent's classification record places it outside the high-risk tier; the group added the two controls as policy beyond what the law requires.