Your books live in a real database. Yours.

Other bookkeeping feeds sync your lines out to a spreadsheet and call the spreadsheet the destination. braatzledger inverts that: the destination is a proper per-tenant database, and everything else is a view of it.

That is why there is no page here about keeping two copies in sync, and no warning that re-syncing will overwrite the edits you made in the other copy — the failure mode that spreadsheet destinations carry as a fact of life. One system of record, derived views on top, corrections as appended judgements underneath.

Getting data out is a first-class face, not an export button: the JSON API and the MCP surface both read and write your books today, against a published parity bar. Spreadsheet-shaped exports ride the API when they land.