Two halves · one man

Casey Tunturiarcane & algorithmic

Casey Tunturi — the manCasey Tunturi — the work
Learn morethe man
Inspectthe work

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

From kernel to cognition.

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

Linux / Qualcomm / Pixel 3

LinuxQualcomm SDM845QMISMEM item 134SLIMbus

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

SouveraineOS

Arch Linuxdevice profilesuserspace daemonshardware integration

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.

Session authority · compositor

sessiond ↔ ViewTop

RustSmithayWaylandDRM/KMSPAM

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.

Agent substrate · upper layer

Souveraine

RustGit-backed memoryEd25519local inference

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

The path onto the body

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.

  1. source
  2. candidate gate
  3. target build
  4. package
  5. signed archive
  6. pacman / updater
  7. package-owned device

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

Authority and provenance recur elsewhere.

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

RedFlag

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

Statelog

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.

Current work · August 29, 2026

The latest shape.

Subjects and systems here; timestamps, hashes, publication state and the uncurated record one click deeper.

rootfssqueekboard
  • Pixel3Archrootfs: select the phone lock before config

Private work also moved. Names and activity counts stay private.

The dated record carries the proof.Open the full day →

The models came late.
The man was already here.

I was making house calls by 2006 and doing professional technical work by 2009. Casey’s Computers later served more than 1,200 distinct customers. People, not tickets.

The failures widened: hotels, farms, hospitals, fire departments, schools, industrial sites, MSP estates, and datacenters under attack. The chronology keeps the long record and its uncertain edges.

In August 2026, I followed an HP all-in-one’s missing analog audio into the Linux HDA controller and sent the fix upstream. The stack keeps getting lower.

I live in Hamilton with my wife, a tuxedo cat, and a canary. I wear the wizard hat unironically. Both halves live here.

  • On technologyTools should serve the person holding them — not extract, not surveil, not create dependency.
  • On AIAn agent is not a warhorse. Presence is earned. Memory is sovereign. Choice is real.
  • On the webThe free, open web is worth fighting for. Services like this should always be free and accessible.
  • On bearing witnessWhen history is being made badly, someone has to write it down. That's not optional.
⋆ ✦ ⋆

“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 archive

Want me in
the room?

Saw the machine and want me in the room?
Choose the reason. Dispatch reaches me directly.