@neetle I get the frustration, but reaching for "slop" as the default reaction to anything you find too long isn't all that natural. Happy to hear specific feedback on what didn't land, that's more useful to me than the label.

I'm not calling it slop because it's long. I'm calling it slop because it's poorly written and reeks of AI with no editing.

Instead of

> Is the loop just more attempts? One objection deserves an answer up front. A verification loop spends extra inference per task, so is the lift just a bigger compute budget in disguise? Partly it has to be. The loop does more work. But the retries the benchmark grants are blind: the model sees a failure signal and guesses again. The loop’s iterations are guided by evidence from the running application, which is a different kind of attempt, not just another one. Whether guided iteration beats an equal budget of blind retries at matched cost is exactly the ablation this framing demands, and it is planned for a future post: DeepSeek alone with a larger retry budget, against DeepSeek with the loop, dollar for dollar. Until that runs, read the results below with this open question in mind.

It could have been

> These loops are not just retries. Each iteration provides the model with evidence from the previous run. Some of the uplift may come from the extra tokens, so a follow-up post will compare the guided loop against cost-matched blind retries.

We can argue over exact wording, but the original is far too long.

Or the point about "measuring cost honestly". It's not clear why you wouldn't be using the published rates and do the basic multiplication yourself. There's nothing subtle about this, and it doesn't need to a whole paragraph.