Environments and promotion

An apply evaluates the complete .deliberate/ tree, previews its effects, and reconciles one Environment:

deliberate diff --env production
deliberate apply --env production

Repeating the same apply is safe. There is no partial-resource apply; the Environment is reconciled to one coherent Project revision.

Environment flows

A flow describes which Environments exist and the allowed promotion edges between them. The bundled default provides the normal preview-to-production experience. Teams on plans that permit custom flows may change this topology; otherwise the current flow remains usable but locked.

Promote a tested revision rather than reconstructing it:

deliberate promote --from preview-42 --to production

Deployment handoff

After apply, the CLI and console report whether Components became ready and show the relevant public or Private Net routes. A Blueprint’s optional onboarding link is a first-deploy UX nudge, not hidden lifecycle state.

Generated platform hostnames are stable for their resource identity. Use your own domain for a customer-facing production address.