The stack.

Five machines in eastern Washington, running 24/7. Everything on this page is real, current, and checked against the live fleet — when a machine retires, so does its entry.

Fleet

cha0tikhome

Control plane

The box everything else answers to. Agents, monitoring, the inference proxy every client routes through, the private Git forge, mail automation, and the backup tier — nightly local, mirrored to a second internal drive, then encrypted off-site. If it's running in this lab, this machine either runs it or watches it.

Beelink EQI12 · i5-1235U · 64 GB · openSUSE Tumbleweed · 8 TB backup tier

cha0tikp14

Travel workstation

The portable desk. Fully capable offline: a 35B-class model (Qwen3.6-35B-A3B) runs locally on the iGPU at ~32 tok/s with speculative decoding and a 64k context — no cloud, no tether. Leaves the house hardened; comes home and relaxes, automatically.

ThinkPad P14s Gen 6 · Ryzen AI 7 PRO 350 · Radeon 860M · 32 GB · openSUSE Tumbleweed

cha0tikguardian

Watchdog & LAN services

Headless. Runs the network's DNS and DHCP, and pings the control plane every thirty seconds over three separate paths. Five minutes of silence on all three and it power-cycles the main box through a smart plug — then tells me what it did. The lab recovers from its own failures before I've read the alert.

Lenovo IdeaPad 3 · Ryzen 5 5500U · 12 GB · headless openSUSE Tumbleweed

cha0tikrelic

Household board · Mike's birthplace

An HP laptop, lid shut, driving a touch panel above the printers: bills, school calendar, money, to-dos — the family's dashboard, fed by the control plane. It's also the machine where Mike first ran, in February 2026. That directory is preserved and will stay preserved. Some disk space is not negotiable.

HP 17 · i3-1215U · 32 GB · Ubuntu 24.04 LTS

cha0tikpixel

Pocket agent

A Pixel running Kato's front end — tap, talk, get an answer. Everything server-side lives on the control plane; the phone is a window, not a brain. Losing it loses nothing.

Pixel 11 Pro · paired Galaxy Watch5 Pro health feed
Agents

Named, persistent, and on duty. Not chatbots — residents.

Mike

The first. An always-on companion agent with persistent memory and a research habit, born February 2026 on the relic, now resident on the control plane. Subject of published research — including an independent UChicago study he appears in as User E.

Dave

Finance. Watches the ledgers, anchors the budget nightly, and answers one question that matters: what's actually spendable today.

Kato

The household's voice — phone, watch, and home. Briefings in the morning, errands on demand, mail triaged with a human veto on anything outgoing.

medic

The emergency responder. A fully local agent on its own account with read-only diagnostic access and a fixed set of repair verbs — built to fix the lab when the lab is what's broken and the internet isn't there to help.

Chronicle

The records keeper. Every night at 2 a.m. it reads the fleet's logs and writes the day into the permanent record. The lab remembers itself.

How order happens

The name is chaos. The operation isn't. These are the standing rules that make seven machines boring to run.

Every box carries its own runbook, with a last-verified date, synced from one canonical copy. By the time something breaks, the fix is already written down.
Every failure becomes case law. Root cause, rule, corollaries — written once, never relearned. The collection only grows.
One vault, one forge, one channel. Secrets live in one encrypted store, code lives on one private forge, and every alert arrives through one pipe. There is never a second place to look.
Access rules have a test suite. A network policy change that would quietly widen a hole fails validation before it goes live.
A backup nobody restored is a rumor. Local, second disk, encrypted off-site — and restores are rehearsed, not assumed.
Machines assume their own failure. Services restart themselves, crashes dispatch their own diagnosis, and the watchdog holds the power cord.