Serving, containers, and resources · Lesson 16 of 17 · 7 min

Prepare a rollout review

A rollout review combines the diff, compatibility, capacity, readiness and rollback. Explicitly record untested conditions rather than converting them into a pass.

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-serving-resources-016.json. Separate the recorded facts from your assumptions.
Hint & worked example
A rollout review combines the diff, compatibility, capacity, readiness and rollback. Explicitly record untested conditions rather than converting them into a pass.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-serving-resources-016.json
```
Common mistake to avoid: Capacity passing makes recovery planning unnecessary.
2
Isolate the deciding signal
Select the rollback_verified field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Verify the rollback before approving this rollout.
A successful JSON query isolates rollback_verified.
```
jq .rollback_verified /opt/ai-lab/cases/aiops-serving-resources-016.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: verify-rollout-rollback, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-serving-resources-016-decision.txt.
Hint & worked example
Verify the rollback before approving this rollout.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'verify-rollout-rollback' > /home/learner/lab/aiops-serving-resources-016-decision.txt
```
Common mistake to avoid: Capacity passing makes recovery planning unnecessary.

Understand the pattern

A rollout review combines the diff, compatibility, capacity, readiness and rollback. Explicitly record untested conditions rather than converting them into a pass.

Interpret the evidence

Verify the rollback before approving this rollout.

A tempting mistake

Capacity passing makes recovery planning unnecessary.

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-serving-resources-016.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "diff_reviewed": true,
  "capacity_pass": true,
  "rollback_verified": false
}

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

$ jq .rollback_verified /opt/ai-lab/cases/aiops-serving-resources-016.json

false

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

$ printf '%s\n' 'verify-rollout-rollback' > /home/learner/lab/aiops-serving-resources-016-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 “verify-rollout-rollback” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Prepare a rollout review” justify?Make the change now and gather the missing evidence afterward.Verify the rollback before approving this rollout.Capacity passing makes recovery planning unnecessary.

Apply it elsewhere

A colleague concludes: “Capacity passing makes recovery planning unnecessary.” 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: Serving and resources checkpoint 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