The claims cutover meets the deadline only if ordered updates remain provable after data movement begins.
The technology deadline protects the customer’s launch commitment; the audit requirement protects every disputed claim after launch.
Who you’d be doing this for
“Operations already asked how we’ll explain two updates landing in the wrong order on the same claim.”
Noor Hassan · Claims API Lead
He owns the public submission API used by brokers and operations staff to amend claims throughout the day.
What is at stake
Seventeen of 24,000 concurrent claim sequences show possible out-of-order updates before Monday’s cutover. You must weigh a deadline-bound migration against evidence that has to stand up in a claim dispute.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- regulatory deadline vs auditable ordering
- low latency vs transaction proof
- automated trace speed vs verified evidence
- migration commitment vs recoverability
Why Cloudflare
Cloudflare Workers, Durable Objects, D1, and R2 form the customer’s proposed transaction path, so the production evidence must match their behavior under concurrency.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.