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

Name files predictably

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

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-cli-workspace-005.json. Separate the recorded facts from your assumptions.
Hint & worked example
Predictable 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.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-cli-workspace-005.json
```
Common mistake to avoid: Putting a secret in the filename is safe because file contents are redacted.
2
Isolate the deciding signal
Select the good_name field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Use the case identifier and artifact type, not a secret, in the filename.
A successful JSON query isolates good_name.
```
jq .good_name /opt/ai-lab/cases/aiops-cli-workspace-005.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: name-by-case, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-cli-workspace-005-decision.txt.
Hint & worked example
Use the case identifier and artifact type, not a secret, in the filename.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'name-by-case' > /home/learner/lab/aiops-cli-workspace-005-decision.txt
```
Common mistake to avoid: Putting a secret in the filename is safe because file contents are redacted.

Understand the pattern

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

Interpret the evidence

Use the case identifier and artifact type, not a secret, in the filename.

A tempting mistake

Putting a secret in the filename is safe because file contents are redacted.

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

{
  "fixture": "Fictional training data; not a live measurement.",
  "good_name": "latency-case-014.json",
  "bad_name": "api-token-example-secret.txt",
  "case_id": "014"
}

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

$ jq .good_name /opt/ai-lab/cases/aiops-cli-workspace-005.json

"latency-case-014.json"

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

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

Explain it

What does the evidence in “Name files predictably” justify?Make the change now and gather the missing evidence afterward.Use the case identifier and artifact type, not a secret, in the filename.Putting a secret in the filename is safe because file contents are redacted.

Apply it elsewhere

A colleague concludes: “Putting a secret in the filename is safe because file contents are redacted.” What should you do?Reject that conclusion; return to the case evidence and its stated limits.Accept it because the training command completed.Treat this fixture as a live measurement.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Compare a configuration copy 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