AI systems foundations · Lesson 3 of 15 · 7 min

Trace a request lifecycle

A request lifecycle has separate waiting, retrieval, inference and validation stages. Compare durations within the same request rather than combining unrelated log lines.

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-systems-foundations-003.json. Separate the recorded facts from your assumptions.
Hint & worked example
A request lifecycle has separate waiting, retrieval, inference and validation stages. Compare durations within the same request rather than combining unrelated log lines.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-systems-foundations-003.json
```
Common mistake to avoid: Tune inference first because the model is always the slowest stage.
2
Isolate the deciding signal
Select the retrieval_ms field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Investigate the 760 ms retrieval stage, the largest measured contributor.
A successful JSON query isolates retrieval_ms.
```
jq .retrieval_ms /opt/ai-lab/cases/aiops-systems-foundations-003.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-retrieval-span, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-systems-foundations-003-decision.txt.
Hint & worked example
Investigate the 760 ms retrieval stage, the largest measured contributor.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'inspect-retrieval-span' > /home/learner/lab/aiops-systems-foundations-003-decision.txt
```
Common mistake to avoid: Tune inference first because the model is always the slowest stage.

Understand the pattern

A request lifecycle has separate waiting, retrieval, inference and validation stages. Compare durations within the same request rather than combining unrelated log lines.

Interpret the evidence

Investigate the 760 ms retrieval stage, the largest measured contributor.

A tempting mistake

Tune inference first because the model is always the slowest stage.

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-systems-foundations-003.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "request_id": "req-014",
  "queue_ms": 40,
  "retrieval_ms": 760,
  "inference_ms": 210
}

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

$ jq .retrieval_ms /opt/ai-lab/cases/aiops-systems-foundations-003.json

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

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

Explain it

What does the evidence in “Trace a request lifecycle” justify?Investigate the 760 ms retrieval stage, the largest measured contributor.Tune inference first because the model is always the slowest stage.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Tune inference first because the model is always the slowest stage.” 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: Name the serving boundary 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