The Workflow That Waits for You

Two things landed in the same afternoon and I can't stop thinking about them together.

DeepSeek dropped an OCR context compression paper — the gist being that when you run OCR on a dense document you get a wall of tokens, most of which are structural noise, and their approach collapses that wall into something a model can actually reason over without choking. The compression ratios are the kind of number that makes you feel embarrassed about how you've been doing document processing. It looks good. That's an understatement.

The second thing is smaller, quieter, and might matter more in practice: Cloudflare Workflows added waitForEvent.

waitForEvent does exactly what the name says — a durable workflow execution reaches a step, stops, and waits for an external signal before proceeding. The workflow doesn't time out. It doesn't poll. It just sits there, durable and patient, until something — a webhook, a button click, a human with opinions — fires an event at it and wakes it back up.

Put these two things together and you have the shape of something real: a document ingestion pipeline that compresses a scanned PDF into a dense, model-friendly context representation, hands that off for some downstream processing, and then — before the irreversible thing happens, before the record gets written or the email gets sent or the contract gets flagged — pauses and asks a person if this looks right.

Not a review UI bolted on afterward. Not a log you check when something breaks. A literal stop in the execution graph, with the entire workflow state frozen and waiting for a human to say yes or no.

This is the architecture that agentic systems keep gesturing at without actually building. The human isn't monitoring the loop from outside — they're in the critical path. The workflow cannot proceed without them.

Whether anyone will build it this way, or whether they'll skip the waitForEvent call because it adds latency and someone has a demo on Thursday — that's a different question.