mintmark

mint·mark, n.

The mark a mint strikes on a coin,
certifying it was struck true.

Mintmark is a personal-finance platform built on one refusal: nothing reaches the ledger unverified. Every number traces to a document. Machines prove the arithmetic. An AI reviewer reads every change and judges whether it is what it claims to be — and when it isn't sure, the change waits for a human. The daily commit is the mark.

How the system works Why it works this way

Three refusals

No invented numbers

Every row comes from a statement, an export, a tax form, or a bank feed — with the source recorded on the row. No plugs, no estimates, no "close enough." A figure that cannot be sourced does not enter the book; it enters a review queue instead.

No unproven ledger

Documents print balances. Mintmark rebuilds the ledger from scratch every day and reconciles it against hundreds of those printed anchors — to the cent. A mismatch anywhere stops the commit everywhere.

No absent reviewer

An AI reads the full diff of every rebuild with memory of every past decision. It approves, or it stages the work on a branch for a human. A gate that opens when the reviewer is absent is not a gate — so every failure mode fails closed.

A day in the life of the book

the packet lines arrivals riding at anchor the Tidewaiter declared, or held the book rebuilt the checks all three green the braingate reads the diff commit the mark stage a branch the Remembrancer
Records arrive on the packet lines — each rail its own scheduled service — and ride at anchor until the Tidewaiter clears them against their own declared totals. The book rebuilds, the checks run, the braingate reads — and the day ends in a struck mark, or a staged branch worked out with the Remembrancer.

The whole run happens in the cloud on a schedule, and the owner gets a one-line digest in Slack. On a clean day that is the entire interaction: one line, already verified.

The cast

The braingate verdict gate

A headless AI reviewer that reads each rebuild's evidence and diff, armed with read-only tools and its own long-term memory. Three verdicts: commit, stage, block. Unsure means stage. It has caught real data corruption that no mechanical validator covered.

The Exchequer issues court

The docket of open matters, split on one line: is the book false, or is something merely late? False blocks and no human can close it. Late gets a fingerprinted docket entry with a per-class deadline — snoozeable, discussable, self-resolving when the condition clears.

The Remembrancer chat brain

Named for the medieval officer who kept the record of outstanding matters. Mention it in Slack and it opens a working session in a fresh clone of the book, applies the decision you state, re-runs the validators, and hands back a branch. It never writes the mainline — you merge.

The Tidewaiter works the packet lines

The customs officer who boarded arriving ships on the tide, before their cargo touched the dock. Everything the packet lines land — bank feeds on their daily runs, statements through the ingester — is opened here, and every document must balance against its own printed totals — declare itself — before its rows are admitted. Nothing enters the book undeclared. Tidewaiters have always answered to the Exchequer.

What it is not

Mintmark is not a budgeting app and does not want your attention. There are no streaks, no nudges, no gamified savings goals. It is bookkeeping infrastructure: an auditable ledger with a staff — a builder, an auditor, a reviewer, a clerk — that runs while you sleep and asks for you only when a real decision needs an owner.

It is also, at present, a personal system rather than a product. The engine is built tenant-free — a strict boundary keeps every personal value in a separate private repository, enforced by an automated leak audit — so that the machinery could serve more than one book. Whether it ever does is an open question.