High-level flow before diving into protocol data and signing
Each community writes a local social contract (the charter). This is what you expect from each other: housing, shared defense, ecological care, consensus process.
Communities then choose a Polity federation. This Polity has rules about membership, exit, conflict, mutual aid, and shared resources. It is not a single government, it is a common framework.
We include a technology path because the opposing system is built on highly optimized, AI-driven infrastructure. Appropriate technology (fedinet, signed ledgers, secure comms) gives counter-power where centralized systems have firepower.
That said, many polity actions can be low-tech: paper consensus logs, neighborhood boards, mutual aid notebooks, and in-person meetings are all valid. This site shows one possible tech-assisted implementation—not a commandment.
The charter text is stored as a protocol file. A trusted node signs the file with their private key (Ed25519). The signature proves this group approved this text at this time.
Signed charter + group identity is sent to other nodes via a federated network (Fedinet) just like in the Fediverse. Other groups can automatically verify that signature and decide to trust or not.