Skip to content
Clairos Learn

Models, artifacts, and runtimes · Lesson 13 of 16 · 9 min

Choose a rollback artifact

A rollback artifact should be known-good, retained and compatible with the current runtime and configuration. The oldest available file is not automatically a safe rollback.

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

A rollback artifact should be known-good, retained and compatible with the current runtime and configuration. The oldest available file is not automatically a safe rollback.

Interpret the evidence

Retain m2 with its verified checksum and compatible configuration as the rollback candidate.

A tempting mistake

Delete the verified version as soon as a candidate loads.

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-models-runtimes-013.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "candidate": "m2",
  "previously_verified": true,
  "runtime_compatible": true,
  "checksum_verified": true
}

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

$ jq .previously_verified /opt/ai-lab/cases/aiops-models-runtimes-013.json
true

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

$ printf '%s\n' 'retain-verified-m2' > /home/learner/lab/aiops-models-runtimes-013-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 “retain-verified-m2” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Choose a rollback artifact” justify?

Apply it elsewhere

A colleague concludes: “Delete the verified version as soon as a candidate loads.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Review model provenanceTry 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. 01Spot a runtime mismatchMismatch diagnosis starts with explicit compatibility evidence. When a runtime rejects an architecture, changing prompt text cannot repair the loader contract.Practice
  2. 02Review model provenanceProvenance connects an artifact to its source, license and revision. Preserve that chain alongside the hash so another operator can explain what was activated.Practice
  3. 03Build a model baselineA serving baseline includes model, tokenizer, runtime, quantization and workload. Record these together before tuning so changes can be attributed rather than guessed.Practice