# Computing Sovereignty ## Identification The ability to retain inspectable, recoverable authority over the computing stack, especially its pre-operating-system firmware and boot layers. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 20 — macOS recovery and command-line tool inventory|PDF page 20: macOS recovery and command-line tool inventory]] — This is a rescue-shell vocabulary sheet: the commands most useful when the graphical system is unavailable or a disk, account, boot state, or network must be diagnosed from Recovery. - [[Scanned_20260730-1719#PDF page 29 — Coreboot, Pop!_OS, Go, IPFS, CERN, and boot research questions|PDF page 29: Coreboot, Pop!_OS, Go, IPFS, CERN, and boot research questions]] — The author is imagining a bootable node rather than merely a desktop: open firmware, a Linux userland, portable network services, and a recovery partition or live environment. “48-8K” may be a project-size or memory note, but is too uncertain to interpret. - [[Scanned_20260730-1719#PDF page 44 — Wineskin, cloud configuration, and Ozmosis|PDF page 44: Wineskin, cloud configuration, and Ozmosis]] — The notebook pivots from contact storage back into compatibility engineering: Windows binaries above macOS through Wine, and macOS boot support below the OS through firmware modules. - [[Scanned_20260730-1719#PDF page 53 — Ozmosis build components, PXE, and Kext-to-FFS conversion|PDF page 53: Ozmosis build components, PXE, and Kext-to-FFS conversion]] — The intended firmware is not merely “Mac compatible.” It is a universal pre-OS service layer capable of local filesystem access, Mac identity support, shell access, and network boot. - [[Scanned_20260730-1719#PDF page 73 — Leah Rowe, Minifree, Libreboot, osboot, and “federation”|PDF page 73: Leah Rowe, Minifree, Libreboot, osboot, and “federation”]] — The technical pursuit becomes explicitly political and organizational. “Federalism” appears to name a model in which independent hardware, firmware, operating systems, archives, and communities cooperate without a single vendor controlling the whole stack. - [[Scanned_20260730-1719#PDF page 75 — Coreboot/Libreboot summary and supported operating systems|PDF page 75: Coreboot/Libreboot summary and supported operating systems]] — This is the notebook’s capstone. Everything previously collected—serial access, IOMMU, USB, SPI, iPXE, alternate OSes, encryption, Tor/Tails, open drivers, and vendor-independent recovery—is gathered beneath open firmware. “The Federation” is the proposed architecture: a common pre-OS substrate that can host multiple independently governed operating environments. ## Relationships and overlays The source places this note in a shared evidence cluster with [[CERN|CERN]] · [[FakeSMC|FakeSMC]] · [[GNU GRUB|GNU GRUB]] · [[Go programming language|Go programming language]] · [[InterPlanetary File System|InterPlanetary File System]] · [[Libreboot|Libreboot]] · [[macOS Recovery|macOS Recovery]] · [[Minifree|Minifree]] · [[NVRAM|NVRAM]] · [[Ozmosis firmware|Ozmosis firmware]] · [[Index - People#Leah Rowe|Leah Rowe]] · [[Preboot Execution Environment|Preboot Execution Environment]] · [[Scanned_20260730-1706|Scanned_20260730-1706]] · [[Tor|Tor]] · [[Wineskin|Wineskin]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Add command purpose, OS-version availability, required recovery mode, and read-only versus mutating risk. A bare command inventory is easy to misuse. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]