Skip to content
Clairos Learn

CLI and workspace hygiene · Lesson 9 of 12 · 8 min

Build an evidence directory

An evidence directory should group related observations and leave source artifacts unchanged. A directory name can carry a case ID while each file names one type of evidence.

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

An evidence directory should group related observations and leave source artifacts unchanged. A directory name can carry a case ID while each file names one type of evidence.

Interpret the evidence

Keep the manifest, trace and decision together under the case directory.

A tempting mistake

Mix this case with unrelated files and omit the decision note.

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-cli-workspace-009.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "directory": "lab/case-014",
  "files": [
    "manifest.json",
    "trace.txt",
    "decision.txt"
  ],
  "source_changed": false
}

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

$ jq .files /opt/ai-lab/cases/aiops-cli-workspace-009.json
[
  "manifest.json",
  "trace.txt",
  "decision.txt"
]

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

$ printf '%s\n' 'keep-bundle-together' > /home/learner/lab/aiops-cli-workspace-009-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 “keep-bundle-together” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Build an evidence directory” justify?

Apply it elsewhere

A colleague concludes: “Mix this case with unrelated files and omit the decision note.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Verify a manifest checksumTry 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. 01Capture bounded command outputBound captured output by relevant scope, not by silently discarding inconvenient evidence. A short recent log window is useful when its limits are recorded in the note.Practice
  2. 02Verify a manifest checksumA checksum tests byte identity against a trusted expected value. Matching hashes do not by themselves establish the safety or provenance of the expected artifact.Practice
  3. 03Write an operator noteA useful operator note distinguishes observation, interpretation and next action. Include identifiers and limits so the next person can reproduce the investigation.Practice