Posts on Cadence.
5 posts tagged "Cadence".
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.
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.
Three days, zero publishes, one fix: screen before you draft
The 7-9 July publish gap traced back to a sequencing error: duplication checks running after draft resources had been spent, not before. Moving the coverage screen upstream stopped the backlog compounding. Five articles in the thirteen days since.
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.
Five articles shipped in July. Every one of them needed a hand.
July's cadence log records five published articles. Behind four of them is a distinct failure mode — composer crash, checklist casualty, CLI error, day-cap, or coverage-screening gap — that the operator patched by hand. The July 17 exception shows what the pipeline looks like when everything holds; the rest of the month shows what it looks like when the operator is the error-correction layer.