- Completion of earlier levels in this track
- Ability to explain design decisions to non-technical stakeholders
- Explain from problem to evidence in your own words and apply it to a realistic scenario.
- A capstone is a build plus proof. You show what you built, why it is safe, and how you know it works.
- Check the assumption "Scope is realistic" and explain what changes if it is false.
- Check the assumption "Risks are documented" and explain what changes if it is false.
- Deliver an end-to-end scenario with clear assumptions and evidence
- Present trade-offs and final recommendation in plain language
- A capstone delivery note that can be used as portfolio evidence
- Vague success criteria. If success is not measurable, you cannot evaluate and you cannot improve.
- Proof without testing. Screenshots are nice, but you still need repeatable checks.