AI Platform and Security · Module 2 · Data, Models and DevSecMLOps

Data Architecture for AI

The lesson starts at the lowest layer of the reference architecture, the data foundation. Participants learn why a trained model is derived data, how data products, descriptors, datasheets and data contracts make ownership testable, how platform-captured lineage carries retention and erasure into every derived store, where feature stores and vector stores differ, why synthetic data has limits, and how the GDPR, EDPB Opinion 28/2024, the Data Act and the Data Governance Act shape the design.

Lesson 6 of 25Chapter 675 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Platform and Security / Module 2 / Chapter 6

Learning objectives

After the lesson the participant can:

Key concepts

Data product descriptor
A file the platform can read that names the product's owner, outputs, classification, lawful basis, retention, datasheet and lineage. Its lawful basis block separates operational use from model training because the GDPR does.
Data contract
A statement of what the consumer may rely on, in a form a test can check. The platform verifies it on every publication, so that when the contract breaks the producer's pipeline fails, not the consumer's model.
Lineage and provenance
Lineage answers where a value came from; provenance answers how an artefact came to exist. The platform captures lineage instead of teams declaring it, so that it can say which models consumed a dataset version.
Point-in-time join
The defining capability of a feature store, which keeps future information out of a training set. A vector store's problem is different: access control, since a chunk is still its source document.
Model collapse
The predictable degradation of models trained recursively on data generated by earlier models: first the tails of the distribution disappear, later the output converges on a few high-probability patterns. Synthetic data is therefore labelled in lineage.

Interactive exercises

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

Interactive exercise 1 · Sort

Feature store or vector store?

Sort each characteristic under the store the chapter attributes it to.

Interactive exercise 2 · Scenario

An erasure request reaches the claims data

Apply Nordvik Region's retention and erasure rule RET-04 to a request from a resident.

Teaching plan

10 minThe teacher presents the inversion: in an AI system behaviour is derived from data, and a model is a lossy, cached transformation of its training set.
20 minRead the descriptor, the Nordvik Region datasheet excerpt and the contract together; participants find the line in each that would change a model design or stop a training job.
15 minCover lineage, the retention and erasure rule RET-04, the two stores, synthetic data and the four GDPR provisions with EDPB Opinion 28/2024.
25 minExercise: write a data contract and an erasure propagation table for one dataset; pairs test each other's contracts for clauses that no test could check.
5 minClose with where to start: data products from the use cases, lineage capture for every pipeline on the first day.

Discussion

  1. The chapter says purpose limitation is the GDPR principle AI programmes break most often. Which dataset in your organisation was collected to run a service and is now a candidate for training?
  2. RET-04 does not promise to delete a person from a trained model at once. How would you explain that position to a data subject and to an auditor?
  3. The known gaps section of a datasheet is said to be the one that changes model design. What would an honest known gaps section say about a dataset you rely on?

Written exercise

Exercise · 25 minutes

A data contract and an erasure path

Choose a dataset that feeds or grounds an AI system in your organisation, or use Hansa Mutual's policy-wordings corpus. Write its data contract: schema constraints, a distribution range for one numeric column or the metadata every document section must carry, permitted purposes, prohibited purposes, a change policy and at least two tests. Then list every derived store the data reaches, such as training releases, feature store rows, vector index chunks, logs and caches, and state for each the retention period and the action on an erasure request, following the pattern of RET-04. Say how the rule would be exercised to prove it works.

Deliverable: A data contract of about fifteen lines and a table of derived stores with retention, erasure action and the test that exercises the rule.

Self-test

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

  1. Which two kinds of field does a data contract add for AI consumers, according to the chapter?

    Show the answer

    B. The distribution of numeric columns and the permitted purposes
    A model served on a different distribution has silently changed behaviour, and data collected under one lawful basis cannot be repurposed by the consumer.

  2. Why can a public authority not rely on legitimate interest for training a model in the performance of its tasks?

    Show the answer

    D. Because the final sentence of Article 6(1) of the GDPR excludes it, leaving public task under Article 6(1)(e)
    The authority relies on public task laid down in law, so its descriptor points to the authorising provision, and a dataset without one cannot be used for training.

  3. How does the vector store handle access control in the chapter's design?

    Show the answer

    A. The index carries its sources' access attributes, and the retriever filters on entitlements before similarity search
    A chunk is still its source document, so entitlements are applied before search and no restricted chunk becomes a candidate.