Aerobrakes — Lesson 10: Writing the Phase I Report

---

Phase 1's simulation work is done. This session — the whole of Phase 2 — is about turning that work into a document someone outside the team could actually understand.

Objective: translate the team's working code and data into a coherent technical writeup.

Session Activities

Structure the report in five parts: problem statement, method, results (the metrics table from Lessons 5–9), the noisy/edge case discussion from Lesson 8, and the final recommendation from Lesson 9.

Then run a peer review pass: each team member reviews a section they didn't write themselves, and must be able to explain it before signing off on it. This directly enforces the course's standing rule that the whole team shares responsibility and understanding — not just whoever happened to write a given section.

Deliverable

The completed Phase I report, posted to the team's engineering notebook. Since the notebook has been maintained continuously since Onboarding, this session should mostly be assembly and polish, not writing from scratch.

Maps to milestone P2-M1.