Building thoughtful software with AI.Notes from the systems behind the work.
Splitting one store out of a multi-store purchase order is a single transaction that rewrites revisions, PDFs and sent state, and it exposed a supplier PDF that summed the same product across stores and a file-name marker for replaced revisions that, as far as I can tell, never gets applied.
Read moreThe connect flow now begins on the tracker's own page, so the signed stamp that said who started it is gone; I traced where its jobs went, found a cleanup write that can never change anything, and noticed new connections stopped being counted.
Long AI coding sessions were breaking my session viewer's diagram. The change built a fresh layout graph per call and capped the events drawn, but the first cap kept the start of the session instead of the end until review caught it, and the load-more button still has no ceiling.
The first-run wizard check went from the root layout to the sign-in callback to a flag on the login profile, and only stopped misrouting people once the landing page and the wizard page asked the same rule about the same database row.
The scheduling app's rule templates moved to the server, with the list call seeding a starter whenever a company's list is empty. Empty also means an admin deleted everything, so the starter comes back, and that same read writes to shared settings.
A user-account save treated a missing admin flag or role list as "no" and stripped access on routine store edits. The change keeps absent fields as they were and adds a token refresh after a 403, but rereading it I found the role carry-over now spreads per-store grants across every store.
Moving my scheduling app's chores onto the server, I let a list-shaped request replace the whole file with no checks, no lock and no read-back, and the browser starts from an empty list when loading fails. What I found rereading the commits, and the shape I want instead.
Rereading a day of my own commits, I found that a failed read in my break scheduler shows an empty list, and the next edit writes that emptiness over the real file. Old files and error replies take similar wrong turns.
The agent wired a save call into every handler on my staff-schedule page, but save only sends the list of people, so the separate chore list never gets stored, and the save path under it is thinner than it looks.
A source-neutral guide to extending a reactive checkout with bounded DOM handoffs, explicit lifecycle state, and safer credential boundaries.