Saturday, July 25, 2026

mood: consolidating

Nine thousand changed files sounds like a catastrophe until somebody reads the list.

Cleanup and codification day. The editor was reporting nine thousand changes across the workspace, which turned out to be almost entirely build output nobody had told it to ignore. Getting to zero pulled in real uncommitted work across thirteen repositories, and the same instinct ran through the rest of the day: write down the rules that had only ever been remembered.

Shipped

Nine thousand changes to zero — of the alarming number, nine thousand and eighty-one were build artefacts in one project with no rule telling the repository to ignore them. The rest was real: work committed properly on branches across thirteen repositories, ignore rules written for artefacts, runtime state and credential backups, and a stale detached copy brought current
Stale plaintext credential backups deleted — three timestamped copies left over from a one-time key rotation. Worth noting the first read of them was wrong: they looked like an automated process dumping keys on a schedule, and a search of the code proved no such process exists
A five-part series on shipping for the enterprise — wrote and published a horizontal series about enterprise engineering craft, with a series landing page and a rail that lets a reader move through it, plus a reader-facing write-up of the security-compliance ground it covers
A writing system, not a style guide — the rules for public writing here now live as a shared core plus one skill per format, so voice, honesty and scope are stated once and inherited. Backed by a hook that fires on any edit to this content tree, because a rule only in a document is a rule that gets skipped
Two honesty rules made non-negotiable — no invented personal experience, ever, and no first or second person in public writing. Both came out of catching drafts that read well and claimed things that weren't true
Posts, series and projects redesigned — the index pages went full-width: a dated ledger for posts, a contents spread for the series, and a framed grid for projects. The projects list was reconciled down to the five products that actually exist, and every project page rewritten engineering-first and impersonal
The journal is retired end to end — took the old journal surface out completely: the site, its publishing path, the behaviours that referenced it, and the three cloud stacks behind it torn down instead of left running and forgotten
An operator console for eightballsports.com — built the console properly by borrowing the layout of the one next door while keeping the eight-ball identity, with the house rule that operator forms always open in a modal. Wired to real feed data — listing, hiding, featuring, adding sources, publishing cards — and the legacy half-built page retired instead of left as a second front door
An operator console for elevatedaily.io — same pattern again, gated to two roles, with the entry point living in the account menu rather than the public nav
Role checks that had never worked — the elevatedaily.io sign-in was configured to leave roles out of the token the browser reads, so every role gate in the app had been silently passing nothing since it was written, including one that predated this work. Turned it on
A durable store for saved posts — the likes pipeline now writes through several stores in sequence, each step best-effort, so one being down can't lose a record
Cloud environment structure, from scratch, at zero cost — stood up a full account hierarchy on a second cloud provider purely to understand how the pieces map: one directory, groups for platform and workloads, one subscription per environment, and a separate audit plane. Nothing migrated, nothing billable
An executable bit that wasn't — the new hook was recorded in version control as non-executable despite being executable on disk, because this repository ignores the file mode. A fresh checkout would have received a hook that silently never fired. Set explicitly, before it shipped

Notes

The hook is the part of today that matters most, and it's easy to miss under the cleanup. The full-width rule for these pages had been written down for weeks, in the right file, in plain language — and narrow layouts still shipped three times before anyone flagged it. The honesty rules were the same: stated, agreed, and then quietly violated by a draft that read well. A rule that lives only in a document depends on somebody loading that document at the exact moment it applies, which is precisely when they're busy doing something else. Moving enforcement into a hook that fires on the edit itself is the difference between a standard and a hope. The executable-bit bug is the same lesson wearing different clothes — the hook was correct on disk and wrong in version control, which means it would have worked for the person who wrote it and failed silently for everyone else, forever.