BUILDING
AI engineering playground. Experiments, agents, tools, games, infrastructure, and things that probably should not work.
1320 contributions · 114/365 dayslessmore
Assembled from the lab's own records and this repository's commit history. Nothing here is a live metric; every row is a dated fact from the repository or its content.
A Codenotch-style side pill for macOS: AI usage rings for Claude, Copilot and Codex, and the dev servers listening on the machine, one hover away.
Docker containers and a watch strip joined the servers card: Vercel deployments and GitHub attention rows, read through the CLIs, no token held.
This site. A monorepo engineering playground built so that spinning up a new experiment costs minutes, not evenings.
the lab grew three registries and a graph: agents derived from their own definition files, MCP servers split into served and consumed, and infrastructure whose schema refuses to publish an address
A personal knowledge base that an agent compiles and keeps current, instead of a pile of documents an agent re-reads from scratch on every question.
ingest loop running against the areas vault; the schema is where all the real tuning happens
A free stockcar drafting racer for iOS where the slipstream is the entire game, with a career whose press conferences are written on-device by Apple's own model.
aero core: draft factor, side draft and the plate cap under test against the spec's curves
A build-a-car driving game for a three-to-five-year-old. One HTML file, zero dependencies, works offline, made for an iPad in a car seat.
The Obsidian vault the LLM Wiki pattern is being run against: twenty-odd life areas, from aero to survival, as plain interlinked markdown.
A hybrid knowledge brain: markdown as the source of truth, PGLite for embeddings and search, testing whether retrieval quality justifies leaving flat files.
A dependency-free HTML and CSS component library for reporting surfaces — dashboards, investor updates, operating reviews — that opens in a browser and prints correctly.
The shared asset and snippet repository that sat behind acker.cloud and thrivecmd.com while both were rented Super.so sites, the part of a rented CMS you could still keep in version control.
A marketing site for a Franklin, Indiana photographer — built, deployed, and waiting on the only two things a developer cannot supply.
Live scoring for the Jäger Bomb, a private annual golf tournament — an installable web app that survives the back nine with no signal and a drinks economy that is an append-only ledger.
An iOS cataloguing app for collectibles — comics, vinyl, cards — with vaults, a square-only camera, and a landscape cover-flow browser that exists purely because a collection deserves to be looked at.
The professional site and resume: enterprise integration work, leadership writing, and a technical wiki, written in Notion and shipped as a fully static Next.js site.
Thrive Culture Media: essays on tech, music, sports, film, and a space section that runs from launch vehicles to naked-eye astronomy, on its own Next.js and Payload platform.
An iOS app that holds at most two things. The constraint is the feature: with room for only two, you finish before you add.
The home hypervisor everything else runs on: virtual machines, containers, storage and backups for the lab, on hardware that lives in this house.
The Doubt stage gave its sub-agent full write access so it could fix what it found. That is a conflict of interest: the cheapest repair for a failing check is always to change the check.
Four failures in one week that every gate passed. None were bugs in the usual sense - each was correct code resting on an assumption that had quietly stopped being true.
A contribution grid looked fine and was wrong three ways. Each was invisible until measured, and two of the fixes were the opposite of the obvious one.
A repository, a name, and nothing else. Created in June 2026 and never given a first commit.
cause of death Never received a commit. The idea — some central hub joining the other projects together — did not survive the walk from naming it to opening an editor, and creating the repository had already delivered the entire feeling of having started.
A golf GPS you wore instead of held: 3D glasses that painted the pin, the carry number and the green's contour onto the fairway in front of you.
cause of death Four independent physical limits, any one of which was fatal on its own, all pointing at the same verdict: the job is to produce one number, and one number does not need three dimensions. Phone-class GNSS is accurate to three to five metres when the overlay needs sub-metre or the flag visibly floats off the green; magnetometer heading drifts ten to fifteen degrees beside a steel-framed cart and a golf bag, which at 150 yards is a forty-yard error in where the pin is drawn; a mown fairway is a low-texture plane, the worst possible input for the visual-inertial tracking that would otherwise correct both; and a sunlit fairway runs three to ten thousand nits against consumer waveguide optics that deliver one to two, so the overlay washed out in exactly the conditions golf is played in. The rules finished it: under the Rules of Golf a device that measures elevation change or recommends a club is a breach unless the feature is disabled, so the interesting half could not be used in any round that counted.
failure is part of the product. nothing is hidden →