Yippee deployment philosophy: the primitives most teams use today are too coarse-grained, mixing application-code changes, infrastructure changes (e.g. upgrading a C utility for a security patch), and schema/database changes into one dangerous release. The framework should expose three distinct deployment types and a built-in deployment queue that serializes them: a developer says 'make these changes now', the framework runs them one at a time, waits for success, and moves on. Docker is embraced for infrastructure deployments but not for application deployments, since rebuilding a Docker image for every Ruby character change prevents sub-second deploys.