Problem
A useful ledger needs consistent records, clear summaries and reliable access boundaries. SpendWise addressed personal expense and income tracking. FamilyLedger is the intended continuation toward household and small-business needs, with additional account, entity and currency concepts still to be developed.
Team and my role
SpendWise was designed and built by Leighton Tidwell, Jason Holmes and Eric Hill for UMGC CMSC 495 in Summer 2026. I am one of those contributors and lead the FamilyLedger continuation. The inherited application is shared team work; this case study does not assign every module to me.
The repository identifies SpendWise commit 754c558 as the import baseline and states that the team consented to publication. Later FamilyLedger extensions are attributed to Jason Holmes, but the planned extension list below is not presented as completed implementation.
What the source contains
Inspect the inherited feature and evidence map
| Area | Baseline implementation | Evidence boundary |
|---|---|---|
| Authentication | Sign-up/sign-in, session refresh, protected routes and logout. | Source, unit tests and recorded CI browser flow; production configuration remains unverified. |
| Ledger workflows | Expense creation/editing/deletion, expense and income categories, recurring income and dashboard summaries. | Inherited SpendWise features with unit/component and browser coverage. |
| CSV handling | Import parsing/validation and authenticated data export with paginated reads. | Source and test coverage; no real financial files used in this review. |
| Access boundaries | Owner-scoped database policies and authenticated server-side data access. | Recorded isolated CI tests exercise database and application surfaces; no production-wide security guarantee. |
Architecture and engineering choices
The baseline uses Next.js 16, React, TypeScript, Tailwind and Supabase. Server actions validate workflow inputs, while Supabase Auth and cookie-based sessions support protected routes. Database migrations enable row-level security with user ownership checks. Route protection and database authorization serve different parts of the access boundary.
The Calm Ledger design system centralizes theme tokens and uses tabular numerals for money. Pure functions handle recurrence, summary calculations and CSV transformations so those rules can be tested without a hosted database.
The CI isolation change addresses missing hosted test configuration by starting an ephemeral local Supabase stack, applying repository migrations and passing its local configuration to the browser suite. The workflow checks that the generated API address is local and tears down the stack afterward. This avoids using production financial records for automated checks.
Verified test evidence
At repository revision a23315a, the 17 November portfolio review reran lint, TypeScript checking and 183 unit/component tests across 29 files; all passed. Local review used Node 26.13.0. No application behavior was changed.
The inspected 16 November CI run, at PR revision 4d10468, passed lint, type checking, 183 unit tests and 23 Playwright browser tests using Node 22 and local Supabase. That is recorded CI evidence, not a fresh local browser rerun. Docker was unavailable in this review environment, so the local database/browser stage was not repeated.
Browser test sources include two-user database isolation and separate-user application surfaces. Passing tests support those defined scenarios; independent security review and current hosted deployment acceptance remain separate.
FamilyLedger direction
The repository describes accounts/entities, multi-currency, budgets, statement import and an agent operating layer as later work. Their requirements, implementation, tests and acceptance should be tracked individually before the portfolio calls them available.
- Confirm the next product requirements and reconcile historical scaffold instructions with the imported feature baseline.
- Implement scoped FamilyLedger extensions with contributor provenance and test evidence.
- Verify an isolated, synthetic-data demonstration and its deployed revision before adding a live-demo link.
- Review access controls, import/export behavior and recovery procedures for the actual release configuration.
Sources and license
Source snapshot: FamilyLedger at a23315a. Scope and credits are recorded in the README; CI and E2E assertions are available with the source.
The application source uses the MIT license, copyright 2026 Leighton Tidwell, Jason Holmes and Eric Hill. Preserve that notice. The repository's public source availability does not authorize disclosure of anyone's financial records.
Evidence reviewed 17 November 2026. This case study uses source and synthetic-test evidence; no private financial information, account credentials or production records are included.

