Lucas WintherandClaude Opus 5
596de45525
Bills that repeat: rent monthly, a subscription every 28 days, a phone bill every 30 days whose clock restarts when the data cap is hit early. A recurring cost projects expected charges forward; each occurrence is confirmed into a real Purchase when the money moves. The fold gains a second balance, so `remaining` never shifts and `projected` says what is left after commitments. The two reconverge as a month settles. The phone bill reads like a third recurrence kind and is not one. It charges 30 days after the PREVIOUS CHARGE, and the data cap only makes a charge happen early — a date two-stage confirmation already records. So `anchoring` is one field, `calendar` or `lastCharge`, and the domain never learns what a data cap is. That collapse is most of why this design is small. Two consequences worth not re-litigating later: - `everyNMonths` carries no day. Rent occurs IN September, and `IsoDate` already permits a bare "YYYY-MM", so the commonest case needs no day arithmetic and no February clamping rule. - `amount` is a single mutable Money with no RuleVersion-style series. Safe ONLY because confirmed purchases hold what was actually paid; under projection-only it would destroy history. Occurrences are computed, never stored — materialised snapshots were rejected in the original design, and an unbounded recurrence would otherwise need a horizon. `upToMonth` comes from the caller, so src/domain/ stays clock-free. Takes schema 6. The global-decimals spec claimed 6 too and is reassigned to 7; both specs now say so. The steps are independent and compose in either order. Spec only. The two settings-layout fixes in the tree are unrelated and stay unstaged. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Budget 2.0
A personal budgeting PWA. Envelope-style monthly budgets with rollover, split purchases, finance plans, multi-currency, and JSON/ODS export. All data lives in your browser — there is no server and no account.
Development
bun install
bun run dev # dev server with hot reload, on :3000
bun test # run the test suite
bun run build # production build into dist/
Self-hosting with Docker
docker build -t budget2 .
docker run --rm -p 3000:3000 budget2
To serve from a subpath, build and run with BUN_PUBLIC_BASE_PATH:
docker build -t budget2 --build-arg BUN_PUBLIC_BASE_PATH=/budget/ .
docker run --rm -p 3000:3000 -e BUN_PUBLIC_BASE_PATH=/budget/ budget2
GitHub Pages
Pushing to main builds and deploys to Pages automatically, using
/<repository-name>/ as the base path. Enable Pages with "GitHub Actions" as
the source in the repository settings.
Your data
Everything is stored in this browser's IndexedDB. Export regularly from Settings → Your data: the JSON export is both your backup and how you move your budget to another device.
Both destructive actions there — Import, and "Reset everything" — download a backup of your current data before replacing it, and abort if that download fails. Reset puts the app back to a brand-new install: the three starter posts, the DKK/USD/EUR currency table, this month at zero income, no purchases.
Known limitations
- Data is per-browser. There is no account and no sync. If you clear this browser's site data, or move to a different browser or device, your budget is gone unless you exported it first. The JSON export is not just a nice-to-have backup — it is the only way to move a budget between devices.
- Installing and offline use are unverified. The manifest ships the SVG plus 192×192 and 512×512 PNG icons, and the service worker demonstrably installs, activates and precaches every asset — but nobody has yet confirmed that Chrome offers its "Install app" prompt, or loaded the app with the network actually cut. It works as a regular tab regardless.
Documentation
docs/ARCHITECTURE.md— layers, data flow, and why the non-obvious choices are what they are.docs/PRODUCT.md— who this is for and what must never break.AGENTS.md— the rules for changing this codebase, and the test that catches each one when broken.CLAUDE.mdandGEMINI.mdpoint at it.docs/DECISIONS.md— an index of the choices that shaped the app, and what each was chosen over.docs/TODO.md— what is still queued.docs/specs/— one design document per piece of work, each recording the alternatives that were rejected.docs/plans/— task-by-task implementation plans.