Observe
Version your prompts. Roll back in one step.
Keep prompts in one place with fixed versions and moving labels, so you know which prompt every trace used.
Versions
Never edited- v15Tighten refund wordingstaging
- v14Add order lookupprod
- v13First review rule
Move a label
- Eval run 41 passes
- Move prod to v15
- Traces show v15
Used by
- Traces
- 1,820 on v14
- Agents
- refund-agent
Why it matters
What prompt registry changes
- Keep prompts in one place.
- Versions are fixed and labels can move.
- Every trace records the prompt it used.
- Prompts live in code, docs and people's heads.
- Nobody knows which version a trace used.
- Rolling back means digging.
The resultKnow which prompt did what.
What you get
Prompt registry, in practice
Versions never change
Edit a prompt and you get a new version. Old ones stay exactly as they were.
Labels you can move
Point production at version 7, or back to 6. Every move is logged.
Linked to traces
See which prompt version was behind any run, and how it scored.
How it works
Step by step
- 1
Write a prompt
Saved as version 1.
- 2
Change it
Saved as version 2.
- 3
Move the label
Production now uses 2.
- 4
Roll back
If scores drop, point back at 1.
Questions
About prompt registry
How does my agent read a prompt?
By name and label or version, for example support-reply@production.
Is the history kept?
Yes. Versions are immutable and label moves are written to the audit log.
Next
Works well with
Know what your agents did.
Start free. Guard your first agent in a few minutes, and keep a record anyone can check.
- Free plan, no card
- Signed, chained decisions
- Checked offline, without us
Signed decision
- Decision
- Approved, 2 of 2
- Action
- refund.issue, £540
- Rule
- Two reviewers must agree
- Sealed
- 14:09, key 7f2c
- Hash
- 5be2…7c44
Checked on your own machine
- Signature matches the public key
- Decision is in the log
- Every link before it adds up