★ Follow-up to "Blaming the model won't fix your workflow": the paper is now a preprint. The real learnings: composable domains, a verification ratchet, and tool naming.

Summary

A month ago I posted the very rough beginnings of a paper. That rough version did not survive: it got pulled apart and rebuilt by the very process it describes, and what came out the other side is now a proper preprint with a DOI: https://doi.org/10.5281/zenodo.21139628 . Short version: the core claim held. The artifacts (specs, plans, executable graphs) and the verification gates wrapped around them have proven out on real work. Agents produce the work, the gates catch the defects, and a milest

SpinGraph analysis pending — check back after processing.

• What's one thing AI does surprisingly well that you didn't expect?
• We are Focused on the Wrong Problems!
• Why I built a proactive context curator instead of a compactor — and what I got wrong for three months
• What's one AI capability that you think is underrated because everyone is focused on AGI?
• i automated my entire social media content production with cloud mcp. heres what actually changed
• Un modello 100% locale sul tuo smartphone!