Skip to content
Souveraine

Bodies and hardware

SouveraineOS calls a hardware target a body. A body has a boot path, a device profile and an evidence record. It does not get its own copy of the session, shell or agent substrate merely because its silicon differs.

Current bodies

Section titled “Current bodies”
BodyStateWhat that means
Pixel 3LIVEThe daily-use reference body. Session, shell and signed package delivery run on glass; calls, SMS and mobile data have been exercised on hardware.
iPhone 7PARTIALIts owned boot chain, NVMe root, tether, display and Souveraine session reach glass. It is host-tethered; touch events, Wi-Fi, modem and battery integration remain open.
HP ProBook 450 G6PARTIALCasey’s x86_64 EndeavourOS workstation runs the substrate and shell. A formal hardware profile and installer path do not exist yet.
Apple siliconDESIGNA possible laptop transfer of the same contract. No M1 device profile or installer exists.
A5–A11 Apple mobileDESIGNCheckm8-class access makes this a research direction, not a support matrix. Each exact device must earn its own profile and hardware evidence.

The exact capability matrix stays in the SouveraineOS device record. This page states the public boundary; it does not flatten experimental hardware into a compatibility badge.

Pixel 3 blueline

Section titled “Pixel 3 blueline”

The current running-device claim is narrow and concrete: the Pixel 3 daily-runs Casey’s mainline-derived Linux 7.1.1 kernel with calls, SMS and mobile data working on the physical phone. Those capabilities did not arrive through one patch:

  • Modem and data. The QMI DeviceNotReady (52) wall was traced to the missing modemsmem path that populates SMEM item 134. Adding Richard Acayan’s existing driver port and the blueline device-tree node brought the modem online and LTE traffic followed. The public modem record captures that stage; it predates the later call and SMS work.
  • Calls. The running audio path has carried a real two-way call, confirmed at both ends. The July 29 field record records that work.
  • SMS. Text messaging works on the running body. MMS is a separate boundary: a manual end-to-end send has worked, while automatic lifecycle and receive remain unfinished.
  • SLIMbus. A Qualcomm DEF_ACT_CHAN encoding correction was submitted for upstream review. It made no immediate behavioral change on blueline and is not evidence for the modem, call, SMS or microphone results above.

The public modem record, field notes and upstream thread prove different parts of this account. None is presented as independent verification of all four.

The rule

Section titled “The rule”

Device packages carry facts such as a kernel, boot assets and board quirks. The common base handles policy. When a shared component assumes one board, that is a bug to remove—not a reason to mint -pixel and -iphone variants of every service.

This distinction makes hardware progress honest and portable: new bodies join by gaining a declared profile, not by copying a laptop-side ritual.