---
id: M04-L03
title: "Capture project and hardware facts"
module: M04
chapters: "9"
checkpoint: CP02
---

# M04-L03 — Capture project and hardware facts

Build a small linked context set that distinguishes what the project wants from what its hardware sources establish. Start with CP02 and the README from Module 4. The output is a sourced identity record and explicit unknowns, not a physical wiring claim.

CP02 supplies the README, project brief, and hardware reference. Create the additional notebook records only as you add meaningful content here and in the next lesson. Use the resulting documents according to their purpose: `requirements.md` for intended behavior, `hardware.md` for exact sourced target facts, `decisions.md` for choices and rationale, `evidence.md` for observations, and `handoff.md` for current state and the next action. The README links readers into that structure. More filenames do not automatically mean better context.

The selected example board is Adafruit product 5477, the ESP32-S3 Feather variant identified with 4 MB flash and 2 MB PSRAM. Confirm the product identifier on the manufacturer's page before reading memory or interface details. A related family name can lead to a different variant. Keep the BME280 breakout identity, product 2652, separate from the host board and from chip-level documents.

Record publisher, title, URL, relevant section, access date, and revision when supplied. An access date is not a publication date. If the source does not establish the revision of a physical board, write that limitation. Do not fill an empty cell with a familiar number to make the table look complete.

Add a consequence to each relevant fact. The exact memory variant affects target configuration; an unknown physical revision affects optional deployment checks. The future capstone's 28.0 °C teaching threshold is a planned requirement or design choice, not a sensor-calibration claim. A source can support an identity without supporting a pin mapping.

Work through one row at a time: identify the claim, find the source location, retain units and conditions, and explain the project's consequence. If two sources disagree, check whether they describe the same board, chip, or operating condition before declaring a conflict. Preserve unresolved differences visibly.

Figure D08 connects requirements, facts, decisions, and results. Explain those four categories using one example from the project. The ability to classify a statement helps prevent an AI-generated summary from turning a plan into an observation. Finally, follow every new project link and review the diff for unsupported added facts.

## Resources and completion

Use the Sensor Monitor `CP02` download and its `README.md`; project paths in this lesson are relative to that root. Read Chapter 9 for the full lab and explanatory review answers. Figure IDs: SS09-01, SS09-02, D08. Primary references: [Adafruit product 5477](https://www.adafruit.com/product/5477) and [GitHub Markdown tables](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables). Complete the [exercise](exercise.md), preserve actual evidence, and use the separate instructor answer key for self-check after attempting the task. Narration scripts are production sources; final transcripts must match the actual narrated edit.