How are SaSame components deployed safely?
Deployment is an evidence-producing operation, not merely a successful build command.
- Collection
- documentation
- Updated
- 2026-07-30
- min read
- 2
- Version
- v1
Deployments bind an immutable source SHA to a component release, health checks, external verification and a rollback target before traffic changes.
Purpose
Deployment is an evidence-producing operation, not merely a successful build command.
Operational model
A release manifest records source, dependency, schema and decision hashes. Candidate components start separately, are verified, switch atomically and retain a rollback receipt.
Boundary and limitations
A local build, CI success or process restart alone does not prove production success.
Examples
2- 01
A blue candidate can pass health and schema checks while the current green website remains active until the final route switch.
- 02
A staging deploy receipt records live_nginx_before_sha256 and live_nginx_after_sha256 as an explicit before/after pair, so an unrelated concurrent change to shared infrastructure is caught as a hash mismatch instead of silently overwritten.