A personal build, documented in public
I wanted my agents to understand my money without asking me to trust a black box.
So I built a ledger that keeps the receipts: what the provider said, what a statement proved, what I corrected, and what a model merely suggested.
ROWAN HOUSEHOLD · SYNTHETICCASE 04
the number is not the answer—
the trail behind it is.
Provider observationkept unchanged
Closed statementcycle proven
Agent explanationderived, not truth
EVIDENCE
ATTACHED
Why it exists
The feeds were useful.
They were not complete.
A connected card once missed transactions that were plainly printed on the closed statement. Pending purchases sometimes vanished. One model confidently called a card payment “spending.” Each problem taught me the same lesson: a finance agent needs a memory of evidence, not just a clever prompt.
Ledgerglass is the system I ended up building around that lesson. It uses deterministic math for financial answers and lets agents operate around the ledger—investigating, retrying, and explaining—without quietly rewriting the facts.
Three promises I can actually test
01 · experimentalA forecast that knows what it does not know
Wave 4 keeps owner and statement schedules separate from detected candidates, expands deterministic occurrences, and projects committed, expected, and possible paths per account and currency. A private post-sync scout may activate only mature derived patterns in the expected scenario behind deterministic evidence gates; it cannot create committed authority or ledger facts. The reusable public subset exports dependency-free recurrence, integer-minor-unit forecast, and backtest arithmetic with synthetic vectors and private/public parity proof; live adapters and orchestration remain private.
See the proof → A documented failure class, reproduced with synthetic data
The feed missed three purchases
A connected credit card stopped including several posted purchases near the end of a closed cycle.
Inspect all six cases- 01
What made it hardThe balance was real, but the transaction feed could not explain it.
- 02
What changedLedgerglass matched supported rows, added three statement overlays, and left one uncertain provider row out of the effective cycle.
- 03
What stayed uncertainThe uncertain row remains visible for later provider or owner evidence.
This is not a service pitch
It is the public implementation and engineering record for a system I use myself.
The private installation holds the real data and operational machinery. This repository holds the reusable core, contract evidence, design decisions, failures, and enough proof for someone else to inspect the implementation.