In July 2026, Mistral released a model aimed at formal software verification — generating machine-checked mathematical proofs, in Lean 4, that a piece of software behaves as specified. It’s a narrow capability with outsized implications for anyone building systems where “we tested it and it seemed fine” isn’t good enough.
July 2026 brought another wave of coding-focused model releases promising near-frontier capability at lower cost. They’re genuinely good — and they make the gap between greenfield and brownfield work more visible, not less. Most conversations about AI-assisted coding default to the easy case: a brand-new codebase, a clean slate, and a coding agent that scaffolds an app in minutes. That’s greenfield work, and it’s genuinely where tools like GitHub Copilot, Cursor, and Claude Code look most impressive. The harder and far more common reality for most engineering teams is brownfield: an existing system with years of undocumented decisions, tangled dependencies, and business logic nobody fully remembers the reason for.