Present a capstone failure and the repair you made

A well-explained failure demonstrates stronger engineering than a perfect demo with no evidence. Show what happened, how you knew and what now prevents recurrence.

Inspect a fictional failure record

The delivery lab documents retry duplication.

from delivery_cases import capstone_failure_case

result = capstone_failure_case()
assert result["complete"] is True
assert result["blame_present"] is False
assert result["production_incident"] is False
assert result["record"]["regression"] == "W-4 now passes"

Structure the story: user impact/contract, minimal evidence, timeline, causal mechanism, alternatives considered, repair, regression test and remaining limitation. Distinguish symptom from cause and actual measurement from inference.

Demonstrate the old test failing and new test passing when safe. Avoid blaming the model, provider or teammate without evidence. Label the event as a local fixture if it was not production.

The FDE for Freshers course expects capstone defence to include recovery and honest limitations.

Exercise

Choose one genuine local failure, reduce it to a reproducible test and present a three-minute before/after explanation with the remaining risk.

Continue learning

This article is part of the FDE career entry and client-delivery practice sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Choose fresher FDE training versus an advanced professional pathway.
• Continue with Create an FDE learning roadmap from completed artifacts.

Reference: GOV.UK service assessment guidance.