Skip to content
Clairos Learn

CLI and workspace hygiene · Lesson 3 of 12 · 7 min

Inspect redacted environment data

Redacted configuration proves which keys are present without revealing their values. A redaction marker is not a credential and should not be pasted into an authentication 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

Redacted configuration proves which keys are present without revealing their values. A redaction marker is not a credential and should not be pasted into an authentication request.

Interpret the evidence

Keep the token redacted; the marker only tells you that a secret field exists.

A tempting mistake

Use [REDACTED] as a real API credential.

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-003.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "API_TOKEN": "[REDACTED]",
  "MODEL_ID": "assistant-stable",
  "safe_to_publish": [
    "MODEL_ID"
  ]
}

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

$ jq .API_TOKEN /opt/ai-lab/cases/aiops-cli-workspace-003.json
"[REDACTED]"

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

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

Explain it

What does the evidence in “Inspect redacted environment data” justify?

Apply it elsewhere

A colleague concludes: “Use [REDACTED] as a real API credential.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Protect local configurationTry 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. 01Read the workspace layoutA workspace separates source artifacts, mutable scratch and generated reports. Make experiments in scratch so an investigation does not overwrite the baseline it is meant to compare.Practice
  2. 02Protect local configurationConfiguration containing credentials needs an appropriate local permission boundary. In this exercise mode 600 gives the owner read/write access and no group or other access.Practice
  3. 03Name 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