Weather, access and identity
Enclosures, mounts, service access, antenna placement, thermal behaviour and visual language are resolved together.
Crux Design / Sensor Net / Method
Designed as a system,
not a gadget.
The physical node, its radio path, public page, maintenance record and human response ritual are treated as one designed experience.
01 / System design
The node is not the product. The operating loop is.
Tap / sense→Receive→Interpret→Act→Record
Crux treats hardware, interface, communications and maintenance as one design problem. A beautiful enclosure that cannot be serviced is incomplete. A live dashboard with no accountable response path is equally incomplete.
02 / Layers
Four disciplines, one field object.
Power and sensors as a stack
PoEA method of carrying electrical power and network data over the same Ethernet cabling.Crux usage: Crux uses PoE to power and connect fixed nodes with a single cable, together with appropriate injectors or switches, conversion hardware, and surge protection.Open full definition, solar, batteries, radio, GNSSThe collective term for satellite constellations and augmentation systems used to determine position, navigation, and precise time.Crux usage: Crux uses GNSS modules for node location, time reference, mapping, deployment evidence, and position-aware diagnostics.Open full definition and environmental sensors are selected as a maintainable system rather than a shopping list.
Atlas as operating context
Readings are validated, summarized and published through controlled interfaces. Public output is separate from private operational state.
Daymark accountability
Events need acknowledgement, ownership and closure. The interface is designed around the ritual: receive, act, record.
03 / Build philosophy
Develop openly enough to be understood; privately enough to remain safe.
Public layer
Approximate positions, major status, sanitized readings, design documentation and participation routes.
Private layer
Exact coordinates, command paths, internal IPs, diagnostics, personal details, raw messages and maintenance credentials.
Design case study