Skip to content
Clairos Learn

CLI and workspace hygiene · Lesson 6 of 12 · 5 min

Compare a configuration copy

Compare the intended configuration with the candidate before activation. A one-line change can still alter behavior substantially, so read the value and its context.

Open the labCourse map
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

Compare the intended configuration with the candidate before activation. A one-line change can still alter behavior substantially, so read the value and its context.

Interpret the evidence

Review the tenfold timeout reduction before deploying the candidate.

A tempting mistake

Call the change harmless because only one line differs.

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-006.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "baseline_timeout_ms": 800,
  "candidate_timeout_ms": 80,
  "changed_key": "timeout_ms"
}

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

$ jq .candidate_timeout_ms /opt/ai-lab/cases/aiops-cli-workspace-006.json
80

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

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

Explain it

What does the evidence in “Compare a configuration copy” justify?

Apply it elsewhere

A colleague concludes: “Call the change harmless because only one line differs.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Search without exposing secretsTry 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. 01Name files predictablyPredictable filenames let another operator relate a note to a case and version. Names should describe what was captured without embedding secrets or sensitive user content.Practice
  2. 02Search without exposing secretsSearching logs should minimize unnecessary disclosure. Select the needed fields and redact credentials before sharing an evidence bundle.Practice
  3. 03Capture 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

Case methodology: evidence, limits, decision