The action system
(cadence, priority, check_name, status, detail, action, metric)
cadence: daily | weekly | monthly | quarterly | yearly
status: action_required | attention | ok- Daily: approvals, uncategorized spend, stale sync.
- Weekly: unassigned money, overspent categories, transfer suspects, cash buffer.
- Monthly: budget set, reconciliations, recurring changes.
- Quarterly and yearly: tax windows and deadlines from a reminders table, with completions so a done window stays done.
Nothing is stored. Every check is computed live from the modeled tables, so there is no queue and no stale state. Thresholds live in one settings row.
The bot
Signal has no bot API, so the bot runs its own Signal account through a signal-cli sidecar. It posts the daily brief at 07:30, the weekly review Sunday evening, and the monthly review on the first. Slash commands cover actions, health, FIRE, cash, spend, the calendar, and a shared todo list.
It connects as a least-privilege role, writes only to its own schema and one completions table, and logs everything it hears and says to a table Metabase can read.
Audio · 3 minMatching cadences to household rituals
Free to borrow for your feed · Square edition
Where you are: a group chat that nags, kindly and on schedule. Next, it answers back.
