The Liability Is the Code Nobody Owns

The liability stacking up in most AI codebases isn't on any dashboard, because nobody's measuring what happens when the person who merged the code can't explain it. Teams track the inputs instead: seats adopted, lines shipped, PRs merged. The number goes up and everyone calls it a win. Meanwhile the thing that actually costs you later, code in production nobody on the team can fix, accumulates in silence.

That's why the Godot decision this week is worth more than the gaming-press framing gives it. A well-run open-source engine formally stopped accepting AI-authored contributions, and the reason was blunt: "We can't trust heavy users of AI to understand their code enough to fix it." Not that the code was bad. That the person submitting it couldn't own it.

Strip the "AI slop" language, which is vivid and beside the point, and the structural problem is left standing. The issue isn't aesthetic quality. It's debuggability and ownership. A community that lives or dies on volunteers being able to maintain each other's work noticed the ownership gap before most enterprises will, because they can't paper over it with headcount.

When the model writes the code, the institutional knowledge lives in the model, not in a person who can explain it three different ways.

This is the same failure the layoff-regret coverage keeps circling, and reading it as an "AI doesn't work yet" story lets everyone off the hook. The technology isn't the failure. The deployment model was. AI got dropped in to replace judgment and tacit knowledge, and the gap surfaced at the worst possible moment.

Godot's version is sharper, because it names the specific thing that went missing: a human in the loop who could account for the output. You can't maintain what you don't understand, and "we merged it fast" is a different claim from "we can keep it alive."

That's exactly the line between vibe coding and agentic coding that vendors keep blurring on purpose. Improvised output is fine for a spike. Ship it into a codebase a team has to live with for years and the knowledge has quietly migrated out of your people and into a model you don't control.

I don't know where the durable line lands for any given team. But the measurement trap is real right now. If the only thing your AI program reports is how much code got generated, you're tracking the input and ignoring the debt. Godot just put a policy on what everyone else is going to discover in a postmortem.