Skip to content
Clairos Learn

Incident response and capstones · Lesson 4 of 12 · 6 min

Review a prompt rollout incident

A prompt incident can appear as a semantic regression rather than a process crash. Compare revisions and evaluation evidence while preserving a known-good 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 prompt incident can appear as a semantic regression rather than a process crash. Compare revisions and evaluation evidence while preserving a known-good rollback.

Interpret the evidence

Review rollback to p7 while preserving p8 failure examples for diagnosis.

A tempting mistake

Increase exposure to p8 because the process remains healthy.

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-incidents-capstones-004.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "prompt_before": "p7",
  "prompt_after": "p8",
  "unsupported_claims_before": 1,
  "unsupported_claims_after": 9,
  "rollback_available": true
}

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

$ jq .unsupported_claims_after /opt/ai-lab/cases/aiops-incidents-capstones-004.json
9

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

$ printf '%s\n' 'rollback-prompt-candidate' > /home/learner/lab/aiops-incidents-capstones-004-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 “rollback-prompt-candidate” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Review a prompt rollout incident” justify?

Apply it elsewhere

A colleague concludes: “Increase exposure to p8 because the process remains healthy.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Investigate GPU pressureTry 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. 01Diagnose retrieval regressionA retrieval regression should be compared against corpus, embedding, filters and index revisions. Find the changed boundary before tuning unrelated generation settings.Practice
  2. 02Investigate GPU pressureGPU pressure diagnosis separates weights, KV cache, concurrent requests and other processes. Reducing a measured source of memory demand is safer than guessing at arbitrary flags.Practice
  3. 03Trace a cost spikeA cost spike should be explained with comparable units and a measured driver. Increased retries can multiply work even when successful request counts remain flat.Practice