Covers July 10 - 12, 2026.
After the public build proofs, I figured the only way to find out what aidd can’t do is to point it at things that look nothing like its home stack. So that’s what this weekend was. Three builds, none of them a Bun-and-React web app.
By then I’d added opt-in automatic follow-up runs to aidd. They are capped at a configurable chain depth. This removed the manual relaunch gap from the build proofs.
Pantry, in PowerShell
Podex is a small application template built on Pode, a PowerShell web framework, with htmx and Mustache on the front. That is quite a way from the Bun and React setup in Spernakit. On Friday, I had aidd import it and build Pantry on top, a kitchen inventory app with twelve features. It does the expected inventory work: CRUD, search, stock and expiry views, quick quantity changes, and CSV export.
Then I ran the audit pass against the fresh build and got fourteen findings back. Debug routes left in, injection hazards, missing security headers, drift between the data model and the UI. I also had it stand up a full Pester suite, which Podex didn’t ship with.
Several of those findings came from the Podex baseline rather than Pantry. The fixes went back into Podex, which was what I hoped would happen when I started this. The Flaskr proof had done something similar, although it hadn’t built a whole product on the foreign stack first.
Habit tracking, on a phone (sorta)
I spent Saturday and Sunday on a habit tracker for mobile. It uses Expo and local SQLite, with a six-room home rendered in Skia. The rooms respond to how you’re doing with your habits, and you earn decorations to place in them. There’s scheduling and check-ins, with pauses and skips accounted for, plus weekly recaps, onboarding, reminders, and archiving. I kept the product loop free of accounts and network services. Your data sits on the device only (unless you back it up or move it yourself). I don’t want it.
Day two was mostly the stuff nobody demos: accessibility, settings, backup and restore, timezone corrections, Android reminders, and the release configuration. I still haven’t put it on a physical iOS or Android device and signed off on it. I’ll get around to it eventually.
An Astro blog
The third one was a blog and project portfolio site. It uses the same review flow and the same gates as everything else now. That’s when I found out even a simple static site has licensing obligations. There is no runtime JavaScript in the thing and it still ships MIT-licensed CSS and fonts, and MIT wants its notice to travel with them. None of my gates were checking for that.
The unfamiliar stacks went better than I expected. I’m still having to decide what counts as finished, though. The phone test is waiting on me, and I have some licensing work to do on the blog before I’m comfortable with what it ships.