15.263 14.9.23 Supply chain, actualización y rollback
SUP-01. Build OCI-compatible images from version-controlled definitions. SUP-02. Pin base image and dependency digests for production releases. SUP-03. Generate SBOM and build provenance for application and model packaging. SUP-04. Sign images, models, configuration bundles and offline update media. SUP-05. Verify signer identity, signature, digest, provenance and compatibility before staging. SUP-06. Reject mutable tags such as latest as activation references. SUP-07. Scan dependencies and images; record accepted exceptions with expiration. SUP-08. Keep build environment separate from the production edge device. SUP-09. Promote the same immutable artifact through dev, benchmark, canary and production. SUP-10. Use two release slots or equivalent previous-known-good snapshot. SUP-11. Run pre-activation migrations with backup and compatibility checks. SUP-12. Run post-activation health, smoke and sample-analysis checks. SUP-13. Rollback automatically when critical gates fail within the observation window. SUP-14. Record a DeploymentReceipt for every activation and rollback.
SLSA estructura garantías de supply chain y provenance; Sigstore/Cosign puede firmar y verificar blobs o imágenes y conservar bundles de verificación. La selección concreta puede cambiar, pero el contrato canónico exige firma, identidad, digest y provenance verificables [P49-R22, P49-R23].
15.263.1 Slots de release
active: release-A (known good)
staging: release-B (verified, not active)
activate B -> migrations -> smoke -> canary window
PASS: B becomes known good
FAIL: rollback to A; persist DeploymentReceipt