Reports directory

Planned static household finance views

Each report view is intended to read from generated local artifacts that are baked into the static deployment. No page is expected to trigger live CLI execution or talk to a hosted database.

Planned /data/reports/budget-status.json

Budget status

Budget summaries can roll up ledger-derived totals, target values, overages, and category health into a read-only static view.

  • Current period totals
  • Budget versus actual variance
  • Categories needing attention
Planned /data/reports/recurring-transactions.json

Recurring transactions

Recurring transaction summaries can show expected bills, subscriptions, transfers, and observed cadence without turning the website into a transaction editor.

  • Upcoming expected charges
  • Missed or changed cadence alerts
  • Category-level recurring totals

Data flow

The intended flow is local data generation first, then static site build. That keeps the website decoupled from live automation while still allowing pta-clerk to prepare the report snapshots consumed by the site.