Cost, capacity, and reliability · Lesson 13 of 14 · 6 min

Review cost anomalies

Cost anomalies require separating request volume, token length, model selection and retries. Compare those drivers before treating an invoice increase as a provider error.

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-cost-reliability-013.json. Separate the recorded facts from your assumptions.
Hint & worked example
Cost anomalies require separating request volume, token length, model selection and retries. Compare those drivers before treating an invoice increase as a provider error.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-cost-reliability-013.json
```
Common mistake to avoid: Blame retry storms even though the retry rate did not change.
2
Isolate the deciding signal
Select the input_tokens_change_percent field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Investigate input-context growth as the changed cost driver.
A successful JSON query isolates input_tokens_change_percent.
```
jq .input_tokens_change_percent /opt/ai-lab/cases/aiops-cost-reliability-013.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: inspect-context-cost, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-cost-reliability-013-decision.txt.
Hint & worked example
Investigate input-context growth as the changed cost driver.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'inspect-context-cost' > /home/learner/lab/aiops-cost-reliability-013-decision.txt
```
Common mistake to avoid: Blame retry storms even though the retry rate did not change.

Understand the pattern

Cost anomalies require separating request volume, token length, model selection and retries. Compare those drivers before treating an invoice increase as a provider error.

Interpret the evidence

Investigate input-context growth as the changed cost driver.

A tempting mistake

Blame retry storms even though the retry rate did not change.

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-cost-reliability-013.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "requests_change_percent": 0,
  "input_tokens_change_percent": 200,
  "output_tokens_change_percent": 0,
  "retry_change_percent": 0
}

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

$ jq .input_tokens_change_percent /opt/ai-lab/cases/aiops-cost-reliability-013.json

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

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

Explain it

What does the evidence in “Review cost anomalies” justify?Investigate input-context growth as the changed cost driver.Blame retry storms even though the retry rate did not change.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Blame retry storms even though the retry rate did not change.” What should you do?Accept it because the training command completed.Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Cost and reliability 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