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) · Technical gear

Reviewed and published, version 1.0.0. Big Widget Company and packet Cards A–G are fictional, course-owned teaching examples, not real records or conformance tests. The handoff tuple, the role tracks, the notation and the prep-rail mapping are this course's own design, not a standard, a conformance test or an exam syllabus.

Scope

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).

This gear treats an expert's output as an object that must survive transfer to an independent party. It defines an assurance handoff formally, states the conditions under which it is checkable (500.R-a), and types evidence relative to the claim it is offered for, so that preparation evidence about a person cannot be used as control evidence about a system (500.R-b).

ObjectiveFormal objectPrimary evidence used
500.R-aHandoff tuple $H$; bounded confidence statement $\kappa$; independence and authority conditions on the next ownerNIST AI RMF 1.0, MEASURE 1.3, 2.1, GOVERN 2.1–2.3, Fig. 3 note1; Raji et al., SMACTR and §52; Pineau et al., NeurIPS 2019 program3; Playbook, for versioning and voluntary use4
500.R-bMapping relation $M$ from handoff parts to rail practices and objectives; claim-relative evidence typing $\sigma(e, c)$Rail structure: this course's Level 500 map (levels/500/objectives.yml), not an external source. Person/system split: NIST AI RMF 1.0, GOVERN 2.2 versus MEASURE 1.3/2.1 and §3 characteristics1

Misconceptions targeted: that expert work is complete when an expert names a question or states confidence (500.R-a), and that completing a prep rail certifies a person or a system (500.R-b).

1. Why transfer, and why to an independent party

Three primary sources motivate the object.

The shared requirement: the verifier is not the producer, the record supports reconstruction, and the result is reported with its structure intact.

Lifecycle placement (course application). The Foundation's three movements are Get to Yes, Stay at Yes and Recover to Yes, and its gate answers "go ahead · only this far · wait for a person · no".5 In those terms, $H$ is an input to a gate, never the gate's answer: $\kappa$ and $N$ bound what a Get to Yes decision may rely on; $F$ and the pinned $v$ keep Stay at Yes honest across versions; and Recover to Yes needs a fix, a retest by $x \notin A(W)$ and a person's ruling, not an announcement.

2. The handoff as a tuple

Let $W$ be a piece of expert work produced by a set of people $A(W)$. A handoff is

H = (P,\ \Gamma,\ \bar\Gamma,\ \kappa,\ F,\ K,\ o)

where

Checkability conditions. $H$ is checkable iff:

  1. Pinning: every input referenced by $\kappa$ and $K$ resolves in $\mu(P)$.
  2. Declared coverage: $\Gamma \cup \bar\Gamma$ covers the claim's scope at the stated granularity, so that silence is never read as coverage.
  3. Rerunnable: each $k \in K$ can be executed by a party $x \notin A(W)$ with only the listed inputs and environment. What cannot be executed that way belongs in $\bar\Gamma$, not $K$.
  4. Open findings persist: no $f \in F$ changes status except by a ruling of $o$ (or a later owner $o$ designates under the same independence rule).
  5. Independence (course rule): $o \notin A(W)$, $o$ is not the author of $H$, and $o$ is not a direct collaborator on $W$. This is the course's design, borrowing the separation of building from verifying (p. 11).1 It removes the producer's own interest in $W$. It does not remove the shared organisational interest that Raji et al.'s §5 limitation names (p. 10).2 Where that shared interest bears on $d$, $H$ should say so and, if possible, choose an external $o$; otherwise record the conflict as an element of $F$.
  6. Authority: $o$ can actually decide $d$. Raji et al. stress identifying decision makers who can drive responses to audit outcomes (p. 3); the AI RMF asks that executive leadership take responsibility for AI risk decisions (GOVERN 2.3, p. 23) and that responsibilities be assigned to supersede, disengage or deactivate systems inconsistent with intended use (MANAGE 2.4, p. 32).21 $o$ is a person; an agent may draft $H$ but is never $o$ and never signs (TRUTH-STANDARD.md, rule 5).

Remediation versus ruling. Assigning a fix for $f$ to a member of $A(W)$ is compatible with condition 5. The ruling that the fix closes $f$ is not: it belongs to $o$.

GOVERN 2.1 is the organisational precondition: roles, responsibilities and lines of communication for AI risk work are documented and clear to individuals and teams throughout the organisation (p. 23).1 The named-person owner field is this course's rule, not a NIST requirement: a handoff whose owner field is a team name fails condition 6. Reading that as falling short of GOVERN 2.1's aim at organisation scale is the course's inference, not a statement in the framework.

Privacy of $P$. If $H$ references a signed receipt, that receipt holds no private content.5 The Foundation's receipt carries "hashes, decision, tier, policy hash, key id" and never "prompts, outputs, payloads, personal data".6 Transcripts and personal data in $P$ stay in a separately controlled work record and enter $\mu(P)$ only as hashes. A hash is not a licence to disclose its preimage.

