Skip to content

PromptOps

Definition

Section titled “Definition”

PromptOps is the discipline of managing prompts as versioned, testable artifacts with safe rollout and observability.

Schema / Parameters

Section titled “Schema / Parameters”
  • Metadata: id, version, owner, domain.
  • IO contracts: input_schema, output_schema, error_schema.
  • Eval policy: tests[], acceptance, budget.
  • Rollout: canary_percent, fallbacks, kill_switch.
  • Storage: repo_path, registry_ref.

Defaults

Section titled “Defaults”
  • Store prompts in VCS; changes require PR + CI passing.
  • Canary to 5% traffic before 100% rollout.
  • Keep last 3 stable versions available for rollback.

Examples

Section titled “Examples”
  • Canary a new prompt with guardrails and artifact diffs captured.
  • Auto-rollback on error-rate > threshold for 5 minutes.

Limits

Section titled “Limits”
  • No production rollout without passing CI evals.
  • No embedded secrets or PII in prompt templates.
Section titled “Related”