Systems · evidence · limits
The AI is up here. Everything beneath it had to exist first. Pick a claim, descend through its mechanisms, and leave Casey’s sites whenever an outside artifact exists.
Identity, memory, sensorium and inference live here.
A Rust substrate for a persistent agent across machines and time. It is the top layer of the work, not the category that explains everything beneath it. The public design and checked source projection can be inspected; canonical internal history and private deployment state remain private.
Operating system · active on hardware
A mobile Linux OS composition running on real phone hardware.
The composition owns device profiles, package delivery, session and device authority, the compositor path, and the hardware contracts around the agent substrate.
The decision to lock and the presentation of a lock are separate facts.
sessiond owns policy and requests the transition. ViewTop owns the Wayland protocol and whether the lock surface exists. A dark panel is not accepted as proof of a locked session. ViewTop is the Pixel 3's daily session compositor, with Hyprland absent from that device's session path; its in-process Flutter seam remains unfinished.
Kernel and device · external trail
The daily Pixel 3 runs Casey's mainline-derived Linux 7.1.1 kernel with calls, SMS and mobile data.
The QMI 52 modem wall fell when the device kernel gained the missing modemsmem path for SMEM item 134; calls and SMS were completed through later telephony and audio work. A separate Qualcomm SLIMbus encoding correction was submitted upstream and made no immediate change on blueline.
Upstream work · public review records
These are public review submissions, not accepted or merged work. Each entry keeps its own scope and evidence.
Qualcomm SLIMbus / Pixel 3
August 7, 2026 · Submitted for upstream review
A separate encoding correction for Qualcomm SLIMbus. Its review status does not establish acceptance, merge status, or the later Pixel telephony and audio work.
ALSA / Intel HDA / HP ENVY 27-p014
August 28, 2026 · Submitted for upstream review
On HP subsystem 103c:2b3e, normal HDA enumeration found HDMI but left the CX20753/4 analog codec at address 0 absent. A board-specific second CRST pulse wakes it, with immediate commands used only while cad0 is created before CORB/RIRB resumes; the reset is repeated before codec resume. Boot, analog capture, and four deep suspend/resume cycles were exercised before submission.
This is the failure behind a familiar HP ENVY 27-p014 Linux-audio search: Intel 100 Series HDA controller 8086:a170, snd_hda_intel loaded, HDMI devices visible, and the built-in Bang & Olufsen analog speakers absent. PipeWire or PulseAudio can route only the devices ALSA receives; hdajackretask, mixer settings, module parameters, and a reinstall cannot configure an analog codec that the controller never discovered.
Independent EndeavourOS report ↗ In 2022, an owner identified the HP ENVY 27-p014 / 2B3E board, reported the same 8086:a170 / 103c:2b3e controller tuple, and showed only HDMI playback devices. They had already tried multiple distributions, alsamixer, output changes, and hdajackretask; a later fresh installation still showed only the Intel Skylake HDMI codec. This independently corroborates the model, subsystem, and symptom; it is not a test of this patch on that machine.
A distributed authority contract
SouveraineOS separates the authority that decides the device must lock from the compositor that presents and attests the locked surface.
Decision · policy · PAM conversation
It consumes sensor and user evidence, applies session policy, requests lock, and waits. It cannot turn its own request into observed truth.
Protocol · pixels · acknowledgement
It owns the Wayland lock protocol and reports whether the secure surface is actually present. It does not silently invent session policy.
request ≠ presentation ≠ observed state. A dark display is not proof of a locked session.
Build · sign · deliver · own
The release path is part of the operating system. A successful local build is evidence of source; package ownership and an update path are what make it maintainable.
Software distribution · package ownership
A hand-copied binary can demonstrate an idea. It cannot demonstrate a system. Components travel through the declared package path before the operating system owns them.
Current boundary: the component delivery path is working; this is not yet a complete installable distribution. Producer-side manifest enforcement, ready device profiles and immutable public version releases remain open.
Same hands · different pressure
RedFlag and Statelog are separate systems. They expose the same preference for bounded power, explicit state and evidence that survives inspection.
Fleet security · public source
A package version waits fourteen days by default before the install path will take it.
On DNF and APT, RedFlag dry-runs the transaction, checks every pinned closure entry against OSV, and requires an Ed25519-signed, agent-bound capability before mutation. Its privileged Rust helper rechecks version, validity, identity, signature and replay state, then executes one fixed argv plan with a cleared environment. The current helper is not network-isolated; dependency hashes that cannot be resolved from signed repository metadata can be omitted. Docker, Winget and Windows Update remain on the default-strict signed-command path.
Custody and provenance · running system
A public record that keeps evidence separate from its interpretations.
Raw responses are content-addressed and never rewritten. A new parser writes a new derivative beside the old one. An unchanged fetch still records an observation. The source and raw custody repositories remain private by design.
External review · archived predecessor
Casey put a Matrix adapter into LettaBot’s review process, marked it draft after his own audit, accepted three additional blockers from a maintainer, and corrected them. The maintainer later approved the architecture and E2EE direction while still asking for a rebase and tests. A later configuration report returned the pull request to draft before Letta deprecated and archived the repository. Its open state is frozen history, not current pending work.
Casey’s account of the lineage: his LettaBot deployment already carried the N+1 primary/subconscious pattern. When Letta stopped developing LettaBot, he moved that architecture into Souveraine rather than abandoning the work with its host project.