Skip to content
Clairos Learn

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

Compare model versions

A version comparison must hold the task and evaluation inputs constant. A better aggregate result from another dataset is not a controlled improvement over the current model.

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 version comparison must hold the task and evaluation inputs constant. A better aggregate result from another dataset is not a controlled improvement over the current model.

Interpret the evidence

Rerun both artifacts on the same held-out dataset before comparing quality.

A tempting mistake

Promote m4 from scores measured on different datasets.

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-003.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "baseline_model": "m3",
  "candidate_model": "m4",
  "same_dataset": false
}

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

$ jq .same_dataset /opt/ai-lab/cases/aiops-models-runtimes-003.json
false

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

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

Explain it

What does the evidence in “Compare model versions” justify?

Apply it elsewhere

A colleague concludes: “Promote m4 from scores measured on different datasets.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Inspect artifact metadataTry 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 a model manifestA manifest records an artifact contract: format, architecture, tokenizer and context assumptions. Read the manifest before selecting a runtime or an inference envelope.Practice
  2. 02Inspect artifact metadataArtifact metadata explains what was downloaded or built. Format, size and quantization are useful checks, but an artifact name alone is not a provenance guarantee.Practice
  3. 03Verify an artifact checksumChecksums detect byte differences relative to a reference. The reference must itself be trusted, and a mismatch should stop activation until its cause is understood.Practice