Skip to content
Clairos Learn

AI systems foundations · Lesson 4 of 15 · 8 min

Name the serving boundary

A serving boundary defines which process accepts inference requests and which dependencies it calls. A loopback listener is not evidence that a service is publicly reachable.

Open the labCourse map
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 serving boundary defines which process accepts inference requests and which dependencies it calls. A loopback listener is not evidence that a service is publicly reachable.

Interpret the evidence

Treat this gateway as loopback-only; a public route has not been configured.

A tempting mistake

Tell users to connect to the loopback address from another computer.

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-004.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "listener": "127.0.0.1:8080",
  "public_proxy": "not_configured",
  "runtime_port": 8090
}

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

$ jq .listener /opt/ai-lab/cases/aiops-systems-foundations-004.json
"127.0.0.1:8080"

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

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

Explain it

What does the evidence in “Name the serving boundary” justify?

Apply it elsewhere

A colleague concludes: “Tell users to connect to the loopback address from another computer.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Read an inference contractTry 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. 01Trace a request lifecycleA request lifecycle has separate waiting, retrieval, inference and validation stages. Compare durations within the same request rather than combining unrelated log lines.Practice
  2. 02Read an inference contractAn inference contract specifies required fields, supported model identifiers and response shape. Validate the request before blaming a model for a rejected envelope.Practice
  3. 03Distinguish training and inferenceTraining updates learned parameters; inference uses a selected artifact to generate output. Generation settings can change inference behavior without changing the weights.Practice

Case methodology: evidence, limits, decision