Engineering showcase
A classroom system with a visible chain of responsibility.
The architecture separates sensing, local decisions, storage and authorised sharing so the system can be tested, explained and improved one layer at a time.
Architecture map
Environment to authorised portal.
Data moves through a small number of explicit boundaries. The public website does not receive a live Pi address or classroom control endpoint.
Layer 02 / Interpret
Raw readings become a state through checks.
Layer 03 / Store
History survives the internet.
Readings are persisted locally on the Pi so a reboot or an unavailable connection does not erase the evidence already collected.
Layer 04 / Respond
Four states, with the reasoning attached.
Stable around baseline.
Minor sustained change.
Significant deterioration.
Confirmed hazardous pattern.
Layer 05 / Share
Why local-first?
Internet access changes what can be viewed remotely. It does not decide whether the classroom can sense, process, store or respond.
Internet available
Local monitoring + optional remote portal. Selected readings and status can be shared with authorised users.
Internet unavailable
Local acquisition + processing + history + classroom response continue on the Raspberry Pi.
