Streaming Video Encoding & Packaging Pipeline · View 07 of 22 · Structure
Why the recipe plane is its own layer
- It is the only derived artefact that is not regenerable: lose it and you have a master and no idea how the published bytes were made.
- Putting it above the control plane rather than inside it is what lets a job be re-run, a region be rebuilt and an encoder be upgraded without any of them touching the decision.
- Everything below Execution is replaceable. Everything in and above the recipe plane is custody.
Two execution paths, one layer
- Batch and on-demand encoders share the layer and the code, and share no capacity (ADR-08). The layer boundary is about responsibility, not about a deployment unit.
Deliberate omission
- Seven edges are drawn out of roughly forty. Every layer writes to the audit log and emits telemetry; drawing that would make the view unreadable and tell a reader nothing.