Bundle, Promote & Rollback

A sales qualification agent flows through dev, staging, and prod. One threshold change floods the pipeline — instant rollback with full audit trail.

💰

The Scenario

A B2B SaaS sales team manages their lead qualification agent. It scores leads and routes them to reps or automated nurture flows.

Inbound Lead "We're a 30-person startup looking at your enterprise plan"
v1.0.0
Route to nurture
Rule: qualify $50K+ ARR potential
vs
v1.1.0
Route to sales rep
Rule: qualify $25K+ ARR potential
v1.0.0 Qualify $50K+ ARR v1.1.0 Qualify $25K+ ARR
1.0x
🔒

The Key Moment: Hash Verification

The SHA-256 hash of the bundle in prod is identical to what was created in dev. Cryptographic proof that nothing changed between environments — no secret edits, no config drift.

sha256:9f3a7b... in dev = sha256:9f3a7b... in prod. Same hash, same behavior, guaranteed.

What the Demo Shows

Act 1 — Bundle

Immutable Bundles

Prompts, policies, and model config are pinned into a single SHA-256 content-addressed artifact. The bundle manifest records every artifact and its hash — nothing can change undetected.

Act 2 — Promote

Environment Promotion

Bundles promote through dev → staging → prod with configurable gates at each stage. The same hash flows through every environment — what you tested is what you deploy.

Act 3 — Rollback

Instant Rollback

One command restores the previous version. Rollback is a pointer change, not a redeploy. The reason, timestamp, and operator are recorded in the promotion history.

Act 4 — Audit

Full Audit Trail

Every promotion, rollback, and gate result is recorded with who, when, what version, and which environment. Complete traceability for compliance and incident review.

Try It Yourself

ReleaseOps runs locally with no API keys. Bundle, promote, and roll back in minutes.

pip install llmhq-promptops llmhq-releaseops
releaseops init
releaseops bundle create my-agent --version 1.0.0