Prompt and configuration operations · Lesson 10 of 14 · 8 min

Detect configuration drift

Drift is a difference between intended and effective configuration. Confirm the effective runtime value before deciding whether the source or the deployment needs repair.

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-prompts-config-010.json. Separate the recorded facts from your assumptions.
Hint & worked example
Drift is a difference between intended and effective configuration. Confirm the effective runtime value before deciding whether the source or the deployment needs repair.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-prompts-config-010.json
```
Common mistake to avoid: Call source control the live truth without checking the process.
2
Isolate the deciding signal
Select the effective_prompt field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Investigate why runtime still uses p6 instead of the declared p7.
A successful JSON query isolates effective_prompt.
```
jq .effective_prompt /opt/ai-lab/cases/aiops-prompts-config-010.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: investigate-drift, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-prompts-config-010-decision.txt.
Hint & worked example
Investigate why runtime still uses p6 instead of the declared p7.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'investigate-drift' > /home/learner/lab/aiops-prompts-config-010-decision.txt
```
Common mistake to avoid: Call source control the live truth without checking the process.

Understand the pattern

Drift is a difference between intended and effective configuration. Confirm the effective runtime value before deciding whether the source or the deployment needs repair.

Interpret the evidence

Investigate why runtime still uses p6 instead of the declared p7.

A tempting mistake

Call source control the live truth without checking the process.

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-prompts-config-010.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "declared_prompt": "p7",
  "effective_prompt": "p6",
  "drift": true
}

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

$ jq .effective_prompt /opt/ai-lab/cases/aiops-prompts-config-010.json

"p6"

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

$ printf '%s\n' 'investigate-drift' > /home/learner/lab/aiops-prompts-config-010-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 “investigate-drift” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Detect configuration drift” justify?Call source control the live truth without checking the process.Make the change now and gather the missing evidence afterward.Investigate why runtime still uses p6 instead of the declared p7.

Apply it elsewhere

A colleague concludes: “Call source control the live truth without checking the process.” What should you do?Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.Accept it because the training command completed.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Prepare a prompt rollback 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