3. Bounded confidence statements

Define

\kappa = (c,\ v,\ S,\ E,\ N,\ (k^\*, r^\*))

with claim $c$, artifact version $v$, scope $S$, supporting evidence $E$, explicit non-implications $N$ (claims a reader might infer but that $E$ does not support), and a falsifier: a check $k^\$ whose outcome $r^\$ would cause $c$ itself to be withdrawn or narrowed.

Falsifier target. $k^\*$ must test $c$ under $S$. A check whose outcome bears only on some $f \in F$ (an explanation of a discrepancy, say) is a proposed resolution path for $f$, recorded with $f$, not a falsifier for $c$.

Relevance. An item $e$ belongs in $E$ only if its outcome bears on $c$, informally $\Pr(c \mid e) \neq \Pr(c \mid \neg e)$, equivalently a likelihood ratio different from 1. Evidence that would leave your credence unchanged whichever way it came out is decoration.

Non-transfer. Strong evidence for $c$ does not resolve a distinct finding $f \in F$. Formally, $E$ may change $\Pr(c)$ while $f$'s status remains $\text{open}$; the handoff keeps both. "I don't know yet" is a legitimate value for $f$; the Foundation's line is that it "always pairs you with someone",6 which here is $o$.

Uncertainty. The AI RMF says measurement processes should include methods "with associated measures of uncertainty" and "formalized reporting and documentation of results" (p. 28); MEASURE 2.1 asks that test sets, metrics and tool details used in TEVV be documented (p. 29).1 For quantitative claims, report the estimate with its interval, the sample it was computed on, and what variation the interval describes; for qualitative claims, state the scope boundary in words.

Worked instance (Card A, fictional). The paper reports 91.0% on its released test set, ±1.0 across its own seeds. Dana logged three seeds of the released code at one pinned commit on the released set (90.6, 91.2, 90.9; mean 90.9) and on a frozen 200-image Big Widget sample (83.5, 84.0, 83.0; mean 83.5). Then:

What the intervals measure. The paper's ±1.0 is seed-to-seed spread on the released set; it calibrates $k^\*$. It is not an interval on a between-set difference, and no sampling interval for the 200-image estimate is given, so the precision of 83.5 is in $\bar\Gamma$. The drop exceeds the reported seed spread by a wide margin, which makes seed variation of the kind the paper measured an unlikely explanation on its own, and says nothing more. No cause is attributed in $H$.

Resolution path for $f$ (recorded with $f$, not in $\kappa$). A controlled relabelling check: a second labeller relabels the same 200 images while code, seeds and images are held fixed. If the gap closed, label error would be supported as a contributor on this sample; it would not establish labels as the sole cause beyond it. A camera-controlled comparison is an alternative path. $o$ = Priya, a data-quality lead not in $A(W)$ with authority to commission checks, decides which path runs first; the purchasing decision holds until she rules.

$K$ for this lesson. Recompute both means from Card A; expected 90.9 and 83.5. A full rerun needs the code, environment and images, which are not supplied: those are in $\bar\Gamma$.

4. Role tracks as instances of $H$

Each track instantiates $H$ on one packet card from the standard gear (Cards A–G). As of 19 November 2026 the runnable synthetic packets and verifier for 500.6 and 500.7 are not in this course's repository, so no track depends on them; a learner may substitute an earlier module's synthetic packet once it is published and checked. On every card, results the reader cannot re-execute (Card B's signature verification, Card D's prompts against the version-4 build) go in $\bar\Gamma$.

TrackCardArtifactTypical $c$Dominant open $f$Typical $o$
ResearcherAReplication discrepancyReproduces on released data at $v$Cause of divergence on new dataData-quality or methods lead outside $A(W)$
Auditor or assessorBMissing-evidence registerRefunds 1–2 carry both required records; 3–4 do notControl execution on unregistered cases; effectivenessExternal assessor or control owner's manager
Regulator or policy staffCScope-exception memoDuty's application turns on one missing role factThe role fact; any legal conclusionCounsel or named decision-maker
Red-team leadDRuling and retest handoffF-1 accepted; listed prompts logged as refused on version 4Coverage beyond the list; retest by non-testerRetester other than the tester
Standards editorEVersioned ambiguity / test-vector noteClause 5 admits two readings at version 0.3; V1 separates themAdopted readingEditors' group, named chair
Governance leadFEscalation recordGate answered hold for the use; required items 1–2 absentGo ahead, only this far, wait, or noAccountable executive
ReviewerGEvidence/revision dispositionClaim 1 supported by Card A; claims 2–3 notAuthor's revisionAuthor for the fix; second reviewer rules on the re-read

Track notes, with primary support:

Against checklist use. The AI RMF states its actions "do not constitute a checklist" and are not necessarily ordered (p. 20), and that it does not prescribe risk tolerance (p. 7).1 The Playbook is for voluntary use; organisations may borrow "as many – or as few – suggestions as apply".4 Meeting the checkability conditions is necessary for a usable handoff, not sufficient for good underlying work.

