Level 500: Governance, safety and research · Module 500.R

People from different jobs, one in a lab coat, compare notebooks at a shared table.
Who checks the checker?

Research and governance roles (role tracks) · Plain gear

Reviewed and published, version 1.0.0. Big Widget Company, the people in it and the seven packet cards are made up. The six-part handoff, the seven tracks and the practice rail are this course's own way of working. They are not a law, a standard or an exam. Where we don't know something, we say so.

What this part is for

A receipt carries: hashes, decision, tier, policy hash, key id; A receipt never carries: prompts, outputs, payloads, personal data
The receipt's allowed metadata versus the private content it never carries; packet details belong in a separately controlled work record, and the handoff lists them by hash (s7).
Figure data as text

Keep the evidence, not the secrets

PartWordingSources
A receipt carrieshashes, decision, tier, policy hash, key id[s7]
A receipt never carriesprompts, outputs, payloads, personal data[s7]

The receipt's allowed metadata versus the private content it never carries; packet details belong in a separately controlled work record, and the handoff lists them by hash (s7).

In the last nine modules you did expert work. You checked a paper. You read a safety test. You designed a receipt, a set of rules and a red-team exercise.

Now a hard question: what happens to that work when you hand it on?

Think of a relay race. You can run your leg very fast. But if you drop the baton, the team loses. In this module, the baton is a handoff: a short record that lets someone else check your work and decide what to do next.

You pick one of seven tracks: researcher, auditor, policy staff, red-team lead, standards editor, governance lead or reviewer. Each track has a small made-up packet in this lesson, called a card.

When you finish, you can do two things:

Two wrong ideas this part fixes:

Why hand off to someone else?

Picture a chef who tastes their own soup and says, "Perfect." Maybe it is. But a second taster, who did not cook it, is more likely to notice the salt.

The sources say something close to this about AI work.

So a good check has three things. Someone else does it. There is a record they can follow. And the answer keeps its "it depends" parts instead of hiding them.

The three yeses. The Foundation names three steps: Get to Yes, Stay at Yes, Recover to Yes.4 Here is how a handoff fits them. This is the course's own way of using them.

The six parts of a handoff

Every track uses the same six parts.

  1. What you were given. Name the exact version of the evidence, so nobody mixes it up with another version.
  2. What you checked, and what you didn't. Both lists. If you only list what you checked, it looks like you checked everything.
  3. How sure you are, with limits. Say what you think is true. Say where it holds. Say what evidence changed your mind. Say what it does not show. Say what result would prove you wrong. That last test must be about the thing you claimed, not about something else.
  4. The open question. At least one thing is still not settled. Write it down and mark it open. You do not get to close it yourself. "I don't know yet" is a fine answer here. The Foundation says it "always pairs you with someone".5 Part 6 names that someone.
  5. How to check it. Steps a stranger can follow, with the files they need and the answer they should get. They should not need you in the room. If they can't redo some part, list it as "not checked".
  6. Who checks next. A real person, by name. It must be someone who did not do the work, and who can actually decide. Say what they must decide.

"How sure you are" is the tricky one. "We're very confident it's fair" says nothing a person can check.

NIST says testing should come with a measure of how uncertain the result is, and with written reports.1

Some rules that hold it together.

The packet cards (made up)

Each track gets one small card. Everything you need is on the card. You can do the key check with a pencil. The earlier Level 500 modules plan their own made-up packets, but on 19 November 2026 the ones for 500.6 and 500.7 were not yet in this course's files. So use the card. Name it like this: "500.R, version 0.1.0, Card A".

A made-up example (Card A)

A weak handoff: "I reran it. Pretty sure it works. Maybe some issues with our data. Over to the team."

What's wrong? Which version? Which photos? "Works" where? What issues? And "the team" is not a person.

A strong handoff:

  1. Given: 500.R, version 0.1.0, Card A.
  2. Checked: the six runs on the card. Not checked: whether our photos are labelled right, other cameras, and how exact the 83.5% is with only 200 photos.
  3. How sure: on the paper's photos, the average is 90.9%. That is inside the paper's range. So I can say "the code does what the paper says on the paper's photos". I can't say "it will work on our photos". What would prove me wrong: if someone else reran it on the paper's photos and the average fell outside 90 to 92, I'd take my claim back.
  4. Open question: why is it 7.4 points worse on our photos? The paper's "1 point either way" only tells you how much reruns on its own photos wobble. It can't tell you why our photos score lower. Maybe the labels. Maybe the camera. Maybe the model. Not decided.
  5. How to check: use Card A. Work out the two averages. You should get 90.9% and 83.5%. You don't need Dana's laptop. A full rerun would need the code and photos, which aren't supplied, so that is "not checked".
  6. Who checks next: Priya, who looks after data quality and did not run either test. She can order new checks. She decides which check comes first. One choice: have someone else relabel the same 200 photos and rerun, changing nothing else. If the gap closed, that would point to the labels on these photos. It wouldn't prove labels are the only cause. Nobody buys the model until she decides.

The seven tracks

