Read and retain
Bring simulator telemetry into a local record. Field adapters and real-site signal quality remain part of future validation.
RAIN / Software
The software platform direction around RAIN Runtime: bring signals in, run models locally, evaluate updates, and retain an operating history.
Simulator foundation
01 / THE IDEA
The current foundation implements telemetry capture, local storage, inference, retraining, model promotion and rollback, and signed history against a battery-storage simulator. RAIN OS describes the broader software product direction around that runtime; it is not an announced general-purpose operating-system distribution.
Bring simulator telemetry into a local record. Field adapters and real-site signal quality remain part of future validation.
Compare a candidate model with the incumbent on held-out data. A rejected candidate remains part of the recorded history.
Connect advisories to model versions and operating records so the next decision has context. Equipment control stays separate.
02 / IN PRACTICE
Define the scope, preserve the boundary, and make the outcome something a person can inspect.
Capture incoming telemetry and retain the data needed for the defined learning task.
Produce inferences, train a candidate, and compare its performance before changing the active model.
Inspect outcomes and model changes as evidence for an operator, rather than treating an advisory as an automatic command.
03 / A FEW DETAILS
A production OS distribution and general deployment process are not offered here. The implemented foundation is a simulator-based runtime, with a scoped field pilot as the next milestone.
No. Field validation, production uplink transport, hardware-backed signing, and delivery of upstream model artifacts remain unfinished work.
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.