Skip to content

Upstream Source

This page is part of Truthound Orchestration 3.x.

Source repository: seadonggyun4/truthound-orchestration Upstream docs path: docs/enterprise/rollback-playbooks.md Edit upstream page: Edit in orchestration

Rollback Playbooks

Operational maturity is not just about successful rollout. It is also about knowing how to step back safely when a host package, docs surface, support matrix, or result contract changes unexpectedly.

Who This Is For

  • release managers
  • on-call operators
  • maintainers approving first-party adapter changes

Rollback Triggers

  • support-matrix or compatibility regressions
  • host-specific API drift in supported minor versions
  • docs or public-site regressions that break operator guidance
  • result-serialization drift that breaks downstream consumers

Minimal Rollback Sequence

  1. stop promoting the new package or docs snapshot
  2. revert to the last green support-matrix and CI gate state
  3. confirm host-native execution still works on the prior version
  4. restore public docs if operator-facing guidance regressed
  5. reopen rollout only after the failing tuple or contract is reproduced and fixed