Independent engineering concept · All workflow states and execution results are simulated · No live repositories or cloud environments connected.
2020 Engineering Delivery
04 / ENGINEERING DELIVERYSimulated

Three environments. Three distinct boundaries.

Dev proves the change runs. Staging proves the release behaves. Production admits only an approved, verified artifact. Environment status and digests below read directly from the shared release.

dev

Automatic

Isolated workspace. Main merge deploys automatically; smoke tests accept the change.

Awaiting artifact
dev.example.invalid

No prod secrets or data; dedicated nonprod resources and deployment identity.

Digest not yet deployed

staging

Validated

Production-like configuration, test data. Integration, e2e and smoke evidence required.

Awaiting artifact
staging.example.invalid

Separate config, secrets and identity. Match production behavior, not production data.

Digest not yet deployed

Production

Human gate

Restricted identity and data. Named approval, change window and health verification.

app:last-known-good
prod.example.invalid

Jordan · synthetic release approver. No agent production writes; least privilege.

Prior artifact · separate known-good digest

Why it matters

Dev must never be a disguised production target. Isolation protects real users, secrets and data while teams move quickly.

Environment ≠ deployment slot

An environment is a security and delivery boundary: its identity, data, configuration and approval policy. An Azure App Service slot is another deployment within an app. Slots can share an App Service plan and downstream data; they do not automatically provide full isolation.

Where slots can help

A production app’s staging slot can validate a version before a controlled swap. Configure slot-specific settings and data access, understand swap behavior and validate recovery. A slot does not replace an isolated Dev environment or a separately governed Staging system.

Microsoft: deployment slots ↗

Promotion history is release evidence.

Same digest in each deployed environment. Last-known-good Production remains separate until promotion.

Open live scenario state

Execution evidence

Deterministic audit
  1. 01
    Scenario

    ENG-104 opened. Synthetic release; no live execution.