Node

The corpus is sovereign and complete — but closed. This lesson gives it surfaces so it can interact with the world outside itself.

The corpus alone

The corpus is a self-contained unit of perception, memory, and observation. It captures from one source, observes through its custodial chain, preserves through its longevity path, and holds one truth.

But it is closed. Nothing can write to it from outside. Nothing can read from it. Nothing can observe or manage it. The corpus holds its truth — but truth that cannot be accessed, that cannot receive, that cannot be managed, is truth in isolation.

The corpus needs surfaces.

Three surfaces

A surface is a boundary where the corpus meets the outside. Not a window into the internals. A defined interface with a single responsibility. The corpus needs exactly three.

Burn. The surface where reality enters. A sensor, a device, a data source pushes a frame to the Burn surface. The corpus receives it, validates it, writes it to S. Acknowledges. Done. Burn is the gate through which perception arrives. It does not interpret. It does not filter. It receives and holds. One responsibility: write.

Inspect. The surface where truth is read. A consumer — an application, a dashboard, an intelligence — queries the corpus through Inspect. Search by time range. Retrieve the last record. Read across the temporal depth. Inspect provides access to what the corpus holds without altering it. One responsibility: read.

Hatch. The surface where the corpus is observed and controlled. Operational state. Health. Configuration. Diagnostics. Repair. Hatch is where the use case lives — the adaptation layer where management happens. Hatch sees the corpus as a running system, not as a body of data. One responsibility: manage.

Why three

Not two. Not four. Three. Each surface has one responsibility. The responsibilities do not overlap.

Write and read are separated because the writer and the reader have different relationships to the corpus. The writer is the source — it pushes perception. The reader is the consumer — it pulls truth. These are different roles with different trust boundaries. Combining them into one surface conflates the source with the consumer.

Management is separated from both because managing the corpus is not reading its data and not writing perception to it. Management is about the corpus as a running system — its health, its configuration, its operational state. A manager does not need to see the data. A reader does not need to reconfigure the system. A writer does not need to know about diagnostics.

Three surfaces. Three responsibilities. Clean separation.

The node

A corpus with its three surfaces is a node.

The corpus is the body — perception, memory, observation, sovereignty. The surfaces are how the body interacts with everything outside itself. Together they form the smallest deployable unit: a complete system that can receive perception, serve truth, and be managed.

The node is not a server. It is not a process. It is not a binary. Those are implementation details. The node is the architectural unit — one corpus, three surfaces. It can be realized on a flight computer, a Raspberry Pi, a rack server, a container. The form factor does not matter. The architecture is the same.

Node sovereignty

The corpus is sovereign. The node inherits that sovereignty. One node, one corpus, one source, one truth. The node does not host multiple corpora. The node does not serve multiple sources. The node is the corpus made addressable — and the corpus demands sovereignty.

This means: every source of perception that needs its own truth gets its own node. A drone with six sensors runs six nodes. A ground station monitoring two feeds runs two nodes. There is no economy of scale in combining them. There is only contamination.

What the 100 level built

Eight lessons. One arc.

Time established that observation is circular. Perception established contact with reality. Memory revealed that perception implies memory — the first primitive for asserting influence over reality. Preservation defined the discipline of holding memory faithfully across timescales. Structure derived the ring buffer as inevitable. The Model described the observation chain. The Corpus emerged as the sovereign unit of truth. The Node gave the corpus surfaces — making it addressable, deployable, operational.

From the paradox of linear existence observed through concentric rings to a running node with three surfaces. The principles led. The architecture followed. Nothing was designed that was not first derived from what came before it.