Skip to content
Clairos Learn

Prompt and configuration operations · Lesson 6 of 14 · 9 min

Review a prompt rollout

A canary rollout limits exposure while collecting comparable evidence. Decide promotion against predefined gates rather than the novelty of a new prompt.

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 canary rollout limits exposure while collecting comparable evidence. Decide promotion against predefined gates rather than the novelty of a new prompt.

Interpret the evidence

Keep or restore p7 because the canary has failed its quality gate.

A tempting mistake

Expand the failing canary to all requests to get more data.

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-prompts-config-006.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "candidate_share_percent": 5,
  "quality_gate_pass": false,
  "rollback": "p7"
}

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

$ jq .quality_gate_pass /opt/ai-lab/cases/aiops-prompts-config-006.json
false

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

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

Explain it

What does the evidence in “Review a prompt rollout” justify?

Apply it elsewhere

A colleague concludes: “Expand the failing canary to all requests to get more data.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Locate a prompt ownerTry 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. 01Compare prompt revisionsCompare prompt changes by meaning as well as line count. Removing an evidence requirement can weaken grounding even if the edited text is shorter and cleaner.Practice
  2. 02Locate a prompt ownerOwnership identifies who can explain, approve and roll back a prompt change. A named owner is useful only when the escalation and change process are recorded.Practice
  3. 03Inspect configuration precedenceConfiguration precedence decides which value is effective when several sources define a key. Read the documented order rather than assuming the nearest file always wins.Practice