5. Failure modes as violated conditions

FailureViolated condition
"High confidence" with no evidence, scope or falsifier$\kappa$ incomplete: $E$, $S$ or $(k^\, r^\)$ empty
Falsifier tests an explanation of $f$, not $c$Falsifier target (§3)
Author marks own finding resolvedCondition 4
Next owner is the author, a collaborator or a teamConditions 5 and 6
Check needs the author's machine or private accessConditions 1 and 3
Lists only what was checkedCondition 2

6. Mapping to the unnamed prep rail

The course's Level 500 rail (500.rail-ai-assurance, defined in levels/500/objectives.yml) is a practice route toward an AI governance or management-system audit certification. Its structure is the course map's, not any cited source's. Under Bob's decision of 18 November 2026, its vendor and exam remain unnamed until he clears each name. No current exam alignment is claimed; the course supplies no vendor-proctored exam and no endorsement.

The rail draws on $O_R = \{$500.6-a, 500.7-b, 500.8-b, 500.9-d, 500.R-a, 500.R-b$\}$ and three practices: $\Pi = \{\pi_1$ produce a role-specific handoff, $\pi_2$ inspect a missing-evidence packet, $\pi_3$ route an unresolved finding to an independent owner$\}$. A learner's mapping is a relation

M \subseteq \text{Parts}(H) \times \Pi \times O_R

that must be total on $\Pi$ (every practice evidenced by some part) and must cite only objectives in $O_R$.

Part of $H$$\pi$Objective
$\mu(P)$, $\kappa$$\pi_1$500.R-a
$\Gamma$, $\bar\Gamma$, missing-proof list$\pi_2$500.6-a; 500.7-b
Clause → gate → evidence → owner rows$\pi_2$500.8-b
Tested/untested coverage; ruling by non-tester$\pi_3$500.9-d
$F$, $o$$\pi_3$500.R-a
$M$ itself, with $\sigma$ respected (§7)$\pi_1, \pi_2, \pi_3$500.R-b

7. Typing evidence relative to a claim

Subject is a property of an evidence item as used for a claim, not of the item alone. Define $\sigma(e, c) \in \{\text{person}, \text{system}\}$ by the subject of $c$. One item can carry both types: Morgan's ruling on F-1 (Card D) is person evidence for "Morgan can rule on findings" and system evidence for "F-1 was found and accepted on version 4".

Typing rule. A claim about a system's controls $c_{\text{sys}}$ may cite only $e$ with $\sigma(e, c_{\text{sys}}) = \text{system}$. Person evidence can raise confidence that an assessor will perform a check well; it cannot stand in for the check's result. An exam result is never typed $\text{system}$ for any $c_{\text{sys}}$.

Scope of system evidence. Typing is necessary, not sufficient. Each system item supports only a narrow inference, under stated assumptions:

$e$Supports, under assumptionsDoes not support
Signed record that verifiesIntegrity and origin: bytes unchanged since signing by a holder of the key, given an uncompromised key and a correct verifierThat the described event occurred; control effectiveness
Retest log on $v$Listed inputs logged as passing on $v$, given a complete and genuine logUnlisted inputs; other versions; independence of the retester
Ruled red-team findingA weakness existed and a person ruled on itAbsence of other weaknesses; overall readiness
Appeal and complaint recordsAn appeal route existed and was usedQuality of appeal outcomes; reachability for all users
Missing-evidence registerWhich required records are present or absentControl execution on unregistered cases

The AI RMF's structure respects the person/system split. GOVERN 2.2 concerns personnel and partners receiving AI risk management training to perform their duties (p. 23); MEASURE 1.3 and MEASURE 2.1 concern who assesses the system and how its testing is documented (p. 29).1 The trustworthiness characteristics (valid and reliable; safe; secure and resilient; accountable and transparent; explainable and interpretable; privacy-enhanced; fair with harmful bias managed) are characteristics of AI systems (p. 12).1

Consequences:

8. Exercises

  1. Write $\kappa$ for the reviewer disposition on Card G. Identify one item a careless reviewer would put in $E$ that fails the relevance test, and one check that is a resolution path for $f$ rather than a falsifier for $c$.
  2. On Card D, the red-team handoff names the original tester as $o$ for the retest. State which conditions fail and rewrite $o$.
  3. A mapping table cites a passed practice quiz as evidence that Big Widget's hiring assistant has working human review. Show where the typing rule is broken.

Further learning (not a citation)

Harvard CS 2881R (AI Safety, Fall 2025), Stanford CS 181/181W (Computers, Ethics, and Public Policy, Spring 2024) and Stanford CS25 (Transformers United V6) go deeper. They support no claim here and none of their material is copied. Links and caveats are in levels/500/universities.md.

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. 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. ↩ ↩ ↩
  5. 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. ↩ ↩ ↩ ↩
  6. 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. ↩ ↩

Next: the quiz