An observable connection
A defined read-only input establishes where site signals enter the system while leaving equipment control separate.
RAIN / Hardware
Explore the architectural idea behind RAIN Node: observe equipment, compute locally, and make the operating record understandable.
Conceptual architecture
01 / THE IDEA
The RAIN illustrations show how connectivity, computation, and storage fit together inside a facility. They are explanatory diagrams, not photographs of manufactured hardware. The physical enclosure and internal configuration remain open design decisions.
A defined read-only input establishes where site signals enter the system while leaving equipment control separate.
Inference, training, and evaluation belong to an understandable local process with recorded model changes.
The local console direction brings advisories and operating history to the people responsible for the site.
02 / IN PRACTICE
Define the scope, preserve the boundary, and make the outcome something a person can inspect.
Understand which data enters the node and which systems retain control of the equipment.
Follow a signal through storage, inference, and model evaluation to see the role each layer serves.
Judge the architecture by whether a person can inspect the output and decide what it means for their work.
03 / A FEW DETAILS
No. It is a code-native diagram of system responsibilities. Form factor, internal components, and installation details are not finalized.
RAIN observes and advises. Showing the boundary makes clear that model output is not an actuation path into plant control or safety systems.
BUILD WITH RAIN
RAIN is preparing for its first field pilot. Start by defining the environment, the data boundary, and what success should look like.