Home · Builds · Cadenced action system

Build

A rules engine that tells you what to do next.

Every check is a view. Every view emits the same row shape. Items appear when something needs attention and disappear on the next hourly sync after you fix it.

Scratch cut · 1:33 The part 7 scratch cut: the brief lands, /actions lists the flagged transaction, the sync runs, the item is gone, then the seven columns the bot read. Demo data, scratch narration.

The shape of a check

Every check view returns the same seven columns, so the Action Center is one union and one filter.

(cadence, priority, check_name, status, detail, action, metric)
status: action_required | attention | ok

What it checks

One row from the weekly view as seven labeled cells with sample values from the demo budget.
Annotated diagram of a single row from the weekly view, each column labeled, grayscale. Also as a square.

What it taught me

Computing live beats storing state. There is no queue to clear and no job to re-run. The thresholds live in one settings row, which is the only thing a household has to agree on.

Tunable settings

Stale sync hours, uncleared days, reconcile days, cash buffer target, transfer match window, and the tax reserve percentage. All in actions.settings.

Audio · 2 minWhy the cadences match the household's rituals, not the data's
Scratch narration Daily is a glance, weekly is a conversation, monthly is a decision, quarterly is a payment.
All buildsNext build · Signal home-office bot

Write to me

I built this for a household. Imagine it pointed at your company.

Fractional CTO and CFO engagements start with a short call. No deck required, no pitch either. Bring the number you do not trust.

Tell me what is stuck