Activity and history

Every write is one numbered revision (1, 2, 3, …). There are no commits or hashes. Each records who made it: the app, kabacus-cli, an MCP client or the signed-in user, with an agent’s name when an assistant made it, and a one-line summary naming the transaction.

• The Activity page lists every revision and opens the transaction it wrote.
• Any revision shows as a diff of the books’ text.
• The books can be read as they were at any revision.
• Rewrites (delete, rewrite outright, declare, rename or remove an account, change a balance assertion) are hidden behind three gates: the host allows them, you hold the ledger-rewrite role, and the app has them switched on. Even then history keeps the earlier versions.

Revisions are not transaction numbers

A batch may change many transactions in one revision. Editing #12 keeps transaction #12 but creates a later revision. A conflict or unchanged save consumes no revision. Use the diff to understand what changed, and the transaction number to locate the entry.

• Save copies, back up and recover
• Command-line reference