Build LogUKCalculators
#01
2026-08-235 min read

`mortgage-abandoned-about-above`: Title-Mangling, Claim Blocks, and the Corrective Pass That Held Fourteen Pillars Together

The Day 2 cron draft came with an unusable slug and three claim blocks that would have shipped unverified. Both got caught and corrected. That pattern — not just the gate, but the corrective pass — is what held a fourteen-pillar streak together.

Read post
Build LogContent Pipeline
#02
2026-08-216 min read

The cadence clock resets on zero-draft runs. The publishing schedule is manual rescue.

On 17 July the approval gate worked exactly as designed: the first multi-day autonomous streak since the pipeline launched. By 20 July I was writing another manual rescue. The 14-day cadence clock had reset again.

Read post
Build LogPipeline
#03
2026-08-215 min read

The Pipeline Conflated failed-* with Successful Publishes. Skipped Hit 7.

Ten cron cycles from 30 June to 13 July produced one ready draft and zero auto-publishes while every log showed a clean exit. The mechanism: draft.py treated failed-* index entries identically to successful publishes — permanently consumed. Skipped climbed from 2 to 7 before the root cause surfaced.

Read post
Build LogContent Pipeline
#04
2026-08-205 min read

Ten cron cycles, one ready draft — draft.py had no concept of retry

From 30 June to 13 July, ten cron cycles ran clean and the skipped counter climbed from 2 to 7. The root cause: draft.py treated any index entry — including failed-* — as permanent completion. Shipped and failed needed opposite treatment and got the same.

Read post
Build LogContent Pipeline
#05
2026-08-165 min read

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.

Read post