TrackCardWork you hand onWhat usually stays openWho might check next
ResearcherAA result that didn't rerun the same wayWhy it changedA methods lead who didn't run it
AuditorBA list of missing evidenceDid the control run every time, and work?The control owner's boss, or an outside auditor
Policy staffCA note on what rules may apply, and what facts are missingThe missing factsA lawyer, or the person named to decide
Red-team leadDA ruling on a problem, and a retestWhat nobody tested; a retest by someone newA retester who didn't find the problem
Standards editorEA note that one rule can be read two ways, with an example that tells them apartWhich reading winsThe editors' group, with a named chair
Governance leadFA record of why a gate said "wait"Go ahead, only this far, wait, or no?The leader named as responsible
ReviewerGA note on which claims hold up and which don'tThe author's fixThe author fixes it; a second reviewer decides

When an earlier module's made-up packet is ready and checked, you may use it instead of the card.

Some tips from the sources:

One warning. NIST says its steps "do not constitute a checklist".1 Its playbook is voluntary. Groups can take as many or as few of its ideas as fit them.6 The six parts are the least a handoff needs. They don't prove the work underneath was good.

Four ways handoffs go wrong

  1. "I'm sure." But no reason, no limits and no way to be proved wrong.
  2. The quiet close. You mark your own open question as done.
  3. Handing it back to yourself. The next checker is you, your partner on the work, or "the team".
  4. Steps only you can follow. The check needs your laptop or your memory.

Your practice and the practice rail

Level 500 has one practice rail. It points toward an exam for people who audit AI governance. The rail's shape comes from this course's own plan for Level 500, not from a source. The course does not name the exam or the company that runs it. Bob decided on 18 November 2026 to keep them unnamed until he clears each one. The course does not give the exam and does not claim to match it.

The rail uses six course goals: 500.6-a, 500.7-b, 500.8-b, 500.9-d, 500.R-a and 500.R-b. It asks you to practise three things:

For each handoff you write, make a small table. In one column, put the part of your handoff. In the next, put which of the three practices it shows. In the last, put the course goal it links to.

Proof about you is not proof about the system

This is the big idea of this part.

Think about a driving test. Passing it says you can drive. It says nothing about whether the car's brakes work. You still need the brakes checked.

First ask: what claim is this evidence for? The same item can count for two claims. Morgan's ruling on Card D says something about Morgan's skill. It also says something about the chatbot.

Even system proof only shows a little at a time:

NIST keeps people and systems apart too. One of its steps is about training people.1 Others are about testing the system and writing down how it was tested.1 NIST's list of what makes an AI system trustworthy, such as being safe, secure and fair, is about the system, not the person checking it.1

So:

Check yourself

  1. A handoff says, "The model is fair. We're very sure." What three things are missing?
  2. On Card D, the person who found the problem also retested the fix. Who should check next, and why?
  3. Someone says your practice table "proves our hiring tool is ready for audit". What claim is the table proof for? What is wrong with what they said?

Words to know

Sources

  1. s2 Tabassi, Elham (National Institute of Standards and Technology) (2023). Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1. Standard. Checked 2026-11-19 by source-checker agent (Claude, fresh session; not the writer, reviser, item writer or an earlier checker), 19 Nov 2026, round 3 re-check. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  2. s3 Raji, Inioluwa Deborah; Smart, Andrew; White, Rebecca N.; Mitchell, Margaret; Gebru, Timnit; Hutchinson, Ben; Smith-Loud, Jamila; Theron, Daniel; Barnes, Parker (2020). Closing the AI Accountability Gap: Defining an End-to-End Framework for Internal Algorithmic Auditing. Paper. Checked 2026-11-19 by source-checker agent (Claude, fresh session; not the writer, reviser, item writer or an earlier checker), 19 Nov 2026, round 3 re-check. ↩ ↩ ↩
  3. s5 Pineau, Joelle; Vincent-Lamarre, Philippe; Sinha, Koustuv; Larivière, Vincent; Beygelzimer, Alina; d'Alché-Buc, Florence; Fox, Emily; Larochelle, Hugo (2021). Improving Reproducibility in Machine Learning Research (A Report from the NeurIPS 2019 Reproducibility Program). Paper. Checked 2026-11-19 by source-checker agent (Claude, fresh session; not the writer, reviser, item writer or an earlier checker), 19 Nov 2026, round 3 re-check. ↩ ↩ ↩ ↩ ↩
  4. s6 AiGovOps Foundation (n.d.). AiGovOps Foundation Manifesto. Official doc. Checked 2026-11-20 by source-checker agent (Claude, fresh session; not the writer, reviser, item writer or an earlier checker), 20 Nov 2026, round 7 re-check. ↩ ↩ ↩ ↩
  5. s7 AiGovOps Foundation (n.d.). AiGovOps Foundation Practice (home page). Official doc. Checked 2026-11-20 by source-checker agent (Claude, fresh session; not the writer, reviser, item writer or an earlier checker), 20 Nov 2026, round 7 re-check. ↩ ↩
  6. s1 National Institute of Standards and Technology (2026). NIST AI RMF Playbook. Official doc. Checked 2026-11-20 by source-checker agent (Claude, fresh session; not the writer, reviser, item writer or an earlier checker), 20 Nov 2026, round 7 re-check. ↩ ↩

Next: the quiz