Product updates, implementation details, and field notes on getting an app running, who may reach it, and the record the next change starts from.
Articles, shipping notes, and the thinking behind how aidrop.it works.
A green build and a log line do not prove a migration landed. Four SQL statements that do, and the rules an agent follows when it runs them against live data.
Stop, delete and destroy leave different things behind. What each verb keeps, why a stopped app still has an address, and a report block for your agent.
A host with no backups has told you where the copy comes from: a job in your project, dumping to storage you own. Two ways by size, and a pg_dump container.
Deploying from an agent session is fast. Give the loop three reasons to stop, name the fixes it may never make, and paste a deploy-loop block into instructions.
Every host is a contract: writable paths, disk, port, replicas, egress. Read it before your agent picks a stack, with a worksheet you can fill in for any host.
A fresh agent session reads the repository, not the running app. Six facts to read from the host first, and a block to paste into your agent instructions.
Rebuilding an old commit is a new artefact. Keep every built image by commit, start it by name, and write migrations so an old version runs on a new schema.
An upload has no history; a platform that commits for you holds a write path a prompt can reach. Why code should reach a host by git push, with three checks.
Signup checks measure the person, not the app. Judge abuse when an address opens to the internet, stop first, delete last, and grade any host with a worksheet.
