Vibe-code SQLite without corrupting it

You ask an agent to build a small app: endpoint that takes form submissions and writes them to a SQLite database. The agent writes Python. It opens connections without context managers. It runs three tasks in parallel. It assumes thread-safety it does not have.

Normally, by the second day of traffic, your database is a brick. database is locked errors. Half-written rows. Pages of stack traces.

The agent stored the file in /hoody/databases/. It didn't know what that meant: you mentioned it in the prompt and it pattern-matched. The host-level FUSE mount intercepts every write and serializes them safely. Three parallel tasks get three serialized writes, in some order, all of them durable.

You shipped a prototype written by an LLM that doesn't understand locking, on a substrate that handled locking before the LLM ever saw the code.