Deployment
Host layout, process supervision, and how releases move through environments.
Process and layout
Prefer one writer per account (or your kit’s documented concurrency model) to avoid nonce and state races.
Pin dependency hashes or use lockfile-driven installs in production.
Ship config changes as versioned artifacts with a documented deploy command and rollback path.
The intended default path is a packaged runtime, env-based configuration, and promotion only after dry-run and operator sign-off.
Releases and rollback
Track which artifact version and profile are live. Rollback should mean redeploying a known-good artifact and env set, not editing running processes ad hoc.
Release numbering and changelog location are described in Release notes.
Related
Last updated