One bucket consolidates everything about how the product is packaged, signed, shipped, installed, upgraded, backed up and restored. Scope includes single-node, multi-node and air-gapped deployments from the same images.
Ops Surface · C13 Deployment & PackagingClick to expand
Why operations is a single bucket
Build · Ship · Run form one continuous pipeline — the same release artefact (image + SBOM + signature) that is built is what ships and runs. Splitting across buckets would fragment the chain of custody.
Three topologies from one codebase — single-node (Compose), multi-node (Helm), and air-gapped (mirrored tarball). SRS §2.4 mandates identical images across all three.
Operational rigour is a first-class concern: backup with verified restore (REQ-SAFE-5), rolling upgrades without downtime, signed + SBOM-attested images (REQ-SEC-13), forward-only versioned migrations.
Air-gap is the hardest constraint in this bucket — every external feed in C11 needs a documented offline refresh cadence and staleness SLO.