Start with the Garden product page to see the flagship proof in working form. This ledger is the reference frame behind it.
Ledger
Verifiable claims about the work.
The studio holds itself to a simple standard: every public claim connects to a working behavior or a testable boundary. Not campaign language. Not borrowed confidence. What the product actually does, and what it structurally cannot do.
Privacy boundary
Servers hold zero decrypted ledger records.
This is not marketing phrasing. The system architecture does not permit the company to read your financial records. The encrypted vault stays on your device. Import, categorization, and analysis happen locally. When syncing is enabled, only anonymous transaction hashes leave the device, never the records themselves.
Offline proof
The product remains usable after first load without a live connection.
This is part of the trust test, not an edge case. If a financial tool requires constant network access to show you your own records, that tool has made a dangerous assumption about the relationship between access and ownership.
Exit mechanics
Exports and backups are first-class features, not support theater.
Your records export as plain-text CSV and printable PDF. Recovery kits print to paper. These are not advanced settings hidden in preferences. They are part of the product surface because ownership is not complete without a clean exit.
Engine proof
582 passing tests gate the financial engine.
Money is not a place to experiment with loose behavior. The categorizer, the balance calculator, and the statement parser all run against a comprehensive test suite. That number will grow as the product grows.