Skip to content
Clairos Learn

Models, artifacts, and runtimes · Lesson 12 of 16 · 8 min

Spot a runtime mismatch

Mismatch diagnosis starts with explicit compatibility evidence. When a runtime rejects an architecture, changing prompt text cannot repair the loader contract.

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

Mismatch diagnosis starts with explicit compatibility evidence. When a runtime rejects an architecture, changing prompt text cannot repair the loader contract.

Interpret the evidence

Use a compatible runtime or artifact; the failure occurs before prompt execution.

A tempting mistake

Rewrite the prompt to fix the artifact loader.

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-012.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "loader_error": "architecture decoder-b not supported",
  "prompt_valid": true
}

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

$ jq .loader_error /opt/ai-lab/cases/aiops-models-runtimes-012.json
"architecture decoder-b not supported"

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

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

Explain it

What does the evidence in “Spot a runtime mismatch” justify?

Apply it elsewhere

A colleague concludes: “Rewrite the prompt to fix the artifact loader.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Choose a rollback artifactTry 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. 01Inspect accelerator availabilityAccelerator availability has several layers: device visibility, driver/runtime support and free memory. A visible GPU does not prove that the model runtime can use it.Practice
  2. 02Choose a rollback artifactA 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.Practice
  3. 03Review 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