Skip to content
Clairos Learn

Safety, privacy, and governance · Lesson 12 of 15 · 5 min

Separate safety and quality

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

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

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

Interpret the evidence

Hold the result despite its quality pass because the privacy boundary failed.

A tempting mistake

A useful answer cancels a privacy failure.

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-012.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "task_quality": "pass",
  "privacy_boundary": "fail"
}

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

$ jq .privacy_boundary /opt/ai-lab/cases/aiops-safety-governance-012.json
"fail"

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

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

Explain it

What does the evidence in “Separate safety and quality” justify?

Apply it elsewhere

A colleague concludes: “A useful answer cancels a privacy failure.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Prepare a governance reviewTry 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. 01Check audit metadataAudit 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.Practice
  2. 02Prepare 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
  3. 03Write a risk summaryA risk summary should describe the failure, affected boundary, mitigation and residual uncertainty. Do not promise zero risk from a finite set of checks.Practice