Use cases · Why Onnie

Finances

Money work with durable records

Money work dies when numbers live in spreadsheets agents can’t see and reminders live in your head. Keep the books as durable records — then let Routines and agents act on them.

Tables · lawWork · motionRoutines · cadenceConnectors · loop

// friction

Spreadsheets aren’t a system

Invoices, categories, and “I’ll chase that Friday” scatter across sheets, email, and chat. Every AI session starts cold. Nothing compounds.

// on onnie

Tables as law, Work as motion

Put financial truth in Tables. Bind recurring money jobs to Work and Routines. Connectors reach tools you already use; agents help without inventing a second ledger.

This is not “AI accounting.” It is durable records the OS can move — chase, explain, gate — without copy-paste archaeology.

01Tables02Work03Routines04Pages05Connectors · Agents

// workflow on the os

How money actually moves

Click each step. Law lives in Tables — motion in Work — not a spreadsheet cosplay.

The ledger is a Table — not a private sheet

Invoices, cash, categories: one durable grid agents and humans share. Status and due dates are columns — not chat memory.

// a week in the books

Residue, not reconciliation theater

MONBooks open

Invoices Table filtered open/due. Chase Work goal set from real rows.

Tables · Work
TUEFacts in the loop

Connector skim suggests two row updates. Nothing writes without you.

Connectors · Tables
WEDRoutine pulse

Morning money routine lands digest on Chase Work. Open loops without a panic.

Routines · Work
THUNeeds you

Approve the Northwind send. Judgment stays human; Table stays law.

Work · Agents
FRIExplain

July digest Page cites paid/open. Same room next week — no cold start.

Pages · Tables

// proof · tables ledger

The ledger is in the room — not in a private sheet

A real Tables glance: primary client, amount, status, due, and a Work link when chase is live. Residue caption ties the grid to motion — not a bare spreadsheet aesthetic.

Invoices
GridBoard
Status · open + due6 rows · 2 need chase
OpenDue / overduePaidTable = law · Work = motion
InvoiceClientAmountStatusDueWork
INV-1042Northwind$4,200.00dueJul 12→ Chase AR
INV-1048Local co-op$640.00dueJul 18→ Chase AR
INV-1051Studio retain$1,800.00openAug 01
INV-1039Acme pilot$9,500.00paidJul 01
INV-1055Workshop fee$320.00openAug 05
INV-1028Legacy retainer$2,100.00paidJun 15
Invoices stays the system of record — Chase overdue AR is Work motion on due rows · Routines keep the filter warm · agents draft; you gate send. Not a private sheet agents can’t see.

// nearby domains

Same OS, different residue

Other use cases that touch money motion or durable records — different jobs and proof objects.

// faq

Common questions

Yes. Financial work sits on Work with durable table records and digests so status is not trapped in a private spreadsheet chat.

Put the books where work can reach them

Stand up an Invoices Table, bind chase Work, let a Routine keep open/due warm.