How Nodes Connect Without Losing Themselves
Every document before this one rests on a claim about scale: multiplanetary civilisation requires redundancy not concentrated in a single hemisphere. Taken seriously, that claim does not stop at one node in one country. Planetary infrastructure is a network of nodes in many countries — different geographies doing different jobs, connected. The Technical Brief already names the mechanism at machine scale: selective lattice synchronisation under explicit consent tokens. This document states the same mechanism at planetary scale.
A network needs joining rules more than it needs a map. This is the joining rule.
It would be easy, and it would read impressively, to fill this page with an assessment of the world's countries — which are stable, which are vulnerable, which have the strengths a network wants. That document will never exist in this project.
An atlas of other people's vulnerabilities, written from a distance, is the cartographer's error this project was founded against: confident lines drawn over places the mapmaker has never stood. The old maps did it to this continent. It will not be done from here to anyone else. Where stability is relevant to a connection, the reference is the country's own institutions and its own public record — never this project's verdict.
CrystalCore's three constraints have now been stated twice — for the machine (First Principles, enforced in code) and for the country (Sovereign Capability Framework). The lattice is their third and final scale.
| Constraint | The machine | The country | The lattice |
|---|---|---|---|
| Local-first | Intelligence and memory reside locally; links are useful, not required | Capability resides in-country, functioning whether or not any partner remains | Every node runs without the network. Disconnection degrades reach, never survival |
| Consent-native | Actions require valid, current consent; absence refuses | FPIC as floor, benefit-sharing as standard; a veto is not a stake | Connection is opt-in, scoped, and revocable — joined by agreement, never by assessment or pressure |
| Continuity-preserving | Memory continuity is a hard constraint | Institutions carry capability across generations | The network strengthens each member's own continuity; it never becomes the single point whose failure erases what members know |
Five rules govern how any country joins the lattice this project proposes to begin building.
Each country names its own strengths, constraints, priorities, and terms. Nothing about a node is inferred, assessed, or assigned from outside — exactly as the consent gate refuses to let anyone speak for a guest. Sovereignty over your own description is the first act of membership.
A country connects the parts it chooses — a recovery port, a training pipeline, a research partnership, a data standard — and keeps everything else. Scope is explicit and enumerated, never implied by membership. What is not named is not connected. This is the gate's read-scope and write-scope, at treaty scale.
Strong and weak nodes exist in every real network, and pretending otherwise is how the strong end up writing the rules alone. The protocol's answer is the Sovereign Capability test applied to every connection, in both directions: what capability does this leave in each node? A connection that drains the weaker member fails the protocol regardless of what it builds.
Joining is not permanent surrender. Consent is ongoing and revocable, and withdrawal is not punished — a node that disconnects retains everything it built and everything it learned, because the third scale's first rule guarantees it can function alone. Fail-safe at planetary scale means leaving is survivable. A network you cannot afford to leave is not a lattice; it is a trap with good branding.
Where a node's stability matters to a connection, the network's role is to strengthen the node's own institutions — its training, its governance capability, its industry — not to grade them. Support flows through the five departments of the Sovereign Capability Framework, which applies to every member, not only the first.
Recovery geography, ports, logistics, launch and landing support distributed across hemispheres.
Supply chains and refurbishment work shared across members' firms.
Training pipelines, research partnerships, and the capability transfer of Framework Department 1.
CrystalCore-class local-first nodes, synchronising selectively under explicit consent tokens — this protocol running at machine speed.
Today, the lattice described here has no members and exactly one proposed node. This document is written before the network exists, deliberately — protocols written after power settles merely describe the power. The rules above are what this project will hold itself to from its first agreement, while it is small enough for the commitment to be cheap and therefore credible.