Architecture
Ecosystem
Root Record is one system with three public layers. Knowledge is what the system knows. Runtime is what the system executes. Data is what the system records.
Loading public telemetry...
Knowledge
The knowledge layer holds architecture, procedures, agent context, security material, work orders, guides, and system documentation. It is the RootRecord Library. A later session, person, or agent is supposed to start from that record instead of from memory.
The public library repository is the published face of that layer. Private notes stay in the library. A repository existing is documented, not a live runtime. Knowledge
Runtime
Runtime does the work. Pacific Solar Server is that runtime. Field systems sit with Hawaiʻi: weather and geology. Computation and services continue on the Mainland Server when the work has to cross the Root Record Network.
The public network feed can show that this path is reporting: Hawaiʻi flows, Mainland Server flows, active flows, and endpoints. Those counts are not a grade of the whole runtime, and they are not a history. Infrastructure · Systems
Data
Data keeps the state. The RootRecord Database is that layer: telemetry, system state, energy, weather, geology, media, logs, and reports. The public site reads a narrow slice of that record. It does not open the database.
This site has no public database health signal. A field reading is an observation. It is not proof that the database is healthy, complete, or caught up. Data
Network
The Root Record Network joins Hawaiʻi and the Mainland Server. Public status uses that link. The globe draws the link from coordinates the public feed can name. Endpoints are places, not a map of private hosts.
The Website Node is the public site. It presents the system. It does not execute field work, and an arc drawn to it is architecture, not a traffic count. Private paths are not part of this page. Status
Continuity
The layers stay separate so the system can still be understood after people, agents, and machines move on. Meaning stays in knowledge. Work stays in runtime. State stays in data. The public site is only the view.
Continuity is also why a missing reading stays missing. Filling a gap with a healthy state would make the next operator trust a fact the feed never reported. Why Root Record exists
Verification
A page loading, a commit landing, or a service being configured is not proof that a runtime is healthy. State is accepted when there is evidence for it: a reading, a time, and a source the public feed actually returned.
The words on Status follow that rule. Documented, reporting, and no public signal are different claims. Security