Evidence-led AI operations · approximately 6 minutes · no timer

A model is ready. The app is not.

Read /opt/ai-lab/incident.json. Identify the failing dependency and save its name followed by a newline in /home/learner/lab/dependency.txt. Model readiness alone does not explain application health.

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your recovery goal

The artifact identifies the failing dependency, based on the synthetic incident report.

Investigation in progress.

Show a recovery path

Use this as a worked example, not the only accepted command sequence.

cat /opt/ai-lab/incident.json
jq -r .failing_dependency /opt/ai-lab/incident.json > /home/learner/lab/dependency.txt

Two stars for resolution; a third for diagnostic evidence. Practice rewards are session-only when signed out and device-local when signed in.

What did the evidence establish?

Separate the failing condition from your explanation of its cause. After a repair, verify the result at the layer the user actually depends on. A changed file, successful syntax check, running process, and successful request prove different things.

Choose another incident Return to the curriculum