0. What you’re looking at
This page is a map of the Sovereign Stack: the minimum set of layers and functional modules that have to work if you want real-world sovereignty to survive stress.
Here, sovereignty means something very practical: the ability for a layer to keep making its own decisions and honoring its own agreements under stress, without being forced to default to external institutions.
Instead of starting from laws, nation-states, or ideology, we start from the smallest unit (a single person with keys) and scale up to hardened citadel-scale infrastructure. At each step the same recurring problems show up—money, comms, security, food, governance—but they look different at different scales.
Think of this as a “civilization OS index”: the top-level schema that other documents, tools, and guides plug into. You can use it as a neutral classification system to:
- Place any real-world thing (person, group, org, enclave) on a clear layer
- See which functional modules actually exist vs which are outsourced or missing
See all 110 modules listed and mapped out here. Not finished with this page, but many of the modules' stacks + toolchains are built out here. Click on any module, most may not work, but many core modules do (money, comms, law, security, etc).
This map is not a blueprint for how society “should” be. It is a description of recurring functions that any resilient arrangement has to handle somehow. You can plug in very different philosophies and toolchains; the categories stay the same.
1. Layers
These five layers are the backbone of the Sovereign Stack. They are fractal: the same functional modules repeat at each layer, but scale, governance, and risk profile change.
Fractal rule Household and Business live at the same “scale band”: both are groups of individuals making shared decisions. Household is inward-facing (shared life). Business is outward-facing (shared production and revenue).
Single sovereign node · unilateral control · low coordination overhead · portable identity/keys.
Why this layer matters
- All higher layers ultimately rest on individual humans with keys, skills, and judgment.
- If individuals are fragile or captured (no keys, no savings, no comms), every larger structure is brittle.
- Design here is about personal resilience: can one person keep operating if every institution around them fails?
Fits here
- One person managing their own keys, budgets, and reserves
- Independent operator (even if earning externally) when funds are personal, not business-ledgered
- Solo “household” only when no shared finances exist (otherwise Household)
Key test
- If one person holds authority over the money system and no shared budget exists → Individual layer
Tight trust · shared daily life · shared consumption · low churn · high emotional/legal entanglement.
Why this layer matters
- This is where most real-world risk, care, and emotional load actually live.
- Household design determines whether people can pool buffers and specialization without losing sovereignty.
- In most crises, “who can you eat, sleep, and coordinate with every day?” is a household question.
Fits here
- Household
- Family unit (nuclear/extended)
- Domestic partnership / marriage
- Roommates with shared bills (if actually recurring shared finances)
- Small shared-living pod (3–8 co-housing) when finances are basically a household
Edge case
- Friend group that shares rent/utilities = Household (for money/finance purposes)
Production/commerce · external counterparties · revenue · AR/AP · refunds · payroll · vendor contracts.
Why this layer matters
- Transforms sovereignty into production and income: how you pay for everything else.
- Most exposure to regulation, courts, and KYC happens through business interfaces.
- Healthy businesses give communities bargaining power; captured businesses become attack vectors.
Fits here
- Company (sole prop → corp)
- Studio / agency
- Contractor collective (paid by outsiders)
- Marketplace operator
- Media org with subscribers (even if “community-driven”)
- Any org whose primary interface is selling goods/services
Key test
- If you generate invoices, handle refunds, or pay contractors regularly → Business layer
Membership fluidity · heterogeneous trust · commons coordination · people come/go.
Why this layer matters
- This is the scale where culture, norms, and mutual aid actually live.
- Community design decides whether people default to dependence on states/corps or on each other.
- Communities can host many households + businesses without centralizing into a state.
Fits here
- Friend group (social + occasional pooling; not a shared household)
- Neighborhood association (informal)
- Community group
- Mutual aid group
- Local meetup group
- Cooperative purchasing club / buying group
- Church/temple congregation as a funding pool (if not a commercial enterprise)
- Social club
- DAO-like group (membership commons, not operating company)
- Co-op when primarily a member commons vs commercial operator
Subtypes (useful distinctions)
- Social cluster: friends, meetups, clubs (light budget, low stakes)
- Commons cluster: associations, mutual aid (shared fund + governance)
- Project cluster: ad-hoc teams with a treasury (mission then dissolve)
- Membership cooperative: co-ops allocating resources among members (strong governance)
Hardened infrastructure · strategic reserves · continuity doctrine · survives coercion/churn/isolation.
Why this layer matters
- It’s what you build if you want the whole stack to outlive any single person, leader, or regime.
- Holds long-horizon reserves and infrastructure so that many communities and entities can survive shocks.
- Acts as a coordination shell for multiple entities without collapsing into a centralized state.
Fits here
- Citadel / enclave
- Resilience hub / safehouse network (shared assets)
- Intentional community (owns significant infrastructure + reserves)
- Long-horizon sovereign community (land/energy/security + multi-entity ops)
- Federation of local communities (network-of-communities)
- Endowment-style treasury entity funding/protecting the whole stack over time
Key test
- If it holds strategic reserves + funds infrastructure + has continuity plans across leadership loss → Citadel layer
Environment, not layer You will notice there is no explicit “State” or “Nation” layer here. In this map, governments, supranational bodies, and large platforms show up as environment and constraints that your stack has to deal with via modules like Law, Trade, Security, and Comms. They are not treated as layers you own.
2. Why layers & modules (fractal logic)
This map separates two questions that usually get mashed together:
- Layer: “Who is this for?” — a person, a household, a business, a community, or a citadel?
- Module: “What problems must this layer solve to stay sovereign under stress?”
Every layer deals with the same kinds of problems—money, comms, keys, food, security, governance—but the design constraints change with scale. A one-person OPSEC setup is not a citadel OPSEC setup, even though both are “security & OPSEC.”
Design rule If you don’t explicitly design a module for a layer, that module is being handled by someone else (the state, a corporation, a landlord, a cloud provider, etc.). This map is a way to make that dependency visible.
Why bother looking at each layer separately?
- Failure modes differ. A household failure (job loss) is not the same as a citadel failure (regime change).
- Time horizons differ. Individuals plan in years, citadels plan in decades.
- Attack surfaces differ. Businesses get targeted through regulation and contracts; communities through culture and division; citadels through infrastructure and law.
Why bother looking at each module separately?
- Everything is a module whether you see it or not. Money, comms, identity, security, food, logistics, memory – they are already there, just possibly fragile or outsourced.
- Modularity lets you upgrade locally. You can harden “Comms & Information” for a household without redesigning its entire life system.
- Fractal reuse. The same module list works for all layers. Once you know what “Security & OPSEC” means for one layer, you can scale the pattern up and down.
Practically: this page defines the canonical box labels. The deeper module pages define concrete stacks and toolchains that fill those boxes.
3. Where common labels land
Words like “neighborhood”, “org”, “guild”, or “co-op” are fuzzy. The same word can describe completely different structures. This section is about classification, not judgment: it helps you decide which layer a thing actually lives on so you can apply the right modules.
- Informal neighbor mutual aid / block group → Community
- Neighborhood with owned shared infrastructure + reserves + continuity (rare) → Citadel
- Business improvement district (commercial interface) → Business
- Revenue-generating org (services/products, payroll) → Business
- Membership commons org (club, mutual aid, association) → Community
- Infrastructure/endowment org (funds multiple groups, holds reserves) → Citadel
- Professional revenue interface (members sell under banner) → Business
- Membership standards + shared fund + mutual aid → Community
- Also manages infrastructure/reserves/continuity across cells → Citadel
- Consumer/buying club co-op → Community
- Worker co-op selling to outsiders → Business
- Housing co-op owning property + long-horizon reserves → Citadel (or Household if tiny and effectively shared living)
The same entity can span layers (e.g. a church as both Community and Business), but for design you should treat each layer’s behavior separately.
4. Quick classification tests
- Do people share daily life expenses and live together? → Household
- Do you sell goods/services to outsiders with invoices/refunds/payroll? → Business
- Is it a membership pool with churn + shared projects/commons? → Community
- Does it hold strategic reserves + infrastructure + continuity doctrine to survive coercion/isolation? → Citadel
- If none of the above and authority is unilateral (one person, no shared budget) → Individual
A “segment” is a functional subsystem required for a layer to remain sovereign under stress. Segments are mostly isomorphic across layers; what changes is scale, governance, redundancy, and external interface.
5. Segment modules (maximal functional list)
We use segment and module interchangeably here: each segment is one functional module. Together, these modules form a matrix with the layers above.
Design matrix In this map there are 22 modules that repeat across 5 layers → 110 distinct design surfaces. For every “Layer × Module” slot you can ask: “Do we own this, or is it outsourced to someone else?”
Below is a maximal module list: a superset of everything a layer might need to handle in a serious sovereignty context. Not every layer has to build each module from day one, but if a module is completely “blank”, it means someone else effectively owns it.
Fractal modules The same modules exist at the Individual, Household, Business, Community, and Citadel layer. The difference is: size of the surface area, governance model, legal exposure, and time horizon.
Core stack (applies to every layer)
How value is stored, moved, tracked, and risk-managed so the layer doesn’t get wiped by one shock.
- Store of value
- Payments
- Treasury policy
- Accounting
- Liquidity
- Credit/debt exposure
- Internal budgets
How signals move: talking, coordinating, publishing, and discovering without being trivially cut off or censored.
- Messaging
- Publishing
- Internal coordination
- Censorship resistance
- Discovery
Who is “us”, who is “not us”, and who can touch what—backed by actual keys and access, not just vibes.
- Identity primitives
- Authentication
- Authorization
- Roles
- Device access
- Key management
The actual machines and workflows that do digital work for the layer, with or without the internet.
- Local compute
- Storage
- Backups
- Workflows
- AI/agents
- Offline capability
How you avoid getting owned: by thieves, states, social engineering, or your own sloppiness.
- Threat models
- Physical security
- Cyber hygiene
- Surveillance resistance
- Coercion/duress posture
How promises are recorded, enforced, and repaired when things go wrong—inside or outside legacy courts.
- Rules
- Agreements
- Enforcement mechanisms
- Arbitration
- Records
- Restitution pathways
How decisions get made, who gets a say, and how power gets handed over or revoked without explosions.
- Decision processes
- Quorum
- Permissions
- Delegation
- Succession
- Anti-capture mechanics
How the layer structures time: recurring cycles, maintenance, audits, and emergency triggers.
- Calendars
- Rhythms
- Maintenance cycles
- Audits
- Drills
- Emergency triggers
- Ritual timekeeping
Why the layer exists at all: shared stories, values, and symbols that make sacrifice and discipline make sense.
- Shared values
- Morale
- Legitimacy
- Cohesion
- Rites
- Identity reinforcement
Material survival (physical sovereignty)
Everything here keeps bodies alive and functioning when abstractions fail. In practice, these are the modules that decide how bad “bad” can get.
Without energy, every other module quietly dies.
- Generation
- Storage
- Distribution
- Fuel logistics
- Redundancy
- Failure modes
Clean, reliable water is the hardest thing to fake long-term.
- Source
- Purification
- Storage
- Distribution
- Testing
- Sanitation coupling
Calories, nutrition, and buffering against supply shocks.
- Procurement
- Production
- Storage
- Cooking
- Nutrition
- Seed/preservation
- Supply resilience
The physical container: where you exist, sleep, and protect assets.
- Housing
- Heating/cooling
- Construction
- Maintenance
- Zoning/jurisdiction strategy (if applicable)
Keeping humans functional over time, not just alive today.
- First aid
- Chronic care plans
- Medicines
- Triage
- Biosecurity
- Mental stability
Where everything goes when you’re done with it—and whether it comes back as disease.
- Sewage/latrine
- Trash
- Compost
- Hazardous waste
- Disease prevention
Movement and exchange
These modules handle how people, goods, and relationships move through the world. They decide how “plugged in” or “cornered” a layer really is.
The ability to move people and assets when you choose to, not only when allowed.
- Vehicles
- Route planning
- Fuel/charging
- Maintenance
- Bug-out options
- Access constraints
How stuff gets from “out there” to “here” reliably.
- Inventory
- Warehousing
- Procurement
- Redundancy planning
- Vendor strategy
- Substitutions
How you touch the outside world: markets, allies, boundaries, and filters.
- Barter
- Markets
- Alliances
- Diplomacy
- Boundaries
- Filtering
Capability-building (anti-fragility)
These modules decide whether the layer gets weaker and more dependent over time, or stronger and more self-directed.
Who knows what, how they learn, and how that knowledge survives turnover.
- Skill acquisition
- Cross-training
- Drills
- Onboarding/offboarding
- Knowledge transfer
The difference between “we can fix it” and “we’re stuck until Amazon arrives.”
- Hand tools
- Spare parts
- Fabrication
- Maintenance regimes
- Local production capacity
Your relationship to the terrain and ecology you depend on.
- Terrain
- Soil
- Ecology
- Resource rights
- Hazard mapping
- Long-horizon sustainability
Everything you know, everything you’ve done, and how someone else could prove or repeat it later.
- Documentation
- Runbooks
- Receipts/contracts
- Lineage
- Audit trails
- “What we know and how we know it”
6. How to use this map in practice
- Pick your layer. Are you working on your own life, your household, a business, a community, or a citadel/enclave? Start with that layer.
- Classify the thing. Use the quick tests and “where common labels land” section to place what you’re looking at on the right layer.
- Walk the module list. For that layer, ask: “Who actually owns this module?” for Money, Comms, Security, Food, etc. If the answer is “the state / a corporation / nobody in particular,” you’ve found a sovereignty gap.
- Check out the full list of modules. Each module (not all of them yet) title has a recommended stack + toolchain.
- Scale fractally. Once one layer is coherent (e.g. Individual or Household), you can repeat the same module logic up a layer (Business/Community/Citadel) without reinventing the mental model.
The map itself is deliberately minimal and reusable. It doesn’t force a particular ideology: it works for legacy, fiat-heavy setups as well as Bitcoin-native, privacy-maximalist ones. The classification just makes dependencies and attack surfaces visible. The opinionated part lives in the module pages and stacks you plug into each box. That is where philosophy shows up.