Use it like this: choose one entry breach, then complete the constitutional trunk in order, then complete the live protocol trunk in order, then add annexes only by role, exposure, and mission.
This path now separates four different things that were previously mixed together: constitutional texts, live standards/specs, operator procedures, and role-specific hardening. Read accordingly.
Entry breach — choose one
- Monetary-civilizational breach: The Bitcoin Standard
- Institutional / anti-legibility breach: Seeing Like a State
- Technical scarcity / consensus breach: Inventing Bitcoin
- Duty / action / existential breach: Bhagavad Gita
- Media / authority / synthetic-reality breach: Technopoly
These breaches are not interchangeable. The Bitcoin Standard is the monetary-civilizational breach; Seeing Like a State is the institutional and anti-legibility breach; Inventing Bitcoin is the technical on-ramp; Bhagavad Gita is the action-and-duty breach; and Technopoly is the media-and-authority breach.
Constitutional trunk
I. Legibility, scale, transition, epistemic capture
- Seeing Like a State (skip here if chosen as entry)
- The Sovereign Individual
- Governing the Commons
- Technopoly
Purpose: destroy trust in schematic legibility, install civilizational transition awareness, block the fake state-versus-market binary, and add the media/technology authority layer.
II. Property, law, adjudication, post-state order
- Anatomy of the State
- Man, Economy, and State with Power and Market
- The Ethics of Liberty
- Law, Legislation and Liberty
- The Enterprise of Law
- The Machinery of Freedom
Purpose: install property, Austrian grammar, nonaggression, spontaneous order, non-monopoly legal order, and fully post-state institutional imagination.
III. Duty, action, field, node, restraint
- Bhagavad Gita (return pass here if chosen as entry)
- The Upanishads
- Tao Te Ching
Purpose: stop two corruptions at once: metaphysics being used to evade duty, and duty being used to forget ontic depth.
IV. Disorder, consequence, emergence
Purpose: expose the earlier law and metaphysics blocks to asymmetry, accountability, decentralization, and bottom-up production.
V. Cypherpunk constitutional layer
This pair is compulsory, not elective. Hughes gives the privacy axiom directly; Chaum gives the cryptographic design grammar for untraceable payments.
Live protocol trunk
Rule before entering this section: do not read specs as scripture. Read them as process artifacts, interoperability proposals, implementation guides, and living constitutional fragments under adversarial change.
VI. Bitcoin conceptual layer
- Bitcoin: A Peer-to-Peer Electronic Cash System
- How does Bitcoin work?
- Some things you need to know
- Secure your wallet
- Running a Full Node
This block installs the conceptual grammar: peer-to-peer cash without a trusted intermediary, blockchain as shared public ledger, key-based authorization, wallet responsibility, and validation.
VII. Bitcoin operator reality
This block exists because operator truth moves. Read the current Bitcoin Core site for live download/storage reality, and read the Bitcoin.org guide as conceptual orientation rather than the freshest source of hardware figures.
VIII. BIP process, wallet grammar, signing grammar
This is the correct order because BIP 3 is the active process frame, while BIP 32, BIP 39, and BIP 174 teach the wallet and signing reality you will actually encounter.
IX. Lightning: routed, enforced second-layer order
This block comes after Bitcoin fundamentals. It covers channel management, routing/discovery, authenticated transport, and invoice/payment encoding.
X. Nostr constitutional layer
A. Read the repository constitution first
- NIPs README: Criteria for acceptance of NIPs
- NIPs README: Is this repository a centralizing factor?
- NIPs README: How this repository works
This comes first because the repo itself tells you how to interpret everything that follows.
B. Base protocol + relay capability
C. Auth, signer separation, routing
D. Identity, encrypted payloads, private messaging
This block now sits inside the main line, not in a late side annex.
Role-based annexes
Operator / public-node / hostile-jurisdiction annex
Not universal. Near-mandatory for exposed operators, founders, organizers, visible writers, journalists, dissidents, high-signal node-builders, and anyone crossing adversarial jurisdictions.
Austrian cathedral annex
Not the doorway. Read only after the legal-economic spine is already installed.
Historical cyber-liberty annex
Read as historical signal, not as current infrastructure doctrine.
Public-community governance annex
This is not base constitution; it is the community/public-governance branch.
Comparative metaphysics / mediation / memory annex
- Corpus Hermeticum
- Nag Hammadi selections
- 1 Enoch
- Egyptian funerary / maat texts
- Melchizedek / Second Temple materials
This annex is for mediation, distortion, recurrence, memory architecture, and sorting under veil. It is not allowed to precede law, protocol, or duty.
Clean order
Choose one entry breach:
Then do the constitutional trunk:
- Seeing Like a State (if not already read)
- The Sovereign Individual
- Governing the Commons
- Technopoly
- Anatomy of the State
- Man, Economy, and State with Power and Market
- The Ethics of Liberty
- Law, Legislation and Liberty
- The Enterprise of Law
- The Machinery of Freedom
- Bhagavad Gita (return pass if chosen as breach)
- The Upanishads
- Tao Te Ching
- Antifragile
- Skin in the Game
- The Cathedral and the Bazaar
- A Cypherpunk’s Manifesto
- Blind Signatures for Untraceable Payments
Then do the live protocol trunk:
- Bitcoin: A Peer-to-Peer Electronic Cash System
- How does Bitcoin work?
- Some things you need to know
- Secure your wallet
- Running a Full Node
- Bitcoin Core download page
- Bitcoin Core requirements and warnings
- Bitcoin.org full-node guide
- BIP 3
- BIP 32
- BIP 39
- BIP 174
- Mastering Bitcoin
- Mastering the Lightning Network
- BOLT 0
- BOLT 2
- BOLT 7
- BOLT 8
- BOLT 11
- NIPs README: Criteria for acceptance of NIPs
- NIPs README: Is this repository a centralizing factor?
- NIPs README: How this repository works
- NIP-01
- NIP-11
- NIP-42
- NIP-46
- NIP-65
- NIP-05
- NIP-44
- NIP-17
Then add annexes by role:
- Extreme Privacy
- Human Action
- A Declaration of the Independence of Cyberspace
- NIP-72
- Corpus Hermeticum
- Nag Hammadi selections
- 1 Enoch
- Egyptian funerary / maat texts
- Melchizedek / Second Temple materials
Governing rules
- Books build judgment.
- Specs build interoperability literacy.
- Operator docs build reality contact.
- Privacy manuals build survivability.
- No standards repository is a throne.
- Reading alone is insufficient.
This is the architecture: anti-legibility, property, voluntary law, duty, cypherpunk privacy, protocol literacy, routing, signer separation, and operator survivability.