Operations
These runbooks separate intended SVNM procedures from observed production facts. Deployment, certificate issuance, sidecar activation, and production verification are asserted only in the dated receipt after direct observation. (docs/OPERATIONS.md:285-342, SVG-Animator-BIBLE.md:334-336)
The operational safety boundary is an immutable release directory plus an atomic live symlink, a single-use release token, and byte verification against the committed six-file checksum ledger. Sidecar code must match the corresponding application release whenever a rollback crosses an audio-service change. (SVG-Animator-BIBLE.md:322-332, docs/OPERATIONS.md:66-68)