Building thoughtful software with AI.Notes from the systems behind the work.
A nightly copy of this box's backup repositories now goes to my NAS and proves where it's writing before it writes, and I also fixed a checksum that would always fail for the wrong reason and an install guard that could never fire.
Read moreThe save at the end of my ordering wizard catches each failed item, logs a warning and keeps going inside one transaction. Postgres aborts the transaction at the first database error, so the partial save it promises can't happen, and the same file reloads sessions by timestamp and drops leftover units.
The agent built an encrypted, signed, two-copy backup system with no tests. Reading the restore path showed a loose success flag, a signature nobody checks, truncate-before-load, and comma-split CSV, plus what I want restore to do instead.
An admin endpoint runs signed, encrypted SQL uploads, and a dry run can reset a version it already applied.
The live allocator in my ordering system never reads the stock ceiling its README promises, the random tests check five rules but not that one, and a ceiling-aware allocator sits unused in the next folder.
Restoring a backup puts the old accounts back, including the one running the restore. The agent's first attempt saved only the admin's password; the second saved the whole account and its grants, and I walk through the gaps I can still see in the code, starting with the login rename and id reuse.
The agent gave my chore app a test runner that saves the config and puts it back after every test, then wired it to an admin button on the live server. It looks clean at the end of a run, but reading the code, visitors could get test settings mid-run, two overlapping runs could delete the real config and still report green, and a killed run loses the only saved copy.