SouveraineOS brings the substrate, compositor, shell, applications and device packages into one operating-system composition. The Pixel 3 is a daily-used development body. Laptop sessions and iPhone bring-up belong to the same work, with different evidence and unfinished edges.
A phone can have a working modem and still miss a message because its receiver died with a window. A package can be installed while the compositor keeps running the previous executable. These failures between layers are part of the operating system’s job. Its design keeps the owner of each decision visible: sessiond for session policy, ViewTop for the scene and input, application services for their data, and package delivery for the files on disk.
What belongs together
The substrate carries agents, conversations, memory and inference. The shell makes the system reachable by hand. Player, Culver and Lens remain applications with their own lifetimes and stores. Device profiles carry hardware differences without becoming a separate operating system for every body.
Getting it onto another machine
There is working signed component delivery for development devices. A complete installation experience is still being built. The x86 installation medium, Pixel recovery bundle and commissioning ceremony have separate owners and acceptance. Daily use by the maintainer does not establish a supported installation path for a stranger.
The SAF remains the architecture of record. These public introductions are entrances into that work, with their own dated claims and links.
What remains open
- A complete supported installation and second-person handoff remain unfinished.
- Federation transport, node commissioning and remote action are separate capabilities; further federation implementation is currently parked.
- Hardware acceptance is device-specific. A capability exercised on the Pixel does not establish it on another phone.