Pixel3Arch owns the implementation that brings Linux onto the Pixel 3: the kernel tree, hardware packages, root filesystem integration, boot assembly and device tools. The living hardware record is owned by SouveraineOS.
Calls, SMS and mobile data have been exercised on the maintainer’s daily phone. Display, audio, touch, sensors, USB and charging each have their own integration and evidence. Fixing one transport or route does not establish every telephony or audio path.
Delivery is part of device support
Signed packages update an existing development phone. Root filesystem overlays serve provisioning and do not automatically change an already-running device. A package can reach disk while its old process remains active, so installation and activation are recorded separately.
A second phone is a different test
The recovery inventory, root filesystem bundle and per-device calibration boundary are work toward an installation path another person can use. A daily working phone does not prove a safe recovery executor or a fresh installation on another unit.
What remains open
- The reproducible Pixel installation bundle, recovery executor and second-person handoff remain unfinished.
- Hardware capabilities require exact-device evidence; factory calibration must not be copied between bodies.
- The repository composes upstream software with component-specific licenses rather than declaring one blanket license.