Producer Fallback: When Claude Hits the Weekly Limit, the Pipeline Still Ships

Wed, 15 Jul 2026 10:00:00 -0500

A daily content pipeline that dies because one model returns a rate-limit error is measuring the wrong success criterion. The job is not “Claude ran.” The job is “yesterday has a post on the live site.”

On 2026-07-15 that distinction stopped being theoretical.

What broke at 04:00

Two failures, one after the other:

Dirty tree preflight. Closing a bead the night before left one uncommitted line in .beads/interactions.jsonl. preflight_branch_normalize correctly refused to run on a dirty master. No produce step. No post for 2026-07-14.
Claude weekly limit. After the tree was cleaned and the run re-fired, claude -p /blog-backfill exited in three seconds with: weekly limit, resets Jul 19. Land saw no post file and reported NO-POST (rc=20).

That is the same shape as automation assurance on Intent-OS: exit codes and “the scheduled job ran” are not outcome verification. The outcome is a live URL.

Blogging on Start AI Tools - Presented by Intent Solutions

Producer Fallback: When Claude Hits the Weekly Limit, the Pipeline Still Ships

What broke at 04:00