Simon Willison surfacing a policy from the SQLite project is exactly the kind of signal that ought to get more attention than it's getting. SQLite is one of the most widely deployed pieces of software on Earth — it lives in your phone, your browser, your car, your aircraft avionics — and its development practices have always been unusually rigorous: 100% branch coverage in tests, MC/DC coverage for aviation-grade builds, and a famously conservative review process led by D. Richard Hipp and a tiny core team.

Now they've drawn a line: no agentic code contributions accepted. Given SQLite's coverage requirements and the fact that every line of code must be defensible under aviation-industry audits, this isn't a knee-jerk reaction — it's a considered position from maintainers who understand what "correct" means at a level most projects never approach.

Why this matters for a technical audience:

• It's a counterweight to the prevailing narrative. Most coverage of agentic coding tools focuses on velocity gains. SQLite's stance forces a harder question: in domains where correctness is non-negotiable, does AI-generated code carry costs that outweigh the speedups?
• Provenance and accountability. SQLite's contributors sign a stringent copyright dedication. Agent-generated code muddles authorship, licensing provenance, and the chain of human accountability that audit-grade software depends on.
• Review economics flip. When a tool can generate plausible-looking patches faster than a maintainer can rigorously review them, the bottleneck shifts dangerously. SQLite's maintainers appear to be saying: we'd rather not be in that race at all.
• Precedent for other foundational projects. Curl's Daniel Stenberg has written extensively about the wave of low-quality AI-assisted security reports drowning maintainers. SQLite formalizing a policy gives other critical-infrastructure projects cover to do the same.

Simon Willison is the right person to be analyzing this — he's been deeply embedded in both the LLM tooling world (Datasette, llm CLI) and the SQLite ecosystem for years, so his read isn't going to be reflexively pro- or anti-agent. Expect a careful look at the actual policy text, the reasoning behind it, and what it implies for how the broader open-source community navigates the next few years.

One upvote is criminally low for a Simon Willison post on this topic. It deserves to be a top-of-page discussion.