Tools · Module 2 · Architecture and Delivery

Platform and Infrastructure Tools

The lesson covers the tools for building and running the AI platform: infrastructure as code with Terraform and OpenTofu, Kubernetes, the model registry entry, MLflow, the self-hosting readiness check, the RAG system configuration, the gateway security configuration and the team artefacts around a platform. Participants learn to separate open standards and replaceable components from products whose replacement has a price, and to say which tools apply at each usage mode.

Lesson 6 of 25Chapter 675 minutes

Read the chapterThe whitepaperThe slides

All courses / Tools / Module 2 / Chapter 6

Learning objectives

After the lesson the participant can:

Key concepts

Model registry entry
An immutable record from AI Platform and Security, Chapter 7, that links a model version to its run, data, model card, evaluation and approvals. Pipelines write it, except for the approvals, which name people who did not build the model.
Self-hosting readiness check
A checklist artefact, all of whose items must pass before a model is self-hosted in production. Each key has an owner or a test; the default patch times are seven days for critical vulnerabilities and 24 hours where exploitation is known.
RAG system configuration
An artefact that codifies ingestion, chunking, embedding, index and retrieval settings in one versioned file linked to an AI Decision Record. The entitlement filter runs before search, so a user's permissions limit what can be retrieved.
Gateway security configuration
A gateway policy of AI Platform and Security, Chapter 17, with a model allow-list, signed models, a client workload identity and guardrail layers that each assume the previous one failed. It is a defensive control kept in the repository.
Data product descriptor
The file the platform reads before it trains: it describes a data product's owner, schema, quality, lineage and access, including a classification block for personal data.

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

Platform tools and what the series uses them for

Match each third-party tool of Chapter 6 with the one-line purpose its family table gives.

Interactive exercise 2 · Scenario

Local model servers on engineers' workstations

Choose what the platform lead should do, following the chapter's treatment of local servers and the gateway.

Teaching plan

15 minPresent Figure 6.1, the layers of the platform, and the two kinds of choice: open standard or replaceable component, versus product with a replacement price. Cover Terraform, OpenTofu and state.
15 minRead the Nordvik Region registry entry for claims-ranker 4.0.0 and the self-hosting readiness check line by line; participants name the owner or test behind each item.
10 minPresent the RAG configuration and the gateway configuration, then the table of tools per usage mode and the rule to route traffic through the gateway wherever a tool allows it.
25 minExercise: participants run the self-hosting readiness check and draft a registry entry for one model.
10 minDebrief: which items had no owner or test, and whether the approver of each promotion built what was promoted.

Discussion

  1. The volume ties the retention of a model version to administrative law, not to storage cost: a case handled with a version can be appealed. What does that imply for the registry of a public authority?
  2. The chapter says the answer to local model servers called by agentic coding tools is the gateway, not a ban. What makes a ban the weaker control?
  3. Nordvik Region keeps the gateway, the registry, evaluation and the control plane but leaves training machinery to its providers. What does it still have to be able to show about a procured model?

Written exercise

Exercise · 25 minutes

Readiness check and registry entry for one model

Pick one model your organisation runs or plans to run itself, or take a fallback model that Hansa Mutual self-hosts in Frankfurt. First apply the self-hosting readiness check: for licence review, no unauthenticated endpoint, patch times for critical and known-exploited vulnerabilities, and weights taken only from the registry in a signed form, write the owner or the test and whether the item passes today. Then draft a model registry entry for the version: artefact location and signature, training run, data versions, model card, evaluation report, and the names or roles of approvers who did not build the model. State the retention you would set and the reason.

Deliverable: A completed readiness check with pass or fail per item and a drafted registry entry with independent approvers and a retention line.

Self-test

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

  1. Why does the chapter call the gateway the single platform component that is not optional?

    Show the answer

    B. It is the only place where logging, redaction, routing and budgets apply to every AI call
    The Summary states that the gateway is the single component that is not optional because logging, redaction, routing and budgets apply there to every AI call; in Modes 1 to 3 the effort goes into making traffic reach it.

  2. In the RAG system configuration, when does the entitlement filter run, and why?

    Show the answer

    C. Before search, so that a user's permissions limit what can be retrieved
    The volume's design point is that the entitlement filter runs before search, so a user's permissions limit what can be retrieved rather than relying on a later layer to hide it.

  3. What do the approved_by fields of the model registry entry record?

    Show the answer

    A. People who did not build the model
    The approvals are the one part of the registry entry that pipelines do not write, and they name people who did not build the model. The chapter generalises this: every promotion has an owner who did not build what is promoted.