Network state
What it means to treat a network's state as a first-class value — objects, canonical form, and ownership.
Concept cluster
RAHN is built from a small set of ideas, each specified, implemented, and test-enforced in its own right. These pages explain each concept: what it means, why it matters, how RAHN approaches it, and where the honest limits are.
What it means to treat a network's state as a first-class value — objects, canonical form, and ownership.
Why the same inputs must produce byte-identical states and ids on every machine — and how RAHN enforces it.
Identity from content: how sha256 over canonical bytes makes state verifiable, shareable, and immutable.
Check before change: how verification gates commits and executions, and what "verified" does and does not mean.
The constitution: structural floors, named connectivity, and the honesty rule that verification is only as good as its encoding.
Explicit causal edges between observations and commits — with epistemic status, never inference.
Why every plan executes in simulation by default, and why real execution is opt-in, isolated, and gated.
For the design reasoning behind these concepts, read the architecture overview; for the normative rules, see the specifications.