Unit 8: Build the Robot System Readiness Dossier

The final unit does not reward the largest pile of screenshots. It asks whether every important system claim has a clear acceptance criterion, a traceable evidence source, and an honest boundary.

Week 17 assembles the strongest Java/WPILib and ROS 2 evidence from the course, adds one controlled failure/recovery case, and turns the result into a readiness dossier that can survive technical review.

Chapter question

How can you decide which parts of a robot software system are ready, conditionally ready, blocked, or not demonstrated when each layer is supported by different evidence?

What you will understand

You will learn claim-to-evidence traceability, acceptance criteria, readiness categories, representative evidence selection, controlled failure injection, recovery criteria, integration-status labeling, and the difference between subsystem readiness and whole-system readiness.

What you will do

You will build a Claim-to-Evidence Matrix, select representative Java/WPILib and ROS artifacts, preserve one deliberate failure and repair, attach the Java-to-ROS Integration Contract, classify each major layer, and prepare a technical defense index.

What you will produce

Your final artifact is a Robot System Readiness Dossier containing the claim matrix, selected evidence, failure/recovery record, integration contract, final readiness table, executive technical summary, and defense index.

How the week connects

Units 4–5 built the Java/WPILib component and evidence practices. Units 6–7 built ROS runtime and reproducible bringup practices. Week 17 combines those evidence streams without pretending they are one integrated execution path. Week 18 will challenge the dossier and produce the final readiness defense and handoff.

Key vocabulary

readiness, acceptance criterion, claim, evidence chain, pass, conditional pass, blocked, not demonstrated, failure injection, recovery criterion, traceability, provenance, technical defense

Approximate time

About 210 minutes for the five lessons, lab, and wrap-up. Students may use local or supplied evidence, but every artifact must identify its provenance accurately.

Final evidence required

A complete Robot System Readiness Dossier with at least ten claim rows, three representative Java/WPILib evidence items, four representative ROS evidence items, one controlled failure and verified recovery, an explicit Java-to-ROS integration status, bounded physical-hardware status, and a defense index linking every major readiness claim to its evidence.