---
id: M08-L05
title: "Challenge: demonstrate and defend your result"
module: M08
chapters: "17–18"
checkpoint: "CP09"
---

# M08-L05 — Challenge: demonstrate and defend your result

Present the final evidence bundle and defend its scope. The core capstone combines requirements, implementation, review, tests, reproducible setup, project instructions, skills, and maintenance. A completion button or quiz score does not prove those activities occurred.

Prepare a short presentation of the requirement, the bounded source changes, the important equality/fault/parser cases, meaningful defect rejection, synthetic replay, firmware compilation, and fresh-checkout reproduction. Point to actual receipts and state any open mandatory gate immediately.

Use the 100-point rubric: requirements/sourced facts 15; Git history/review 15; firmware behavior 25; verification quality 25; documentation/handoff 10; instructions/skills 10. The suggested target is 80, plus mandatory reproducible build, critical software behavior, host/replay checks, and honest evidence labels.

Defend a few concrete decisions. Explain why 27.5 can have two states in the hysteresis band, why a valid threshold command cannot clear FAULT, why trailing numeric text is rejected, and why reset restores defaults. Show where requirements and tests establish each answer.

State the physical boundary. No board measurement, upload, wiring, sensor accuracy, USB behavior, or physical timing follows from the core software results. Optional bench work has separate evidence and is not required for the agreed core result.

Include the transfer task and maintenance plan. Explain one lesson from total-effort review and name a realistic trigger for rechecking a tool, source, or skill. If a result cannot be reproduced, preserve the failure and return to the relevant bounded repair rather than defending an unsupported pass.

Complete the final module quiz with explanations and unlimited retry. Practical assessment remains evidence-based; quiz progress is a self-check. A complete private candidate with reproducible software evidence is a valid course outcome without public publication.

## Reading the recorded demonstration

The recorded defense gives the demonstrated candidate a provisional 96/100 while its final package-accessibility gate remains open. This is an example of reporting an unfinished gate honestly, not a final practical pass or a human learner assessment. Your own submission must satisfy every mandatory gate in the rubric.

## Resources and completion

Read Chapter 17–18 and the matching Sensor Monitor checkpoint README, requirements, and evidence notes. Project paths are relative to its root. Figures: SS17-05, SS18-03. Attempt the [exercise](exercise.md), preserve actual results, then use the separate instructor answer key. 

Source resources: [Chapter 17](../../../../book/chapters/ch17/chapter.md); [Chapter 18](../../../../book/chapters/ch18/chapter.md); [checkpoint and recovery map](../../../../examples/sensor-monitor/docs/checkpoints.md). Use the README and requirements inside your named checkpoint; the repository's final CP09 files include features absent from earlier stages. The [capstone rubric](../capstone-rubric.md) defines scoring and mandatory evidence gates.