A peek at each
Not the whole thing. What each one is for, what it taught me, and where it stands. Infrastructure details stay home.
The SQ5 garage
A 2025 Audi SQ5, logged five times a second through a reverse-engineered cable and a Pi in the footwell. Build log, lessons, and a weekly health card the car writes about itself.
Alert board
A board built by cron, four hook rungs, an acknowledgement ledger with five verdict words, and a headless responder for the hours nobody is typing.
PHOSPHOR wall
A portrait screen on the wall that is the alarm surface for everything else. It latches red until a human clears it, on purpose, and reads from the hallway.
Memory as infrastructure
The agent's memory is a directory of one-fact files with a linter, an index whose lines are triggers rather than summaries, nightly verification against the machines, and git for history.
fleet-patch
A fortnightly patch cycle for a small Proxmox fleet, graded on evidence of what actually updated rather than on the schedule having run.
partswatch
Watches classifieds every fifteen minutes and fifty-odd store prices hourly for a wanted-parts list, and sends one message when something moves. The part matters, not the store.
lanwatch
Internal traffic versus traffic that leaves the house, as two different facts, because a home network full of IoT devices should have to explain itself.
jackal-protocol-re
Reverse-engineering a proprietary automotive diagnostic cable: USB capture, frame recovery, checksums across 285,832 frames, and the signed-channel bug that made a million readings silently wrong.
Crucix
A personal intelligence agent that watches several data sources and pings when something changes. A fork I run and extend.
meanwhile
Horizontal matrix rain where live news and true facts decode out of the code. Zero dependencies, one file.
Built with Claude Code
Claude Code has been part of the work behind these projects. Usage recorded in its transcripts since 2026-07, deduplicated:
Counted by tools/tokens.py. Streamed messages are deduplicated; a session's tokens are split evenly across the project folders it touched. Private projects are summed, never named. Totals include cache reads; these are usage counters, not unique generated words or a cost estimate.