All courses / AI Blue / Module 3 / Chapter 14
Learning objectives
After the lesson the participant can:
- Explain the three forms of dependence and why automation bias makes designed verification necessary
- Apply the six soundness criteria to a triage verdict, a timeline and a containment proposal
- Design a seeded-incident programme with a catch-rate threshold and a stop rule
- Interpret a set of oversight-quality metrics and propose measures that keep review real at volume
Key concepts
- Soundness criteria
- Six criteria defined before the conclusion arrives: grounding, completeness, alternatives considered, stated confidence, reversibility and stability. They belong in the mandate manifest and the closure policy so the pipeline rejects output that fails them.
- Key fact
- The one fact on which a conclusion depends. The reviewer reproduces it by a route the AI did not take, re-running the query by hand or confirming it from a second source the adversary could not have altered.
- Critique agent
- A second AI that reads the evidence and the first agent's conclusion and flags unsupported claims and missing alternatives. It runs on a different model family, raises questions and never gives an approval.
- Caught-seed rate
- Seeded faults caught over seeded faults injected, read with its counts. The programme starts with a threshold of 0.80 over a rolling quarter; below it, extension of delegation for the class is frozen.
- Back-pressure
- When a reviewer's cap of open proposals is reached, 12 by default, a Level 2 class drops to Level 1: the agent keeps summarising but stops proposing until the queue clears. Pressure goes to the agent, not the person.
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
Soundness of a triage verdict
Match each soundness criterion with what the chapter requires of a triage verdict under it.
Interactive exercise 2 · Scenario
The cap is reached at night
Apply the chapter's measures for keeping review real at volume.
Teaching plan
| 15 min | Teacher opens with the night-shift analyst at the Polish service centre and names the three dependencies and the control each calls for. |
| 15 min | Soundness drill: groups score a prepared AI summary and containment proposal against the six criteria and decide whether the pipeline should have rejected it. |
| 15 min | Practice of the review order: participants write a provisional verdict and the fact that would change it before opening the agent's summary. |
| 40 min | Exercise: groups design a seeded-incident programme for one alert class following the eight steps of the practical guide. |
| 20 min | Reading of the oversight report OQM-HM-SOC-01 for 2027-Q3: what was met, what was missed and why the report is deliberately not a clean pass. |
Discussion
- A model's stated confidence is part of its output and not a measurement of its accuracy. What should a reviewer accept as a basis for confidence instead?
- With five seeds in a month a single miss moves the monthly rate by 0.20. How should small numbers be reported so that nobody reads more into them than they hold?
- The chapter places accountability for a missed closure first with those who designed the review and then with the person who approved. What would your organisation need to record to make that distinction visible?
Written exercise
Exercise · 40 minutes
Starting a seeded-incident programme
Follow the practical guide for one class that AI handles at Level 2 or Level 3 in your SOC, or for Hansa Mutual's closure classes. Name the SOC lead as owner and a seed owner who does not review seeded cases. Write the reporting rules to agree with employee representatives: team and class level only, no individual figures, no use in appraisal or discipline. Specify the first ten seeds as six seeded errors in AI summaries and four seeded incidents, the injection of five a month at random times, the registry tag and the no-action path. Define the outcomes to record, the rolling-quarter catch rate, the threshold of 0.80 and the stop rule, and how misses are analysed as design questions.
Deliverable: A programme specification with roles, agreed reporting rules, ten seed descriptions, injection plan, catch-rate threshold, stop rule and miss-analysis procedure.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
What is the cheapest correction for anchoring, the strongest effect of automation bias, according to the chapter?
Show the answer
D. Changing the order of work: the analyst forms a provisional view before opening the AI's conclusion
The reviewer who reads the conclusion first sees the evidence through it. The analyst therefore opens the raw alert, writes a provisional verdict and the fact that would change it, and only then opens the summary.Why does the critique agent run on a different model family from the agent it critiques?
Show the answer
A. Because agents on one model family may share blind spots and fail together
The design choice draws on the correlated-failure argument: a second opinion from the same model family may repeat the first agent's mistake. The critique agent stays read-only and never approves.In Hansa Mutual's oversight report for the third quarter of 2027, how does a reader learn that the caught-seed rate of 0.86 is fragile?
Show the answer
B. The report notes beside the figure that two more misses would breach it
With 28 seeds, 24 caught gives 0.86, but 22 of 28 is 0.79. The report states this beside the figure and also says that the reproduction rate and unassisted share missed their targets.