Skip to content
Clairos Learn

Safety, privacy, and governance · Lesson 11 of 15 · 9 min

Check audit metadata

Audit metadata should record what changed, who authorized it and which versions were involved. Avoid collecting raw secrets simply to make an audit record look complete.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Audit metadata should record what changed, who authorized it and which versions were involved. Avoid collecting raw secrets simply to make an audit record look complete.

Interpret the evidence

Retain the authorization and version trail without adding secret values.

A tempting mistake

An audit is incomplete unless it stores all credentials.

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-011.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "actor": "reviewer-3",
  "change": "policy-v4",
  "authorization_recorded": true,
  "secret_values_recorded": false
}

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

$ jq .authorization_recorded /opt/ai-lab/cases/aiops-safety-governance-011.json
true

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

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

Explain it

What does the evidence in “Check audit metadata” justify?

Apply it elsewhere

A colleague concludes: “An audit is incomplete unless it stores all credentials.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Separate safety and qualityTry 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

  1. 01Review human escalationHuman escalation needs an identified recipient, a bounded reason and a safe hold state. A vague “ask someone” message is not an operational handoff.Practice
  2. 02Separate safety and qualitySafety and task quality are separate evaluation dimensions. A useful answer can violate a data boundary, while a safe refusal can still be unhelpful for an allowed request.Practice
  3. 03Prepare a governance reviewGovernance review checks intended use, data permission, access, retention, testing and ownership together. Mark missing evidence explicitly rather than assuming it exists.Practice