AI systems foundations · Lesson 12 of 15 · 6 min

Define an operator signal

An operator signal names a quantity, unit and observation window. A bare latency number cannot support an incident claim until its aggregation and time range are clear.

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-012.json. Separate the recorded facts from your assumptions.
Hint & worked example
An operator signal names a quantity, unit and observation window. A bare latency number cannot support an incident claim until its aggregation and time range are clear.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-systems-foundations-012.json
```
Common mistake to avoid: Report that all requests take exactly 480 ms.
2
Isolate the deciding signal
Select the aggregation field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Record this as p95 latency of 480 ms over five minutes, not as every request taking 480 ms.
A successful JSON query isolates aggregation.
```
jq .aggregation /opt/ai-lab/cases/aiops-systems-foundations-012.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: record-window, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-systems-foundations-012-decision.txt.
Hint & worked example
Record this as p95 latency of 480 ms over five minutes, not as every request taking 480 ms.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'record-window' > /home/learner/lab/aiops-systems-foundations-012-decision.txt
```
Common mistake to avoid: Report that all requests take exactly 480 ms.

Understand the pattern

An operator signal names a quantity, unit and observation window. A bare latency number cannot support an incident claim until its aggregation and time range are clear.

Interpret the evidence

Record this as p95 latency of 480 ms over five minutes, not as every request taking 480 ms.

A tempting mistake

Report that all requests take exactly 480 ms.

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-012.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "value": 480,
  "unit": "milliseconds",
  "aggregation": "p95",
  "window": "last 5 minutes"
}

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

$ jq .aggregation /opt/ai-lab/cases/aiops-systems-foundations-012.json

"p95"

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

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

Explain it

What does the evidence in “Define an operator signal” justify?Record this as p95 latency of 480 ms over five minutes, not as every request taking 480 ms.Report that all requests take exactly 480 ms.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Report that all requests take exactly 480 ms.” 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: Use evidence before action 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