Atlas Protocol
Governance
A protocol with no company behind it still needs rules. Atlas splits governance into two layers — one designed not to change, and one you're free to fork.
Who makes the rules when there's no one in charge?
Imagine a network with no company behind it. No board of directors. No CEO who can push an update overnight. Just thousands of independent nodes, each run by a different person, each with their own priorities.
How do you agree on anything? Every decentralized system faces the same dilemma: make rules too rigid and the network can't adapt to new needs. Make them too flexible and everything fragments into chaos.
Atlas resolves this by separating governance into two distinct layers — each with different scope, different change cost, and different exit cost. Together, they give the network just enough structure to cohere, and just enough freedom to evolve.
What cannot be changed
The first layer is protocol-level governance — rules embedded directly in code and shared by every compatible node on the network. These are the non-negotiable invariants. If you break them, your messages simply aren't valid.
This layer is slow to change. Updates require new software to be written, reviewed, and adopted across the network. It's expensive to exit — leaving means your node becomes incompatible with everyone else.
Think of it as the rules of physics for the network. You can build anything you want on top, but gravity still applies.
- Cryptographic primitives — which algorithms are valid for signing, hashing, and encryption. The bedrock of identity and trust.
- Protocol validity rules — what makes a message structurally correct. The grammar every node must speak.
- Envelope structure — the required format for signed, immutable content containers. The shape of every piece of data on the network.
Protocol rules keep the network coherent, but they can't govern everything. For dynamic decisions — economic parameters, coordination norms, trust allocation rules — Atlas uses Legislation: signed documents that any node can choose to adopt, modify, or ignore.
Governance Through Signed Documents
LegislationLegislation documents are cryptographically signed and published to the network like any other content. But unlike protocol rules, they aren't enforced automatically. Each node explicitly chooses which Legislation to adopt.
This makes the soft layer fundamentally different from the hard layer. Don't like a rule? Stop adopting it. Want to change a parameter? Publish a new version. The cost of change is low, and the cost of exit is even lower — you simply stop following the document.
Legislation defines the dynamic interpretation layer of the network: shared convention-based systems, network parameters tuning, and coordination norms that help nodes work together without being forced to agree.
How the Network Bootstraps
Semantic AnchorEvery network needs a starting point. On bootstrap, a semantic anchor publishes the initial set of Legislation documents — the foundation for custom order and rules building.
These initial documents define the starting parameters: how trust allocations work, how FairShares are distributed, how voting is conducted. They are the first draft of the social contract.
The semantic anchor is a starting point, not a permanent authority. Once the network grows, the community governs changes to these parameters through the voting rules that the initial Legislation itself defines. The anchor lights the fire — the community decides how it burns.
What Can Be Changed
ParametersSo what does Legislation actually control? Concrete, named parameters that shape how the network behaves. Each one has a clear purpose and can be adjusted through the governance process.
These aren't hidden in source code. They're visible, named, and configurable — published as Legislation that every node can inspect, adopt, or reject.
Four principles that hold it together
Influence over meaning is named, visible, and configurable. No hidden power, no backdoor control.
Each node independently chooses which interpretations to adopt. Exit is always an option.
Legislation affects interpretation and weighting only. Protocol validity and safety remain untouched.
Disagreement results in divergence, not coercion. The network splits cleanly, not violently.
