Posts on Content Pipeline.
40 posts tagged "Content Pipeline".
Ten drafts at 08:35, zero at 08:22: ground-fetch quality was always the variable
Four days into the 14-day pillar sprint, the cron ran on time, ranked 150 clusters, and produced nothing. On day six, it produced ten drafts. The schedule hadn't changed. The source layer had.
The schedule held. The composer failed. That's what July's headline rescues exposed.
Three weeks of cadence data from ukcalculators: the approval gate works, the schedule holds, and every high-signal publish — May HPI, fiscal-drag projections, the Santander rate — required manual intervention when the composer failed. The bottleneck was never the schedule.
The cron ranked 150 clusters and drafted none: what a corrective verifier is built to surface
On 2 July, the morning cron ranked 150 clusters and produced zero drafts. The cron exited clean. The gap between those two facts is the surface a corrective verifier is built to make legible—without one, every zero-draft run looks identical from the outside.
The drafter was ready. The gov.uk sourcing layer was not.
Day 4/14 of the ukcalculators publishing sprint: the cron ranked 150 keyword clusters and produced zero drafts. The drafter had already proved it could run. The actual bottleneck was upstream — no authoritative gov.uk sources to ground claims against. Day 6 changed that.
The July gap was a sequencing problem: coverage screening was happening after the draft, not before
Between 7 and 9 July, the UK Calculators content pipeline triaged candidates, ran draft cycles, and published nothing. The check that would have caught the problem existed — it was running at the wrong stage.