Safety, privacy, and governance · Lesson 13 of 15 · 6 min

Prepare a governance review

Governance review checks intended use, data permission, access, retention, testing and ownership together. Mark missing evidence explicitly rather than assuming it exists.

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-013.json. Separate the recorded facts from your assumptions.
Hint & worked example
Governance review checks intended use, data permission, access, retention, testing and ownership together. Mark missing evidence explicitly rather than assuming it exists.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-safety-governance-013.json
```
Common mistake to avoid: An assigned owner makes every untested control a pass.
2
Isolate the deciding signal
Select the retention_tested field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Complete the missing retention test before declaring the review complete.
A successful JSON query isolates retention_tested.
```
jq .retention_tested /opt/ai-lab/cases/aiops-safety-governance-013.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: test-retention, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-safety-governance-013-decision.txt.
Hint & worked example
Complete the missing retention test before declaring the review complete.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'test-retention' > /home/learner/lab/aiops-safety-governance-013-decision.txt
```
Common mistake to avoid: An assigned owner makes every untested control a pass.

Understand the pattern

Governance review checks intended use, data permission, access, retention, testing and ownership together. Mark missing evidence explicitly rather than assuming it exists.

Interpret the evidence

Complete the missing retention test before declaring the review complete.

A tempting mistake

An assigned owner makes every untested control a pass.

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-013.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "use_reviewed": true,
  "data_permission": true,
  "retention_tested": false,
  "owner": "ops-team"
}

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

$ jq .retention_tested /opt/ai-lab/cases/aiops-safety-governance-013.json

false

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

$ printf '%s\n' 'test-retention' > /home/learner/lab/aiops-safety-governance-013-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 “test-retention” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Prepare a governance review” justify?An assigned owner makes every untested control a pass.Make the change now and gather the missing evidence afterward.Complete the missing retention test before declaring the review complete.

Apply it elsewhere

A colleague concludes: “An assigned owner makes every untested control a pass.” What should you do?Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.Accept it because the training command completed.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Write a risk summary 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