# Review 2026-03-15

Made at the owner's request. When it was written nothing in the notes had been changed. On 2026-03-16 the owner answered: 2 yes (applied), 3 no, 1 not yet (waiting).

## 1. Twelve nodes, but the houses list nine
Kind: contradiction
Where: `state.md` (Demo inventory); `greenhouse-a.md`; `greenhouse-b.md`
Found: the inventory and `sensor-node.md` say twelve nodes; greenhouse A has four and greenhouse B five. Three are not placed anywhere in the notes.
Proposed fix: add to `backlog.md`:
```
- Where are the other three sensor nodes? `state.md` says 12, the houses list 9 (owner; found in the review of 2026-03-15).
```
Status: proposed

## 2. The dashboard shows the forecast but does not name its source
Kind: missing relation
Where: `dashboard.md` (first line)
Found: the dashboard shows "the forecast", which comes from `weather-feed.md`; the dashboard note does not name it.
Proposed fix: in `dashboard.md` replace
```
- Reads from `timeseries-db.md`.
```
with
```
- Reads from `timeseries-db.md` (the forecast comes from `weather-feed.md`).
```
Status: applied 2026-03-16

## 3. Firmware: the review date has passed
Kind: superseded
Where: `firmware.md` (header `review_after: 2026-03-01`)
Found: the humidity calibration was due on 2026-03-01; nothing says it was done.
Proposed fix: calibrate one node against the reference sensor, then move `last_confirmed` and `review_after` (2026-09-01).
Status: declined 2026-03-16: the calibration is planned for April with the new reference sensor