Git in the file, or the file in Git

There are two ways to put Git on your data.

Beads wanted a board agents could share. It indexed that board with SQLite. The index is a second copy of the truth. Git can't merge it. You have to keep it honest.

You don't need that sidecar. A scan of the files is enough. Kanbus dropped it. Virtuus made that the product: one JSON file per record. Indexes live in memory and die. The files are the store.

DoltHub wanted the other shape. Apps already speak SQLite. They wanted branch, merge, and diff on the rows. They kept the SQL engine. They swapped the B-tree for a Prolly tree. Git lives inside the database file.

So the leftovers are different. DoltLite's is a C storage engine sitting next to the rows. Beads' is a sync tax for a problem the filesystem had already solved. If you're picking a store for agent work, you don't need SQLite just because Beads had one.