Skip to content
Clairos Learn

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

List prompt versions

A prompt registry separates the active revision from drafts and rollback candidates. A listed draft should not receive traffic until its rollout is deliberate.

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 prompt registry separates the active revision from drafts and rollback candidates. A listed draft should not receive traffic until its rollout is deliberate.

Interpret the evidence

Treat p7 as active while p8 remains a candidate.

A tempting mistake

The latest listed revision automatically becomes active.

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-001.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "active_revision": "p7",
  "draft_revision": "p8",
  "rollback_revision": "p6"
}

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

$ jq .active_revision /opt/ai-lab/cases/aiops-prompts-config-001.json
"p7"

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

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

Explain it

What does the evidence in “List prompt versions” justify?

Apply it elsewhere

A colleague concludes: “The latest listed revision automatically becomes active.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Inspect a prompt manifestTry 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. 01Inspect a prompt manifestA prompt manifest records ownership, variables and intended use. Missing metadata makes future evaluation and rollback harder even when the prompt text itself is readable.Practice
  2. 02Separate system and user inputTrusted application instructions and untrusted user input belong in distinct roles. Quoted user text should not gain authority merely because it resembles an instruction.Practice
  3. 03Validate prompt variablesPrompt-variable validation catches missing substitutions before inference. An unresolved placeholder is a configuration defect, not useful context for the model to guess.Practice