AI Platform and Security · Module 1 · Foundations

AI Decision Records, Model Cards and the Architecture Repository

The lesson extends the Architecture Decision Record to AI systems. Participants learn the fields the AI Decision Record adds, follow four worked records of Nordvik Region and Hansa Mutual from proposal to supersession, and see how model cards, datasheets and the system card accompany the record in an architecture repository from which the technical documentation of Article 11 and Annex IV of the AI Act is generated instead of written by hand.

Lesson 5 of 25Chapter 590 minutes

Read the chapterThe whitepaperThe slides

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

Learning objectives

After the lesson the participant can:

Key concepts

AI Decision Record (AIDR)
A record that keeps the short, numbered, immutable structure of the Architecture Decision Record and adds intended purpose, prohibited uses, risk classification, role, data sources, evaluation criteria, human oversight, logging and retention, and retirement criteria.
Retirement criteria
The conditions under which the system is withdrawn or the model retrained. They are the contract that lets evidence re-open a record: when a monitored threshold is breached, the pipeline creates a review task against it.
Model card and datasheet
Version-controlled companions of the record. The card reports a model's intended use, evaluation and limitations; the datasheet documents a dataset. The pipeline fails if the card's reported metrics do not match those the evaluation stage produced.
System card
The description of a compound system as a whole: every component and version, the data flow, system-level evaluation results and the controls. It records that the organisation deploys the general-purpose AI model but provides the compound system it has assembled.
Architecture repository
The single source of truth in which each Annex IV heading has one place where its evidence lives, so that the technical documentation is generated, versioned and signed on every model promotion and every merge to the decision log.

Interactive exercises

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

Interactive exercise 1 · Put in order

The life of AIDR-0007

Put the events in the life of Nordvik Region's decision record for case prioritisation in the order in which they happened.

Interactive exercise 2 · Match

Companions in the architecture repository

Match each artefact with what the chapter says it documents or does.

Teaching plan

10 minThe teacher gives the three reasons the classic record falls short for AI: the model does not stay fixed, deployment carries a regulatory classification, and intended purpose has a legal meaning.
25 minRead AIDR-0007, AIDR-0011, AIDR-0021 and AIDR-0027 together; for each, participants name the field that does most work and the option that was rejected.
15 minFollow AIDR-0007 to its supersession by AIDR-0018, then cover model cards, datasheets, the system card and the mapping of repository paths to Annex IV.
30 minExercise: participants write an AI Decision Record for a real choice; a neighbour acts as reviewer and looks for blank fields and untestable criteria.
10 minClose with the three habits that make people write records and the threshold per usage mode for when a record is needed.

Discussion

  1. The retirement criteria of AIDR-0027 are deliberately asymmetric. What does that asymmetry say about the difference between a control that has failed and a system that performs poorly?
  2. Nordvik Region shows caseworkers a priority band with reasons instead of a numeric score, and queues a random sample without a band. How would you show that human oversight in one of your systems is effective and not nominal?
  3. Which facts about your AI systems are written by hand in more than one document today, and which of those documents would contradict each other first?

Written exercise

Exercise · 30 minutes

Write an AI Decision Record for a real choice

Pick a decision about an AI system that your organisation has taken or is about to take, for example retrieval against fine-tuning, or advisory use against write access. Write the record in the form of the chapter's template: context with measured figures you can defend, intended purpose, prohibited uses, risk classification and role, data sources with lawful basis, at least two options considered with the reason each lost or won, evaluation criteria as metrics with thresholds, the human oversight path, and retirement criteria. Mark any field that does not apply as not applicable with a reason. State which reviewers the front matter would add to the pull request.

Deliverable: A complete AI Decision Record of one to two pages, with testable evaluation and retirement criteria and a list of required reviewers.

Self-test

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

  1. In AIDR-0011, why did Nordvik Region reject showing caseworkers a numeric score for each claim?

    Show the answer

    A. Because a numeric score invites over-reliance
    The chosen design shows a priority band with the three main reasons; the band rather than a score reduces automation bias.

  2. How is an accepted AI Decision Record changed when the decision no longer holds?

    Show the answer

    D. Only its status fields change, in the pull request that accepts a successor stating why it was retired
    The body of an accepted record is never edited. Supersession is the only way to change a decision, and the successor carries the reasoning.

  3. What role analysis does the chapter say is recorded in the system card of a compound system built on a third-party language model?

    Show the answer

    C. The organisation deploys the general-purpose AI model but is the provider of the compound system it has assembled
    The system card is where the roles are decided: if the compound system is high-risk, the provider obligations of Article 16 apply to the organisation, not to the model vendor.