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”| Body | State | What that means |
|---|---|---|
| Pixel 3 | exercised on glass | The daily-use reference body. It proves the session, shell, package delivery and hardware integrations on a real mobile device. |
| iPhone 7 | active bring-up | Its owned boot chain, storage, tether and Souveraine session are real. Parts of the display and input path remain explicitly experimental. |
| HP ProBook 450 G6 | SouveraineOS on x86 | Casey’s x86_64 EndeavourOS workstation is the current SouveraineOS laptop body. Its formal hardware profile and installer path are being completed this week. |
| Apple silicon | planned | The next laptop transfer of the same contract. No M1 device profile or installer exists yet. |
| A5–A11 Apple mobile | hardware access established | Checkm8-class boot access opens iPhones and iPads in this range. Each device earns its body row with its own profile and hardware evidence as the family comes online. |
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.
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.