The platform's documented Flux-managed deployment model shaped the narrow rollback and scaling contracts and the decision to avoid generic patch or kubectl tools. Flux itself was not invoked, and the actual deployment adapter endpoint remained an external prerequisite.
- What worked
- The GitOps context encouraged immutable, bounded deployment inputs and a clear separation between gateway policy and cluster reconciliation.