Systems
What everything actually runs on, 3 machines in a house, and 5 managed platforms doing the parts that are not worth owning.
Conceptual by construction. The content schema runs every string on this page past a check that refuses IP addresses, internal hostnames, ports, remote-access URLs and anything shaped like a credential, so the architecture is publishable and the attack surface is not. That is a build failure rather than a review comment, because review is a person remembering and this failure mode is quiet.
Inventory8
- RUNNING
Apple platforms
PLATFORM · Managed and on-device
Where the native side of the lab runs: on-device inference, sync without a server, and distribution that does not need one either.
- CloudKitSync for Collect with no backend to operate, which is the reason it has survived without maintenance.RUNNING
- On-device modelsInference inside Aeroslip that never leaves the phone, so there is no per-request cost and no network path to fail.BUILDING
- The trade is real: no server to run, and no way to change behaviour without shipping a build through review.
- RUNNING
GitHub
PLATFORM · Managed
Source of truth for every repository in the lab, and the scheduler for the jobs that keep generated content fresh.
- RepositoriesThe lab's roster, published and held back alike, asserted by a test so the count cannot quietly drift.RUNNING
- ActionsCI on every push, the contribution-calendar refresh, and the post-deploy production check.RUNNING
- Action logs on the public repository are public. Nothing that identifies an account or carries a token is printed into them.
- RUNNING
House network
NETWORK · The house
The physical layer under everything else: the electrical panel, thirteen Cat6 home runs to one rack, and UniFi on top.
- PowerA 200A panel with arc-fault and GFCI breakers, the knob-and-tube gone, and dedicated circuits for the office and the rack.RUNNING
- Structured cablingThirteen Cat6 home runs in a star to one rack, through a keystone patch panel and a brush panel, every run labelled with one ID at both ends.RUNNING
- Gateway and switchingA UniFi gateway and a 24-port PoE switch that powers the access points and cameras.RUNNING
- Wi-FiThree ceiling access points inside and a mesh point outside, each on its own home run.RUNNING
- UniFi ProtectCameras and doorbell on PoE, recorded locally. Counts and placement are deliberately not published.RUNNING
- HomebridgeOn a Raspberry Pi, bridging Protect into HomeKit.RUNNING
- Labelling both ends of a cable with the same ID is free while it is in your hand and expensive forever after.
- RUNNING
Media pool
STORAGE · The house
Four spinning disks pooled into one tree with mergerfs, one of them given over to SnapRAID parity. Where the lossless library and the backups live.
- mergerfsPools the data disks so the library is one tree. Its create policy now picks the disk with the most free space, not the one where the folder already exists, which would have filled one disk while the others sat empty.RUNNING
- SnapRAID parityRecovery for a dead data disk. The scheduled sync was the crash trigger on bad memory, so it was switched off until the RAM was replaced, and the parity resync is the open item.BUILDING
DEPENDS ON proxmox · THE PROJECT →
- Parity that has not been synced protects nothing added since. This page says so rather than calling the array healthy.
- RUNNING
Notion + Super.so
PLATFORM · Managed
The publishing platform behind the writing sites: Notion is the editor and the database, Super renders it as a real site, and a CDN carries the shared brand layer across both.
- NotionWhere the writing actually happens, so publishing is not a separate act from drafting.RUNNING
- Super.soRenders the Notion tree as a site with custom CSS, which is the whole reason this stack survives contact with taste.RUNNING
- CDN-hosted brand layerOne stylesheet served to both sites, so a brand change is a single file rather than two copy-pastes.RUNNING
- The trade is honest: almost no engineering, and a hard ceiling on what the pages can do. For writing, the ceiling has not been hit.
- RUNNING
Proxmox node
COMPUTE · The house
The one machine everything self-hosted runs on. A single node, not a cluster: a consumer board, a 4-core APU, NVMe for guests, and the media pool hanging off it.
- PlexIn a container, with the APU's integrated GPU passed through for hardware transcode. Serves the lossless library to Plexamp.RUNNING
- SambaExports the media pool to the rest of the house.RUNNING
- Guest backupsvzdump on a schedule, restored from rather than merely configured. Written to the parity disk so they add no load to the array.RUNNING
- Host config backupA nightly tarball of the hypervisor's own configuration, because vzdump backs up guests and nothing else.RUNNING
- Alert relayOutbound mail through Resend, so the box can tell someone it is failing. It spent eighteen months unable to.RUNNING
- Hardware watchdogThe chipset's own timer, which fires even when the kernel is wedged. The default software watchdog could not.RUNNING
- Offsite backupRestic to object storage, so a dead house is not a dead library.PLANNED
- Minecraft serverA container for the kids' world. Capacity is not the problem; the RAM swap came first.PLANNED
DEPENDS ON house-network · THE PROJECT →
- Conceptual only. Addresses, ports and hostnames are refused by the content schema rather than left to a reviewer to notice.
- It ran on failing non-ECC memory for eighteen months without a single machine check exception. The postmortem is in the notes.
- RUNNING
Supabase
SERVICE · Managed
Postgres, auth and realtime for Stagger, the one project here with live multi-user state to keep consistent.
- PostgresNine tables, row-level security on all of them, and the drinks ledger's one real rule enforced as a check constraint rather than a promise in application code.RUNNING
- RealtimeStandings recompute from raw rows and push to every phone over a websocket, so nothing polls.RUNNING
- Realtime rejects the newer publishable key and fails silently; the live leaderboard needs the legacy anon JWT. That cost an evening and is written down here so it costs nobody else one.
- RUNNING
Vercel
PLATFORM · Managed edge
Production for zckr.dev. A push to the default branch is the deploy; there is no other release step and no runtime to babysit.
- Static hostingEvery page on the site is generated at build time and served as a file.RUNNING
- Serverless functionsThe only routes that run: the REST API, the MCP server, A2A, SOAP, and the markdown mirrors.RUNNING
DEPENDS ON github · THE PROJECT →
- The build is the gate. A content file that fails its schema fails the deploy, which is the intended behaviour rather than an inconvenience.
8 systems · 27 services · what runs on what →