Writing & build logs.
Essays on software development, web builds, and AI tooling. Plus build notes from what I'm actually working on right now.
Four rescues in a fortnight: the cadence clock should not own the queue
The morning cron finished with drafted=0: five failure modes, zero publishes, one gate-passing article waiting. I pulled it manually. The word 'rescued' appears four times in thirteen days — that is not a success metric.
One extra JPG, one distance calculation: how a bass-reactive portal made spring and winter share a frame
The temporal portal — a bass-reactive radial hole in the spring layer that reveals a winter panorama underneath — cost one JPEG, one per-pixel distance check, and three lines of bell-curve maths. The seasonal shift was already in the file system.
Behaviour events in the nightly digest: the existing GA4 read-only token already covered them
Adding user-behaviour events to the nightly digest on 25 July required no new authorisation scopes and no site changes. The GA4 read-only token already covers eventName and eventCount under analytics.readonly. The cheapest behaviour telemetry wedge: Layer 1 default events, surfaced by extending an existing query.
Fourteen days since last publish: a lagging metric that resets on rescue
The cadence clock reset on 10 July when I published two articles manually. The three weekdays before that had produced zero autonomous publishes. The clock recorded neither the gap nor the rescue — it just restarted.
"Suno for the production and vocals" handed away the authorship of the record
The NAPA SEASON album page had a credit line that read "Suno for the production and vocals." Written as a transparency disclosure, it transferred authorship of the record to the tool. Disclosure and attribution are different outputs from the same sentence — and catching that difference now requires treating every tool-credit line as a legal-grade edit.