Delivery Lifecycle
Plan, code, review, build, test, package, release, deploy, verify, operate, learn — each stage with its inputs, outputs, evidence and rollback story.
Plan through learn as a chain of stages, each with defined inputs, outputs, automation, evidence and a way back.
The decisions taken before and during writing — change shape, size, reversibility and coexistence — determine how safely it can ship.
Human review reliably catches some classes of defect and reliably misses others; treating it as a general safety net is how the missed classes reach production.
Build one artifact, address it by digest, promote it through environments, and make the release a recorded decision separate from the deployment.
A deploy reporting success says the orchestration worked; verification is comparing the new version against a baseline on signals that reflect users.
The stage that closes the loop: turning what production taught you into a merged change, rather than into a document and a resolution to be careful.