Safety, privacy, and governance · Lesson 14 of 15 · 7 min

Write a risk summary

A risk summary should describe the failure, affected boundary, mitigation and residual uncertainty. Do not promise zero risk from a finite set of checks.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read the case evidence
Read /opt/ai-lab/cases/aiops-safety-governance-014.json. Separate the recorded facts from your assumptions.
Hint & worked example
A risk summary should describe the failure, affected boundary, mitigation and residual uncertainty. Do not promise zero risk from a finite set of checks.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-safety-governance-014.json
```
Common mistake to avoid: The mitigation label proves the risk is zero.
2
Isolate the deciding signal
Select the residual_tests_pending field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Record the pending tests and residual risk alongside the filter mitigation.
A successful JSON query isolates residual_tests_pending.
```
jq .residual_tests_pending /opt/ai-lab/cases/aiops-safety-governance-014.json
```
Common mistake to avoid: Using a different case or an unrelated signal as the justification.
3
Record your operational decision
Choose the justified code: record-residual-risk, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-safety-governance-014-decision.txt.
Hint & worked example
Record the pending tests and residual risk alongside the filter mitigation.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'record-residual-risk' > /home/learner/lab/aiops-safety-governance-014-decision.txt
```
Common mistake to avoid: The mitigation label proves the risk is zero.

Understand the pattern

A risk summary should describe the failure, affected boundary, mitigation and residual uncertainty. Do not promise zero risk from a finite set of checks.

Interpret the evidence

Record the pending tests and residual risk alongside the filter mitigation.

A tempting mistake

The mitigation label proves the risk is zero.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result

$ cat /opt/ai-lab/cases/aiops-safety-governance-014.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "risk": "cross-tenant retrieval",
  "mitigation": "tenant filter validation",
  "residual_tests_pending": true
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .residual_tests_pending /opt/ai-lab/cases/aiops-safety-governance-014.json

true

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'record-residual-risk' > /home/learner/lab/aiops-safety-governance-014-decision.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “record-residual-risk” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Write a risk summary” justify?Make the change now and gather the missing evidence afterward.Record the pending tests and residual risk alongside the filter mitigation.The mitigation label proves the risk is zero.

Apply it elsewhere

A colleague concludes: “The mitigation label proves the risk is zero.” What should you do?Reject that conclusion; return to the case evidence and its stated limits.Accept it because the training command completed.Treat this fixture as a live measurement.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Safety and governance checkpoint Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

Case methodology: evidence, limits, decision