For teams running voice or chat agents in production

You approved the prompt.Is that what’s actually running?

Prompts get edited straight in the platform console — a quick fix, a reworded line, a guardrail quietly dropped — and your repo never hears about it. This vault registers the versions you approved and hashes what’s live in each agent, so you can see at a glance which ones drifted, and which are running a prompt nobody signed off on.

Get the Vault — $59one-time · runs offline · connects to nothing
Five deliverables · runnable
Runnable Python register + scan
stdlib
Workbook that reproduces it
xlsx
Drift-scan export
csv
Vaulting playbook
docx
Drift-response runbook
docx
Governance layer for
Voice Prompt Forge · Canary Call Library · Prompt Regression Lab
01.The Problem

The guardrails you certified can vanish in production.

console edit
a prompt changed in the platform UI that never went through your pipeline
pinned ≠ live
an agent pinned to v1.1 quietly running v1.0 — a real version, the wrong one
1 shadow
one unapproved prompt live turns the whole fleet red
02.See It Work

Strip a guardrail in the console. Watch the vault flag the shadow.

4 live agents vs 2 approved versions
front-desk-Apinned dental-v1.1
IN SYNC
front-desk-Bpinned dental-v1.1 · running dental-v1.0
DRIFTED
overflow-Dpinned dental-v1.0
IN SYNC
after-hours-Cpinned dental-v1.1 · matches no approved versionconsole-edited
UNKNOWN VERSION
2 in sync · 1 drifted · 1 unknownSHADOW PROMPTS LIVE

front-desk-B is the quieter failure: it’s pinned to v1.1 but actually running v1.0 — a real approved version, just not the one it’s supposed to be on. That’s DRIFTED, not a shadow, and the vault names exactly which version it landed on.

03.The Runnable Scanner

Register once. Scan your live fleet against it any time.

A zero-dependency Python tool registers your approved prompts and scans a live export against them by content hash. Here is its actual scan output on the shipped four-agent sample — two in sync, one drifted, one shadow:

PROMPT VERSION VAULT - DRIFT SCAN
====================================================

PER-AGENT (live prompt vs registry)
----------------------------------------------------
front-desk-A       IN SYNC          matches pinned dental-v1.1
    live hash 1265c78451fb
front-desk-B       DRIFTED          pinned dental-v1.1, running dental-v1.0
    live hash f19c9463c92c
after-hours-C      UNKNOWN VERSION  matches no approved version
    live hash 1865eb8f2e16
overflow-D         IN SYNC          matches pinned dental-v1.0
    live hash f19c9463c92c

ROLLUP
----------------------------------------------------
Agents scanned ........... 4
In sync .................. 2
Drifted .................. 1
Unknown version .......... 1
Fix first ................ after-hours-C

VERDICT: SHADOW PROMPTS LIVE

Hashes text you export; it connects to nothing and grades no person.
Not legal advice.
04.The Standard

Three things the vault holds your fleet to.

Approved isn’t the same as running

You can approve a prompt, ship it, and still have someone tweak it in the platform console a week later. Your repo says one thing; production says another. Only comparing the live prompt to your registry reveals the gap.

A shadow prompt is the worst case

A live prompt that matches no approved version was edited outside your process — the safety blocks you certified may be gone, and no one signed off. One shadow prompt forces the whole fleet to SHADOW PROMPTS LIVE.

Cosmetic changes aren’t drift

The vault normalizes trailing spaces, blank-line runs, and indentation before hashing, so a reformatted prompt reads IN SYNC. A real wording change reads as drift. You get signal, not formatting noise.

05.What This Is — And Isn’t

A provenance check. Not an eval framework, not a text differ.

It is
  • A registry of your approved prompt versions, by content hash.
  • A drift scanner: live vs approved, per agent.
  • Shadow-prompt aware — it catches the unapproved console edit.
  • Offline — it hashes an export you provide and connects to nothing.
It isn’t
  • An eval framework or a versioning war-room — that’s the Prompt Eval System.
  • A prompt-text diff — that’s the Prompt Regression Lab.
  • A live platform connection — it scans what you export.
  • A judge of people — it hashes text, grades no one.

Scope note. The vault hashes prompt text you export and compares it to a registry you build; it connects to no platform, changes no agent, and grades no person. A match confirms the text is identical to an approved version — it is not a review of whether that version is correct or compliant. Not legal advice.

06.Who It’s For

Anyone accountable for what a fleet of agents actually says.

Agencies running voice or chat agents across many client sub-accounts
Teams where more than one person can edit a live prompt
Operators who need to prove an approved prompt is the one in production
Anyone who found a guardrail missing and couldn’t say when it left
08.Common Questions

The parts worth pinning down before you buy.

That's an eval framework and a versioning war-room — it helps you score prompt quality and organize your workflow. This is a narrower, sharper thing: a provenance check. It answers one question — is the prompt actually running in each live agent the one you approved, or has it drifted, or is it a version nobody signed off on? It's the governance layer that catches an unapproved edit in production, not a place to manage prompt development.

Know which prompt is live.
On every agent. Right now.

Register what you approved and scan what’s running, so a shadow prompt can’t hide in your fleet. One purchase, lifetime access, 12 months of updates. $59, once.

Sold by RedHub AI LLC · Secured by Stripe · redhub.ai