Streaming Video Encoding & Packaging Pipeline · View 16 of 22 · Operations
A promoted build changes nothing retroactively
- New recipes pin the new build. Existing recipes and the renditions derived from them keep their digests and are untouched.
- The catalogue migrates lazily: a rendition is re-encoded under the new build only when demand asks for one that does not exist yet.
- This is the consequence of content-addressed identity (ADR-04) that makes it affordable rather than terrifying.
The determinism gate is first
- A build that does not replay a golden corpus byte-identically is rejected before anything else is measured. Non-determinism would invalidate idempotent retries, cache trust and lineage in one step.
- Quality regression against the current build is a separate gate, because a build can be deterministic and worse.
Assumptions
- Assumed 1% shadow encode on new titles and a 48-hour single-tenant canary before promotion. Both are judgement calls, both are cheap to change.
