Capstone project
Capstone: deliver, verify, and recover
Lesson 20 of 20 · 29 min · Module 6: Verify and recover
Connect checked source to a staged release and a practiced recovery path.
Start this lesson →Free. No installation: you write and run the code in your browser, and it is checked automatically.
By the end, you’ll be able to…
- Trace the change through every boundary
- Make the failure scenario a first-class test
The idea
A workflow combines an event boundary, job dependencies, and ordered steps. Conditions and prerequisite outcomes determine which jobs can run.
01Trace the change through every boundary
Review how tests justify the build, how the artifact reaches deployment, and how the deployment is checked. Source order alone does not connect those responsibilities.
02Make the failure scenario a first-class test
A successful build followed by an unhealthy release is plausible. Verify that smoke fails and recovery actually becomes eligible.
03Explain the operational outcome
The intended final state is the known-good release with a recorded failed candidate and recovery. The lab models the workflow; it does not claim a real Actions run took place.
Your project brief
What the checks look for
- Creates a checked build artifact
- Deploys the artifact to staging
- Verifies the candidate and triggers recovery
- Finishes on the known-good version with limited access
Take this with you
Delivery includes evidence, environment boundaries, verification, and recovery.
Go a little further
Write a runbook explaining which evidence to inspect before retrying the failed release.