Posts on Content Pipeline.
40 posts tagged "Content Pipeline".
`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.
The pipeline ran every day in July. Every published article started as a rescue.
Five publish events across July. Every one required a human to notice the cron had failed and pull a piece through by hand. The one exception — a two-day autonomous streak on 16–17 July — proved the pipeline can work. The rescue rate is the metric no one was tracking.
Zombie draft, dead zone, zero-draft cron: three failure modes from one misread index
Ten cron cycles between 30 June and 13 July produced exactly one ready draft while the skip counter climbed from 2 to 7. Three distinct failure modes were active simultaneously—a zombie IHT draft reaching its third PR, a dead-zone mortgage cluster that never re-drafted, and zero-draft mornings with clean exit codes. The root cause was identical in each case: draft.py could not tell failure from success.
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.
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.