
Engineering AI in your role (role tracks) · Standard gear
As of 19 November 2026. Reviewed and published, version 1.0.0. Big Widget Company, its people, its models and its numbers are made up for teaching. Every real framework, paper and case below is real and cited. The role tracks, the three questions, the track rows, the release rule and the rail mapping are this course's own practice, not a law or a standard. Where we do not know something, we say so, and we say who checks next.
What this module does
Figure data as text
Three questions for any role
| Stage | What it shows |
|---|---|
| GET TO YES (COURSE) | Does it work? Held-out data like real use, a baseline, uncertainty, by slice. |
| STAY AT YES [s1] | Does it still work? Which signal, which threshold, who is told, and hold or roll back. |
| RECOVER TO YES [s2] | Could a stranger check it? Which records, which versions, decided by whom, checkable without trust. |
Modules 400.1 to 400.9 taught how models are trained, adapted, fed with data, operated, secured, evaluated, tested for fairness, recorded and audited. This module puts that work into your own job at Big Widget Company, the made-up 100,000-person maker of complex, expensive, car-like widgets used across this course.
You take the track for your role. Big Widget has eleven engineering tracks, listed below. Then you answer two things:
- For one model in your role, name the evaluation that would show it works, the monitoring that would show it still works, and the evidence a stranger would need (400.R-a).
- Map your role's work to one cert-prep rail and the course objectives it draws on, and explain what a certification does and does not prove (400.R-b).
Two beliefs this module corrects:
- "Evidence is the governance team's job, not the engineer's." The engineer is the one who chose the test set, set the threshold and shipped the version. If those choices are not written down when they are made, nobody can write them down later.
- "A certification proves the system I built is safe." A certification is about a person. Whether a particular system is fit for its job is shown by evidence about that system. A level or a badge describes a person's practice, never a system's assurance.
Three questions for one model
Every track asks the same three questions about one model the learner builds, adapts, runs or supports. They sit on the three yeses from Level 100.
| Question | What it asks | Where in the three yeses | Where the course taught it |
|---|---|---|---|
| Does it work? (evaluation) | On held-out data that looks like real use, against a baseline, with uncertainty, broken down by the slices that matter | Get to Yes: before the release decision | 400.6, 400.7 |
| Does it still work? (monitoring) | Which signal, which threshold, who is told, and what happens next (hold, roll back) | Stay at Yes: while it runs | 400.4 |
| Could a stranger check it? (evidence) | Which records, with which versions, decided by whom, verifiable without trusting the team | Recover to Yes: after, on demand or on incident | 400.8, 400.9 |
The release decision itself is one of four answers: allow (go ahead), constrain (only this far), hold (wait for a person) or deny (no). A hold is not a slow yes. A named person releases it, or it stays held. An AI tool may help draft the evidence, but it never records the release decision. A person does.
These questions are not new ideas invented for this course. They line up with outcomes that a published framework and two papers already name.
Does it work? The NIST AI Risk Management Framework (AI RMF 1.0, January 2023) lists, under its MEASURE function, that "Test sets, metrics, and details about the tools used during TEVV are documented" (TEVV is test, evaluation, verification and validation).1 It also asks that the system to be deployed is "demonstrated to be valid and reliable", and that "Limitations of the generalizability beyond the conditions under which the technology was developed are documented".1 Breck and colleagues' ML Test Score, a rubric of 28 actionable tests for production machine-learning systems, includes "A simpler model is not better" (regularly test against a very simple baseline model) and "Model quality is sufficient on all important data slices".2 Slicing, they write, "avoids having fine-grained quality issues masked by a global summary metric".2
Does it still work? The AI RMF asks that "The functionality and behavior of the AI system and its components ... are monitored when in production".1 Its MANAGE function asks that post-deployment monitoring plans are implemented, including mechanisms for "appeal and override, decommissioning, incident response, recovery, and change management".1 The ML Test Score explains why a launch score is not enough: "Validation data will always be older than real serving input data", so quality measured before serving "is only an estimate".2 Its monitoring tests include checking that data invariants hold for inputs, that models are not too stale, and that prediction quality has not regressed; for quality it says thresholds must be set and "a responder should be notified immediately if quality drifts outside that threshold".2 Its infrastructure tests include that serving models can be rolled back, and it says operators should practise rolling back "normally, when not in emergency conditions".2
Could a stranger check it? Mitchell and colleagues proposed model cards: "short documents accompanying trained machine learning models that provide benchmarked evaluation in a variety of conditions".3 A model card also discloses "the context in which models are intended to be used, details of the performance evaluation procedures, and other relevant information".3 Its proposed sections are Model Details, Intended Use, Factors, Metrics, Evaluation Data, Training Data, Quantitative Analyses, Ethical Considerations, and Caveats and Recommendations.3 The authors say quantitative analyses "should be disaggregated, that is, broken down by the chosen factors", with confidence intervals when possible.3
But the same authors also say a card is not proof on its own: "the usefulness and accuracy of a model card relies on the integrity of the creator(s) of the card itself".3 They call model cards "one transparency tool among many", alongside, for example, algorithmic auditing by third parties.3 That is why the third question asks what a stranger would need, not what the team would show.
Signing the card does not close that gap. A signature shows who made a record and that nobody changed it afterwards. It does not show that the numbers in it are right, or that the monitors and the release gate actually ran. So a stranger needs the underlying records and a method they can repeat, not just a signed summary. The signed, versioned, tamper-evident bundle a stranger verifies offline, against a key and a checkpoint received separately, is what 400.8 and 400.9 taught.
What the bundle holds, and what it never holds. The shareable record carries hashes, versions, the decision and who made it, and the policy it was made under. It never carries prompts, model outputs, payloads or personal data: no customer claims, no employee details, no raw test images. Those stay in a separately controlled work record at Big Widget that the bundle points to by hash. A hash is a pointer, not permission to share what it points to.
Why evidence is the engineer's job
The AI RMF treats governance as a function that runs through all the others, not as a separate team's step at the end. It says governance "is designed to be a cross-cutting function to inform and be infused throughout the other three functions".1 One of its GOVERN outcomes is that "Roles and responsibilities and lines of communication related to mapping, measuring, and managing AI risks are documented and are clear to individuals and teams throughout the organization".1
It also separates building from checking. Its figure of the people involved across the AI lifecycle notes that those "building and using the models" are separated, as a best practice, from those "verifying and validating the models".1 And it asks that "Internal experts who did not serve as front-line developers for the system and/or independent assessors are involved in regular assessments and updates".1
Put those together and the engineer has two duties, not zero:
- Produce the evidence while doing the work: the test set and its version, the baseline, the slices, the metric and which direction is better, the threshold and why it was chosen, the monitor and who it alerts, the rollback that was practised.
- Do not be the one who decides the release. The RMF asks for the separation. This course goes one step further and has an independent validator record the release decision (400.9). The engineer's job is to make that check possible. Not being on the build team is the minimum here; 400.9 also keeps the validator separate from the person who holds and operates the system.
What happens when nobody can check. In Bates v Post Office Ltd (No 6), judgment of 16 December 2019, Mr Justice Fraser found that the Post Office's Legacy Horizon accounting system "was not robust", and that although Horizon Online in its HNG-X form was better, its "robustness was questionable, and did not justify the confidence placed in it by the Post Office in terms of its accuracy".4 In the same paragraph he said the later HNG-A "is a different matter", which the experts agreed is "far more robust than Horizon in earlier times".4 Horizon was an accounting system, not a machine-learning model, and the finding is about named versions. It is here for one lesson that 400.8 and 400.9 build on: confidence in a system's output is not evidence that the output is right.
A worked example: the paint-line inspection model
Made up for teaching. Big Widget's paint line has cameras. A vision model flags panels with paint defects for a person to inspect. The team wants to replace an older rule-based check with it.
Does it work? (evaluation, Get to Yes)
- Held-out data that looks like real use. Images collected the way the line collects them: the same cameras, lighting, colours and shifts, from a period the team did not use while building.
- Why "the same way" is not enough on its own. Recht and colleagues built new test sets for CIFAR-10 and ImageNet "by closely following the original dataset creation processes".5 A broad range of models still lost 11 to 14 percentage points of accuracy on the new ImageNet set.5 So the team writes down exactly how its test set was built, and does not treat one test set as the truth about the task.
- A baseline. The old rule-based check, scored on the same images.2
- Slices. Results broken down by paint colour, camera and shift, with intervals, so a good average cannot hide a bad slice.23
- A metric tied to the harm. The share of real defects the model flags (missed defects reach customers), with the decision threshold and the reason for it written down.3
- Which direction is better. For this metric, higher is better. The pass rule (below) is written for that direction.
Say which way is better, then write the pass rule. Some metrics improve as they go up: the share of defects caught, or the share of safety claims routed. Others improve as they go down: forecast error, simulation error. The course's pass rule, written before the run, has three parts:
- A worthwhile improvement. The whole interval for the difference from the baseline sits on the better side by at least the smallest improvement worth acting on. For a higher-is-better metric, that means the lower end of "model minus baseline" is above it. For an error, it means the upper end of "model error minus baseline error" is below minus that amount.
- No bad slice. Every slice clears its own floor. For a higher-is-better metric, the lower end of each slice's interval is at or above the floor. For an error, the upper end of each slice's error interval is at or below the most error that slice can tolerate.
- Undecided means hold. If an interval is too wide to tell, the answer is "insufficient evidence": hold and re-check, not pass.
Made-up numbers to show the direction matters. A recall improvement with a difference interval of [0.08, 0.12] and a smallest worthwhile improvement of 0.02 passes part 1. A forecast whose average error drops from 10 to 7, with an error-difference interval of [−4, −2] and a worthwhile improvement of 1, also passes: the whole interval is below −1. An error that rises from 10 to 12, interval [1, 3], fails. Apply the higher-is-better rule to the raw errors, with a smallest improvement of zero, and it goes backwards: the real improvement (lower end −4) fails, and the regression (lower end 1) passes. An interval of [−3, 1] is too wide to decide: hold.
The floors for slices are not the decision threshold. The decision threshold is the score at which the model flags a panel. The floors are the least acceptable result for each slice. Write both down, with reasons, before the run.
Does it still work? (monitoring, Stay at Yes)
- Inputs. Checks that incoming images still match what the model was tested on, such as brightness, size and camera id, with an alert when they diverge.2
- Quality on live data. A person labels a sample of the panels the model passed, so missed defects are counted, not assumed. A threshold, set before launch, names who is told when the miss rate crosses it and what happens next: hold, then roll back if the last good version is safe under current conditions.21
- What that sample measures. It gives the share of passed panels that had a defect. To estimate the share of all defects the model catches, the team also needs the number of panels passed and the confirmed defects among flagged panels, over the same weeks.
- Age and dependencies. An alert on how old the model in production is, and a notice to the team when something it depends on changes, such as the camera software.2
Recover to Yes. A rollback can contain harm that a new release caused, if the fallback is compatible and safe under current conditions. It does not undo a change in the world. A change in live inputs may degrade the old version a little, leaving it within its bounds, or it may make both versions unsafe. Suppose the camera software changes and the new images hide defects from both the new model and the old one: switching back recovers nothing. The cause alone does not tell you which case you are in; a check of the fallback on current images does. So the first step is to hold the affected action, not to assume the old version is safe. On the paint line that means people inspect every panel by hand until the model's named owner has checked that the fallback works on today's images. Containment is not recovery either. The team finds the cause, re-runs the evaluation on the repaired version, and goes back through the release decision before claiming it is at yes again. Until then, the honest status is "held", not "fixed".
Could a stranger check it? (evidence)
- A model card for this version: intended use (flag for a person, never auto-reject), evaluation data, metrics and their direction, sliced results with intervals, caveats.3
- The versions of the model, the test set and the configuration, and the monitoring thresholds.
- The release decision, recorded by a named validator who did not build the model. The separation follows the AI RMF;1 the signed decision is this course's practice (400.9).
- A practised rollback record (400.4).2
- All of it in a bundle a stranger verifies offline against a key and a checkpoint received separately (400.8). The test images themselves stay in Big Widget's controlled work record; the bundle carries their hash.
The eleven tracks
Each row is one track. The example models and the answers in the row are made-up Big Widget examples, written as course guidance. Where a real case sits behind a row, the row cites it; otherwise it names the module that teaches it. The last column is the cert-prep rail the track most often draws on (next section). Many roles touch more than one rail.
| Track | Example model (made up) | Does it work? | Does it still work? | What a stranger needs | Case or module | Rail |
|---|---|---|---|---|---|---|
| ML engineering | A language model fine-tuned on service manuals | Task score against the base model, and the safety evaluation re-run after every fine-tune | Refusal and error rates on a fixed probe set, per release | Base model, data and fine-tune versions; both evaluation runs | Fine-tuning can degrade safety6; 400.2, 400.L | ML engineering |
| Data science | A warranty-claim triage model | Held-out claims from a later period, against the current rule, with intervals; higher recall is better | Live quality from a labelled sample; drift in claim mix | Model card with sliced results3 | 400.6, 400.7 | Data |
| Data engineering | The warranty-claim triage model, through the pipeline that feeds it | Role-owned: schema and invariant tests on every load. Model-level: the data science team's evaluation, re-run on each new dataset version | Invariants on live inputs; alerts when upstream sources change2 | Dataset versions and lineage, linked to the model version each one trained | 400.3 | Data |
| MLOps and platform | The paint-line inspection model, through the serving platform | Role-owned: canary and validation before serving.2 Model-level: the inspection team's evaluation, which the gate checks is present and passing | Model age, latency and quality alerts with named owners2 | A practised rollback record restoring model, data and configuration together | 400.4 | ML engineering |
| Security engineering | The service-manual assistant | Tests for extraction of training data and for injection | Logs of unusual query patterns | Attack test results, key custody and signed logs | Training-data extraction7; 400.5 | AI security |
| Evaluation and quality | The warranty-claim triage model, through Big Widget's evaluation harness | Model-level: fresh test sets built the documented way; baselines; intervals. Role-owned: the harness re-scores a fixed, known case and gets the recorded answer | Re-evaluation on a schedule and after every change | Test sets, metrics and tool details documented1 | New test sets lowered scores5; 400.6 | Data |
| Manufacturing and quality inspection | The paint-line vision model (above) | Held-out line images, sliced by colour, camera and shift | Labelled sample of passed panels; input checks | Model card, versions, signed release | New test sets lowered scores5; 400.6 | ML engineering |
| Maintenance and reliability | A model predicting bearing failure from vibration data | Back-test on held-out machines, against the fixed service schedule | Missed failures counted from the work-order record, once failures are known; the label delay is stated | Which machines, sensors and periods it was tested on | 400.4, 400.6 | ML engineering |
| Forecasting and supply chain | A parts-demand forecast | Error against a naive forecast on later periods, with ranges; lower error is better | Error tracked each period once actual demand is in; alert when it leaves its band | Forecast versions and the data each one used | 400.6 | Data |
| Service and warranty | A model routing safety-related claims to engineers | Share of real safety claims it routes, by product line | Labelled sample of claims it did not route | Sliced results; who reviews unrouted claims | 400.6, 400.7 | Data |
| Engineering and simulation | A surrogate model that speeds up a stress simulation | Error against the full simulation on held-out designs, inside the tested range; lower error is better | Spot checks against the full simulation; alert outside the tested range | The tested range and its limits, written down1 | 400.6 | ML engineering |
Component tracks. Three tracks own a component rather than a model: the pipeline, the serving platform and the evaluation harness. They still answer 400.R-a for one model, the one their component supports. They test their own component, and they name the model-level evidence and the team that supplies it. Component evidence does not stand in for model evidence. A schema check cannot show the triage model's recall. A canary cannot show the inspection model is accurate. A harness cannot validate its own measurements just by existing.
Two course rules run through every row. First, the team that built the model does not decide its own release. Second, any threshold, slice, metric direction or rollback that is not written down before launch does not count as evidence after it.
The cases behind the rows
ML engineering: re-check after every fine-tune. Qi and colleagues (ICLR 2024) report that, in their tests, fine-tuning GPT-3.5 Turbo on only 10 adversarially designed examples jailbroke its safety guardrails, at a cost of less than USD 0.20 through OpenAI's APIs.6 They also report that fine-tuning on benign, commonly used datasets can degrade safety alignment, though to a lesser extent.6 This is a measured result on 2023 models and APIs, not proof that every model loses every guardrail. The lesson for the track: a fine-tuned model is a new model, and its safety evaluation is re-run, not inherited.
Security engineering: test what the model gives away. Carlini and colleagues (USENIX Security 2021) extracted hundreds of verbatim text sequences from GPT-2's training data by querying the model.7 The examples included public personal information such as names, phone numbers and email addresses, and some appeared in only one document in the training data.7 The lesson for the track: an extraction test belongs in the evaluation, and its result belongs in the evidence. The result goes in as a count and a pass or fail, not as the extracted text.
Evaluation and quality, and inspection: one test set is not the task. The Recht study above.5
Every track: confidence is not evidence. The Horizon judgment above.4
Cert-prep rails: what a certification does and does not prove
Level 400 maps four cert-prep rails to the course objectives they draw on. These are this course's map (levels/400/objectives.yml), not a vendor's syllabus. The course prepares people for vendor-proctored exams; it never sits them and never shares live exam content. No certification vendor or exam is named until Bob clears it, so every rail's vendor and exam read "not cleared" (as of 19 November 2026).
| Rail | What it covers | Draws on | Tracks that usually take it |
|---|---|---|---|
| ML engineering | A cloud machine-learning engineering certification: build, deploy and monitor models | 400.2-a, 400.2-c, 400.L-a, 400.4-a, 400.4-b, 400.6-a | ML engineering; MLOps and platform; inspection; maintenance; simulation |
| Data | A data engineering or data science certification: pipelines, data quality, evaluation | 400.3-a, 400.3-b, 400.6-a, 400.6-c, 400.7-a | Data science; data engineering; evaluation and quality; forecasting; service and warranty |
| AI security | An AI or cloud security certification: attacks on ML systems, keys, logs | 400.5-a, 400.5-b, 400.5-c, 400.8-b | Security engineering |
| AI audit | An AI governance or AI management-system audit certification | 400.8-a, 400.8-c, 400.9-a, 400.9-b, 400.9-c | Anyone who will validate or audit other teams' models |
What a passed exam shows, and what it does not. This is course guidance, from what an exam and an evidence bundle are each about.
| A passed certification exam | An evidence bundle | |
|---|---|---|
| It is about | A person | One system, at named versions |
| It shows | That person met the exam's bar, on the date they sat it | What was tested, monitored and decided for that system, and by whom |
| It does not show | Whether any model that person built works, still works or is safe | Whether the people involved hold any credential |
| Who can check it | The certifying body's records | A stranger with the bundle, and a key and checkpoint received separately (400.8) |
The ML Test Score makes the same split from the other side. Its score is meant to measure "how ready for production a given machine learning system is".2 Each test earns half a point if it is run manually "with the results documented and distributed", and a full point if a system runs it automatically on a repeated basis; the final score is the minimum of the four section scores.2 The score belongs to the system and its records. A test that is never run earns nothing, however certified the engineer. A test run once by hand with no written, shared results earns nothing either. This course also asks for automated test results to be in the bundle; that is the course's evidence rule, not part of the paper's score.
So a certification is a reason to trust that someone can produce good evidence. It is never a substitute for the evidence. In 400.P, the stranger verifies the bundle, not the team's credentials.
Your track exercise
Bring this to the project (400.P).
- Pick your track from the table, or write a new row for your role at Big Widget.
- Pick one model in that role. Write its intended use in one sentence, including what it must never do on its own. If your track owns a component, name the model it supports and the team that owns that model's evaluation.
- Does it work? Name the held-out data and how it was built, the baseline, the metric tied to the harm and which direction is better, the slices and their floors, the decision threshold and why, and the smallest improvement worth acting on.
- Does it still work? Name the signal, the threshold, who is told, and what happens next. Say what is held while that person checks, and how you would know the fallback is safe under current conditions. If labels arrive late, say how late and what you watch meanwhile.
- Could a stranger check it? List the records, their versions, who decides the release (not you), what stays out of the bundle, and how a stranger would verify it without trusting your team.
- Your rail. Name the cert-prep rail your role draws on and two of its objectives you will use in 400.P, with one sentence each on how it applies to your model. Then write one sentence on what that certification would not show about your model.
Where you cannot answer yet, write "not known yet" and name who will find out. That is an honest answer; a guess is not.
What this module does not claim
- It does not say Horizon was an AI system. It was an accounting system; it is here for the lesson about confidence and evidence.4 It does not apply the HNG-X finding to the later HNG-A, which the same paragraph treats differently.4
- It does not say every fine-tuned model loses its guardrails. The Qi study measured tested models and APIs in 2023.6
- It does not say the NIST AI RMF is a law or that Big Widget must follow it. NIST says the framework is intended to be voluntary; it is used here because its outcomes name the same three questions.1 The RMF asks for builders and validators to be separated; it does not require a signed release decision. That is this course's practice.
- It does not say a model card proves anything on its own. Its authors say its accuracy relies on the integrity of whoever wrote it.3 A signature on it shows authorship and integrity, not truth.
- It does not name or rank any certification, certification vendor or exam. None is cleared yet. Company names in the cited research (Google, OpenAI) are attribution, not recommendations.
- It does not say a rollback always stops harm. Switching back can help when the fallback is shown to be compatible and safe under current conditions. A change in live inputs or dependencies can make both versions unsafe, and only a check on current conditions tells you whether it has.
- The example models, thresholds, intervals and rows are made up for teaching. None of them was run on a real system, so none of them is checked evidence about one.
Words to know
- Role track: the part of this module for your own engineering role.
- Component track: a track that owns a pipeline, platform or harness rather than a model; it still names one model it supports.
- Evaluation: a measurement, before release, of whether the model does its job on data like real use, against a baseline, with uncertainty.
- Metric direction: whether a higher or a lower value of a metric is better. Write it down before the run.
- Monitoring: measurements after release, with thresholds and named owners, that show whether it still does.
- Slice: a subset of the data, such as one paint colour or one camera, reported on its own so an average cannot hide it.2
- Model card: a short document that goes with a trained model and reports its evaluation, intended use and limits.3
- Release decision: allow, constrain, hold or deny, recorded by a named person who did not build the model (course practice, 400.9). Never recorded by an AI tool.
- Rollback: switching back to the last good model, data and configuration versions together. It can contain a fault the release caused. It is not proof of recovery.
- Evidence bundle: the signed, versioned records a stranger can verify offline against a key and a checkpoint received separately (400.8). It holds no private content.
- Cert-prep rail: this course's map from a kind of vendor certification to the objectives that prepare for it. Vendors not cleared.
- Independent validator: a person who did not build the model1 and who, in this course's practice, records the release decision (400.9).
Further learning (not cited, never copied)
Free university courses listed in levels/400/universities.md for this module: MIT 6.S191 Introduction to Deep Learning; Carnegie Mellon 10-414/714 Deep Learning Systems; and MIT 6.5940 TinyML and Efficient AI Computing (Fall 2026, partial public materials). They are further learning only; this module does not rely on them for any claim.