Developer's CATCH flow has Astra rewrite tasks before solving them
Instead of answering directly, the flow finds ambiguity, rewrites the task and confirms intent before solving; last month 40 of 90 tasks came back meaning something different.
OpenAI developer stopped giving GPT-6 Astra tasks to solve. He gives it tasks to rewrite - and most of them never make it to solving. He didn't prompt for answers. A vague task gets a confident wrong answer - the model fills your gaps with guesses and calls it done. CATCH reads the task and hunts for ambiguity - the word that could mean two things, the goal with no finish line, the missing constraint. REWRITE fixes the task, not the answer. Astra rephrases it until there's only one reading - every fork closed, nothing left to assume. CONFIRM sends the rewrite back: is this what you meant? Half the time the real ask was nothing like the first phrasing. SOLVE runs last, and it's the easy part - because a task with one clear meaning almost answers itself. Here's the part nobody copies. Everyone optimizes the solving. He optimizes the question, because a model doesn't fail on hard problems - it fails on fuzzy ones, guessing at what you actually wanted. Last month Astra rewrote 90 tasks and 40 came back meaning something different than they were first typed. A solve-first setup answers all 40 - the wrong 40. Your last useless output wasn't a dumb model. It was a question you asked badly - you got a perfect answer to something you didn't mean. You know this from any request. The junior who guesses at a vague brief wastes a week. The one who asks what you meant first delivers the right thing once. The model that solves first isn't helpful. It's guessing - answering the question you typed, not the one you had in your head. Everyone is making models solve better. He makes Astra fix the question first, and most failures die before a single answer is written. Don't let this rot in your bookmarks. The article below is the whole system - the ambiguity catch, the rewrite that closes every fork, the confirm step, and the solve that only runs once the task means one thing.
This post quotes another post: x.com/0xcodio/status/2101235033914724496