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

One artifact. Every environment. No shortcuts.

AI-assisted development ends at a reviewable PR. Deterministic CI/CD begins with independent checks, then promotes the exact same release through Dev, Staging and Production.

Next safe action

Scope the change before tools can act.

PR #142 · independent gates

idle
Format / lint
Typecheck
Unit tests
Integration & contract tests
SAST / secret scan
Dependency scan
Build verification
SBOM / provenance verification

Conceptual DAG: parallel quality/security gates → verification build → SBOM/provenance checks → human review. PR verification builds are disposable; only protected-main merge creates the release artifact.

Create a PR first; merged checks cannot be changed.

All required PR checks must pass before human review.

Required checks and separate human PR approval are mandatory.

Immutable release

app:7c8e2f1

sha256:7c8e2f1a9b4d620e83f051ca467e285b90d41ac7f603be28d1659a842c3e507f

Not built · merge required

Mock SHA 7c8e2f1. Synthetic SBOM and signed provenance evidence; no real signing occurs. Production uses the same digest—not a new build.

Concurrency: one logical release, serialized promotions. Production rollout is never superseded by a competing run in this simulation.

dev

Automatic

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

Awaiting artifact
dev.example.invalid

staging

Validated

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

Awaiting artifact
staging.example.invalid

Production

Human gate

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

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

Main → isolated Dev

Merge to protected main and build the immutable artifact first.

Dev accepted → Staging

Dev smoke acceptance is required; staging already green cannot be redeployed in this scenario.

Staging green → Production

Staging integration, e2e and smoke evidence must be green.

Named production approval and an open change window are required.

Monitor, decide, recover

Deploy production before post-deploy verification.

Production health must pass before keeping the release.

Deploy this release to Production before rollback; reset to replay a completed rollback.

Health: idleDecision pending

Failure lab · deliberately simulated

An injected unit-test failure and an unmerged change are required; reset to replay after merge.

Dev must be accepted and production not yet approved.

A failed staging run is required.

Production must be deployed and not finalized.

Why it matters

A release cannot advance just because an AI says it is ready. Independent evidence and two separate human decisions keep authority explicit.

Execution evidence

Deterministic audit
  1. 01
    Scenario

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