Thriving Quest 02 · Public build

Proactive Family Finances

I don't want money living rent-free in my head. For me to feel fully confident in our resource planning, I need a regular and robust process for historical reporting, short-term budgeting, long-term financial planning, and tracking progress toward our financial goals.

This quest adds an extra layer: a key stakeholder, my wife. I'll manage the automation and workflows, but we make financial decisions together, so every output needs to be easy and secure for both of us to access on the web.

This thriving quest is to move from haphazard financial archaeology to a proactive and regular family finances routine: owned source data, trustworthy automation, recurring planning rituals, clear reporting, celebrations as we reach our financial goals, and specific actions tied to the life we're building.

Current problem

Irregular attention may be slowing our progress toward our family's financial goals. A lack of clarity and precision may also be shaping suboptimal financial behaviors without us realizing it.

Thesis

Agents can help us achieve financial freedom faster and with less stress.

Current progress

An initial draft of the local data foundation, dashboards, goal model, and review surface exists. The underlying processes still need to be hardened, tested individually, and refined with feedback from my wife.

Follow along

Subscribe to the . The first essay will graduate from the build notes once the stable loop has real family mileage.

The vision

“The ability to do what you want, when you want, with who you want, for as long as you want, is priceless.”

Morgan Housel, The Psychology of Money

I want our financial system to be penny-perfect and instantly accessible.

As end users, my wife and I have both regularly scheduled and ad hoc needs. On a regular cadence, we review budgets, assess goal progress, and plan our expected financial behaviors into the foreseeable future. At unpredictable moments, we also need to conversationally assess everything from this week's budget and spend-anomaly alerts to net-worth modeling for retirement. Anything related to money should feel easy and intuitive.

Underneath that experience, the data stays secure, scheduled loops are hardened, and the system runs proactively, nudging us toward better planning and saving.

Our ultimate goal is financial freedom. Getting there requires a better way to track and manage our family finances: one that makes progress visible, helps us act sooner, and lets us celebrate milestones along the way.

Design intents

  1. Positive reinforcement with negative alerts - celebrate progress during every review ritual, and alert us proactively if we're veering off track
  2. Tech independence - the family record stays local, portable, and rebuildable, with vendors treated as swappable inputs
  3. Secure by construction - credentials stay outside model context, statements are masked before parsing, and shared web access must be authenticated and least-privilege
  4. Pristine provenance - every record, change, and decision traces back to its source
  5. Trust is earned - regular human reviews continue until alignment is consistently very high
  6. Works for both of us - outputs make sense, remain easy and secure to access, and inform decisions for both of us
  7. Close the loop - every decision and target is proactively tracked and reported against

Success criteria

Status (2026-07-14)

The pieces are farther along than the operating system. At the July audit, the system held 5,862 synthesized transactions and 160 categorization rules: 110 imported and 50 learned. The first categorization review covered 473 transactions with five corrections. But the daily sync was never installed, the recurring rituals had not completed a cycle, and a derived-layer duplicate fix returned after a rebuild. The build had substance; the operating loop did not yet exist. This is now a stabilization quest.

What's working

  • The philosophy is specific - family freedom, a stress shield, lifestyle bounds, and re-design triggers are written down
  • The raw materials are owned - statements and bank feeds land in a local database with source provenance
  • Trust is a design constraint - rules are meant to earn automation through approvals and continuing samples
  • The family ritual has a surface - goals, watched categories, balances, and commitments can share one monthly view
  • The database is rebuildable - independent source layers feed one stable query surface

What's not (yet)

  • Freshness isn't governed: the advertised daily job stopped, and no health check made that failure loud
  • Source merging isn't deterministic enough: approved design rules and running code disagree, and known duplicates can return after rebuilds
  • The categorization loop is mostly an agent playbook, not a tested executable pipeline connected to fresh bank data
  • The recurring rituals are only partially built and remain unproven: no complete cycle has yet closed the loop
  • The local dashboard boundary needs hardening before it can become a secure shared or remote family surface
  • Plans, status pages, counts, and source-of-truth claims contradict one another

Stabilization sequence

  1. Make input health explicit - freshness, account coverage, statement coverage, and sync failures become visible gates
  2. Make gold deterministic - one matching contract, durable overrides in source/config, reconciliation tests, reproducible rebuilds
  3. Finish the categorization loop - executable rules, confidence state for every category, a durable review queue, and coverage metrics
  4. Prove the family routines - harden access, run each ritual on its intended cadence for three months, carry commitments forward, and remove anything that doesn't aid a decision
  5. Add proactive guidance - specific recommendations and probability models only after the descriptive loop stays trustworthy

Key milestones

  1. Financial intelligence system mappedCompleted milestone

    The first design set the core rules: local-first data, full provenance, human-earned trust, and automation that increases only after demonstrated accuracy.

  2. Tiller trust gap provedCompleted milestone

    Statement reconciliation confirmed that the convenient feed was incomplete. Monthly statements became the verification layer instead of a file cabinet nobody opens.

  3. Statement-backed database builtCompleted milestone

    Transactions from multiple institutions landed in a local SQLite database with source provenance, categorization, and tax metadata.

  4. Security boundary definedCompleted milestone

    Credentials stay outside model context, statements are masked before parsing, and any shared web surface must be authenticated and least-privilege.

  5. Goals + monthly review surface builtCompleted milestone

    Goal tiers, watched spending categories, balance snapshots, health metrics, and a partner-friendly monthly review were wired together.

  6. Plaid medallion pipeline builtCompleted milestone

    Statements, Plaid, and Tiller became independent raw layers feeding one rebuildable transaction table with explicit source priority.

  7. Prototype audited as a systemCompleted milestone

    A full audit separated the real working foundation from stale status claims, brittle merges, missing operating cadence, and security work still needed before shared access.

    Changelog entry →
  8. Deterministic, self-checking data loopUpcomingUpcoming milestone

    Freshness, reconciliation, categorization coverage, and source conflicts become explicit health gates. A rebuild must reproduce the same totals without manual gold-layer patches.

  9. Family finance rhythms sustained for three monthsUpcomingUpcoming milestone

    Reporting, budgeting, long-term planning, and goal tracking each run on the cadence they require for three months, with decisions and commitments carried forward.

  10. Recommendations earn the right to actUpcomingUpcoming milestone

    The system proposes specific transfers or spending adjustments with traceable evidence. Nothing moves without explicit human approval.

Quest log

The prototype became a systems audit

The July audit found a substantial build: 5,862 synthesized transactions and 160 categorization rules, but no trustworthy operating loop. A failed derived-layer repair proved that fixes must live in durable rules.

The philosophy became operating rules

Financial freedom, resilience, lifestyle boundaries, and redesign triggers were written down, then translated into goal tiers, income assumptions, budget thresholds, and allocation rules.

The ledger became vendor-independent

Statements, Plaid, and Tiller became independent raw inputs feeding one synthesized ledger. Vendors could now be replaced without surrendering the family record or its provenance.

Goals became a shared review loop

Goals, watched spending, live metrics, balance snapshots, and commitments came together in one review surface. The breakthrough was treating family finance as a recurring decision ritual, not another dashboard.

Essays from this quest

None yet - mature quest-log threads graduate here.