Sketch system
TallyHouse
A household is not a chart. It is a small, governed economic unit with members, obligations, roles, and decision rights — and AI agents are about to start spending against it.
A governance layer for household finances. The policy boundary that decides what a person, a partner, or an AI agent is allowed to spend, with what authority, and against which obligation.
Most personal finance software answers what did I spend? TallyHouse is an attempt at a different question: who is allowed to spend household money, under what conditions, against which obligation, and with what accountability?
It begins with familiar primitives — income, recurring obligations, budgets, alerts, household members — and uses them to model the household as what it actually is: a small, governed economic unit with roles, redundancy, and decision rights.
Why now
AI agents are moving from advice to action. They will plan, book, subscribe, renegotiate, and pay on a household’s behalf. Without a governance layer, that future is unsafe by default — agents acting on stale context, optimising the wrong thing, committing the household to obligations no one approved.
TallyHouse is designed to be the termination point before spend: the small policy boundary every actor — human, partner, caregiver, agent — passes through before money moves.
What it explores
- The household as the unit. Not a single user with a dashboard. A household with members, roles, dependents, obligations, and shared continuity.
- Policy as plain language. Rules a household can actually write: groceries under a routine cap auto-approve; new merchants need a second pair of eyes; emergency reserves are protected unless this is an emergency.
- Continuity over optimisation. The first job is to keep the household functional under stress — known obligations, assigned ownership, redundancy if the primary person is unavailable.
- Agents as governed actors. An agent is a delegate, not an owner. Identity, scope, limits, audit trail, revocation — the same shape as any other principal.
- Decisions that are richer than allow/deny. Approve, deny, require a second approver, approve with a cap, approve from a specific envelope, delay until safer, escalate.
- Calm by construction. The interface should feel protective and clarifying, not punitive or noisy.
Discipline
There is a long surface area here — projections, simulations, agent marketplaces, household-to-household primitives. None of it ships before the wedge: a household that becomes legible to itself, with a small policy engine and an audit trail it can trust. Everything downstream depends on that being real.
Status
In ideation. Independent writing on household governance, agentic spend boundaries, and continuity will surface alongside the product as the thinking matures.