Two halves · one man
Drag the seam between the two halves — or choose plainly.
Don’t take my word for it.
No analytics. No fingerprints. Only what you choose to leave.
The machine underneath
A mainline-derived Linux 7.1.1 kernel runs the phone. The operating system, lock authority, compositor, package path and agent substrate form one body with evidence and limits attached.
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.
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.
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.
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.
The live engineering record
Current work · August 25, 2026
Subjects and systems here; timestamps, hashes, publication state and the uncurated record one click deeper.
Private work also moved. Names and activity counts stay private.
Who I am
I've worked as a Senior NOC tech, CISO, network engineer, field responder during major cyberattacks, and IT on yachts. That work built the operational instincts underneath the systems I make now.
Private engagements include a 150-server ransomware recovery and zero-downtime migrations across more than 2,000 endpoints. References can corroborate the work that cannot be linked publicly.
I'm in Hamilton, Ontario, running a homelab, and putting most of my hours into the things that matter — mobile Linux, systems that remain locally ownable, and an agent substrate that treats identity, memory and authority as engineering problems. Samaritan is where the work leaves my hands.
I wear a wizard hat. Unironically. I have a tuxedo cat and a canary and a wife who is more interesting than my LinkedIn ever was.
The archive
“The list of things I can't talk about continually is growing larger — and in tomorrow's world that's going to be evermore so.”
I've been documenting political and civil rights concerns since late 2024 at caseytunturi.com/witness — methodically, without performance, because someone has to. History written by those paying attention is different from history written after the fact.
Read the archiveReach Casey
Saw the machine and want me in the room?
Choose the reason. Dispatch reaches me directly.
