M04-L03 exercise — Capture project and hardware facts

Starting checkpoint: CP02. Figures: SS09-01, SS09-02, D08.

In a new CP02 copy, prepare three sourced rows: board identity, memory variant, and one explicit physical-revision unknown. Create a requirements document with the teaching alert threshold labeled as a planned later feature, keeping it separate from hardware facts and current baseline behavior. Link the documents from the README. Submit the context files and source-check note. If a source cannot be opened, record the access limitation and distinguish supplied reference material from your own live check.

Completion record

Record the checkpoint, changed files, checks actually performed, results, and open limitations. Keep expected output distinct from observed output. Preserve the starting copy and review the final diff before considering the artifact complete.

Full guest editor view shows the populated documentation tree and README links on the guest-only surface.
SS09-01 · SS09-01. Inspect the populated document tree and its linked project context.
Full editor view shows board 5477 and memory facts, the separate 2652 comparison, source URLs, and an explicit physical-revision-unobserved note.
SS09-02 · SS09-02. Record sourced board and memory facts while leaving physical revision unobserved.
Requirements lead to a test plan and actual evidence; sourced hardware facts support decisions and implementation.
D08 · D08. Requirements, sourced facts, decisions and actual evidence support different parts of a reviewable engineering result.