resources
kernel / manuals / field specs / self-audits
This is the kernel + manuals layer of Sov Stack Architecture.
Where the Sov Stack Atlas maps tools, environments, and ecosystems, this page gathers the texts, maps, surveys, and field manuals that define the practice itself—and let people run serious sovereignty work on their own stack without ever commissioning architecture.
Roughly:
Kernel → Atlas → Manuals → Client deployments
This page lives in the Kernel + Manuals band:
- Kernel: primary texts, declarations, whitepapers, philosophical and legal cores
- Manuals: design specs, playbooks, self-audits, and schematics for citadels, nodes, aid cells, and narrative work
- Maps: reading maps, curriculum, jurisdictional maps, and threat framings
Some core resources appear in multiple sections because they cut across domains—architecture, health, narrative, education. Duplicates are intentional.
Use this page to study the underlying law-core and threat model, run self-audits before or instead of working with me, borrow specs and patterns for enclaves or projects, and treat Sov Stack Architecture as a discipline rather than a brand.
If you want to know which tools to use, start with the Sov Stack Atlas. If you want to know how to think and build like an architect, start here.
Core texts that define the ontology, threat model, and philosophical substrate.
- bitcoin white paper — the original specification of Bitcoin, treated here as legal and mythic precedent, not just technical artifact
- a note on ai — AI framed as governance substrate and Synthetic Stack enforcement lattice rather than a neutral tool
- The “Beyond Money” Whitepaper — Bitcoin as civilizational integrity kernel and substrate for law, property, and myth
- Bitcoin Sovereignty: Real, Synthetic, and the Space Between — framework for distinguishing genuine sovereignty from dependency costumed as sovereignty
- You’re Not Sovereign — forensic audit lens for stacks that still rely on brokers, SaaS, and single-jurisdiction chokepoints
- The Sovereign Stack Primer — main upstream reference for Sovereign vs Synthetic vs Resistance stacks
- Sovereign Metaphysics — field/node metaphysics, law, flesh, and stack interaction
Higher-level maps, indexes, and schematics for stacks and standards.
- bitcoin toolstack index — a Bitcoin-specific sub-atlas feeding into the broader Sov Stack Atlas
- Sov Stack Curriculum — study map across economics, metaphysics, threat, infra, and law
- SovStack Health Resource Library — health, resilience, trauma-aware practice, and capacity for individuals and nodes
- Sov mediums — medium-as-law analysis through the McLuhan lens
- sov map — experimental terrain sketch of sovereign jurisdictions; not legal advice
- Austrian Economics Guide — economic logic layer of the stack and its completion through Sovereign Recursion
Layered privacy protocols for practical use.
Self-audits to run your own capture map and integrity checks.
The link index below is the working library for this page. Some texts cut across multiple domains. The list remains intentionally broad and uneven; it records the current public corpus rather than a final canon.
- bitcoin white paper
- a note on ai
- bitcoin toolstack index - (what i gather to be) the best bitcoin tools
- sov mediums - looking at everything through the lens of marshall mcluhan
- 7 layer privacy stack - recommended privacy protocol. easy to follow along
- sov map - interactive map of some sovereign jurisdictions. click on each dot for more. experimental for now. also zooming out on your browser settings helps
- the problem - an analysis of 'the problem' through many lenses
- declaration of independence of the sov stack
- sovereign readiness & synthetic exposure survey — experimental, 0 data collected. A gentle first-pass self-audit for newer people.
- sovereign integrity audit — a deeper self-test for people who already consider themselves at least somewhat sovereign. Experimental, 0 data collected.
- Bitcoin Sovereignty: Real, Synthetic, and the Space Between
- You’re Not Sovereign: A Forensic Framework for Bitcoiners Who Think They Are
- Sovereign Health Guide
- Sovereign Nostr Operations Manual
- Austrian Economics Guide
- The “Beyond Money” Whitepaper: Bitcoin as Substrate, Not Endpoint
- DECLARATION OF SOVEREIGN FINANCIAL RIGHTS AND LIMITS ON STATE POWER OVER MONEY, CODE, AND DATA
- Some [More] Declarations Regarding Bitcoin Sovereignty
- Our Language Constraints
- FAMILY SOVEREIGN INHERITANCE KIT
- Stories & Archetypes We Do Use
- The Sovereign Stack Primer: Synthetic vs Resistance vs Sovereign
- SMALL ENCLAVE / CITADEL DESIGN MANUAL
- THE NARRATIVE SOVEREIGNTY MANUAL
- The Flesh-Law Whitebook: Nervous System as API. Sovereignty as Protocol.
- Ritualized Collapse & Succession Spec: For sovereign / cypherpunk / Bitcoin-aligned projects, orgs, nodes
- Local Sovereign Node Design Manual (similar to Enclave/Citadel Manual, but slightly different)
- Sovereign Aid Cells Blueprint
- Bridge Interface Blueprint (ties in together with, but not limited to, Sov Aid Cells)
- Sovereign Health Cells Blueprint
- Sovereign Metaphysics
- Sov Stack Curriculum — a sovereignty-heavy educational map.
- SovStack Health Resource Library
Patterns and specs for enclaves, nodes, inheritance, and core functions.
- SMALL ENCLAVE / CITADEL DESIGN MANUAL — physical and social architecture for small citadels and enclaves
- Local Sovereign Node Design Manual — node design for families, micro-cells, and local organizers
- FAMILY SOVEREIGN INHERITANCE KIT — transmitting keys, law, memory, and story without recreating capture
- Sovereign Aid Cells Blueprint — aid cell structure, security, exchange, and anti-NGO guardrails
- Bridge Interface Blueprint — interfaces with outside systems while minimizing capture and burnout
- Sovereign Health Cells Blueprint — health and care cells with explicit anti-capture guardrails
- Ritualized Collapse & Succession Spec — clean shutdown, handover, and death protocols for projects and nodes
- Sovereign Nostr Operations Manual — operational patterns for relays, clients, keys, topology, and info hygiene
Law-core and language scaffolding: declarations, rights, and constraints.
- DECLARATION OF SOVEREIGN FINANCIAL RIGHTS... — formal framing of financial, digital, and cryptographic rights under this model
- Some [More] Declarations Regarding Bitcoin Sovereignty — additional legal and symbolic declarations for Bitcoin as substrate
- declaration of independence of the sov stack — foundational declaration distinguishing Sov from Synthetic and Resistance stacks
- Our Language Constraints — language as law, boundary, and property rather than neutral description
Myth, narrative, and ritual treated as part of the operating system rather than decoration.
- Stories & Archetypes We Do Use — which archetypes we can and should encode into stacks
- THE NARRATIVE SOVEREIGNTY MANUAL — reclaiming, designing, and defending narrative infrastructure
- The Flesh-Law Whitebook — nervous system and fascia as infrastructure; trauma, regulation, and capacity as law
- Ritualized Collapse & Succession Spec — cross-listed because ritual, law, and shutdown fuse here into one pattern
- Sovereign Metaphysics — cross-listed because field/node metaphysics shapes architecture directly
Framing the problem and the wider civilizational gameboard.
- the problem — multi-lens analysis across functional, symbolic, economic, technological, and spiritual dimensions
- The Sovereign Stack Primer — core triad model of the three active civilizational stacks
- Bitcoin Sovereignty: Real, Synthetic, and the Space Between — especially relevant for people stuck in Synthetic Bitcoin land
- You’re Not Sovereign — diagnostic hammer for sovereignty claims resting on Synthetic infrastructure
Stacks fail at the body and care layer first. These resources make that explicit.
Practice-level specs governing how work, money, and data are handled.
- Medium of Exchange Spec — accepted exchange media, markups, BTC parity, and decay across conditions
- Returns Guide — refund logic, milestones, cooperation expectations, and exclusions
- Threat Model & Scope — what the practice does and does not defend against
- Data Handling & Retention Policy — how notes, intake, and artifacts are minimized, stored, or destroyed
These documents sit at the intersection of kernel, law, and operations: how the practice treats money, risk, and data in line with its own standards.
Suggested entry paths:
- new to the frame — start with The Sovereign Stack Primer, Bitcoin Sovereignty, and You’re Not Sovereign, then skim the Sov Stack Atlas
- want to self-audit first — begin with the readiness survey, then the integrity audit, then cross-reference manuals and the Atlas
- designing enclaves / nodes / projects — go to the enclave manual, node manual, inheritance kit, aid cells blueprint, bridge interface blueprint, and health cells blueprint, then pull tooling from the Atlas
- teaching or building your own practice — work through the curriculum, Austrian Economics Guide, Sov mediums, narrative manual, and Flesh-Law Whitebook
- engaging the practice as a client or collaborator — read the Medium of Exchange Spec, Returns Guide, Threat Model & Scope, and Data Handling & Retention Policy, then move to Offerings
Everything here is treated as field code, not scripture.
If serious flaws or blind spots are found in any of these specs, guides, maps, threat models, or legal- and health-adjacent documents, the default stance is:
- patch the design
- note the change and deprecate the old version
- credit the critique
- where appropriate, tip sats
Adversarial review is part of the operating model, not an exception.