Foundation: single arm64 container (Hono + SQLite via Drizzle, React + Vite), local sign-in with long-lived sessions and passkeys, roles (read-only, full access, admin), nightly and pre-upgrade backups, light and dark themes, date-based version numbers, and the ideas lightbulb behind IDEAS_ENABLED. Money in: accounts with balances, CSV import with bank detection, a column mapping pop-up for unknown layouts, duplicate checks, transfer pairing and undo; one-tap review with learned rules; activity with search, splits, tags, notes and cash entries. Statement files are blocked from commits by a pre-commit hook; tests use synthetic fixtures only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
836 B
Markdown
19 lines
836 B
Markdown
# Statement samples
|
|
|
|
Drop your bank and card exports here, exactly as downloaded.
|
|
|
|
1. Make one folder per account, named however you like, e.g. `bofa-checking`,
|
|
`bofa-savings`, `discover-1`, `discover-2`, `chase-prime-visa`.
|
|
2. Put that account's export in its folder untouched: same file name, same
|
|
contents. Two or three months per account is plenty.
|
|
3. That's it. Tell Claude when they're in place.
|
|
|
|
How these files are protected:
|
|
|
|
- Git ignores everything in this folder except this note, and a pre-commit
|
|
check blocks statement files anywhere in the project.
|
|
- Only the `pi` user can open this folder.
|
|
- Claude never opens the raw files. A script on this server turns each one
|
|
into a masked profile (column headers, date and amount formats, value
|
|
shapes such as `Aaaaaa #999` and `-99.99`), and Claude works from that.
|