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, and an AI reviewer judges every change — unsure means a human decides. The daily commit is the mark.

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 queue at anchor the Tidewaiter inspects each arrival the Binder assembles the book the Gauger to the cent the braingate reads and rules commit the mark struck the Exchequer files it on the docket the Remembrancer the thread stage for review the owner merges

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 Tidewaiter works the packet lines

The customs officer who boarded arriving ships on the tide. Everything the packet lines land 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.

The Binder builds the book

Bookbinding is assembling pages into a volume; the Binder does it to the ledger daily, from nothing — merge, transfer-matching, tagging, every row from a source. Any day's book can be reproduced by replaying its inputs; a hand-fixed number would not survive the night.

The Gauger runs the checks

The excise officer who measured every cask against its declaration: hundreds of document-printed anchors matched to the cent, and the integrity invariants — no money from nowhere, no shares never bought, no transfer half-explained. No opinions; only arithmetic, and a closed gate when it fails.

The Exchequer issues court

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

The braingate verdict gate

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

The Remembrancer chat brain

The medieval officer who kept the record of outstanding matters. Mention it in Slack and it works 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.

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, at present, a personal system rather than a product — but the engine is built tenant-free, with an automated leak audit holding the boundary, so the machinery could serve more than one book. Whether it ever does is an open question.