The engineering notebook.

A measurement becomes useful through context: its unit, where it is taken, what normal operation looks like and what change should prompt an action. Before adding a dashboard, define the question that the reading needs to answer.

Ask: who sees this value, and what can they do next?

Connectivity is an operating condition, not a guarantee. A useful system description explains what stays local, which actions need a network and how the operator understands the state after a connection returns.

Ask: what should continue working without the external connection?

A prototype does not need to contain every planned feature. Start with the uncertainty that matters most to the next decision, define an observable result and document what the experiment does and does not tell you.

Ask: which assumption would change the design if it proved wrong?