Proven core

With AI you could build a ledger from scratch. Here is what you would be building.

What a ledger must get rightWhat goes wrong when it does notStatus here
Value dating: trading date and value date on every movement, every property a date series, back-dated corrections re-accruedA rate stored as a column; interest wrong by a day, on every account, discovered at month-endCore, event-sourced, tested
Accrual and compounding across day counts and conventionsRounding drift that never reconcilesCore, five conventions from the ISO code set
Day-end that can run forward and replayForecasts disagree with what actually postsOne code path, parity tested
A sub-ledger that balances per entity and per currency, and reconciles to your general ledgerManual journals, FX result in the wrong place, a month-end that never tiesCore, posting rules configured, journal export
Four-eyes control on the operations that matterA single clerk moves a limitDeny by default, authorisation eligibility derived
Multi-currency revaluation and period closeA profit that disappears when the rate movesCore, in the books
Schedules on irregular frequencies with multiple calendarsPayments on public holidaysCore, configured per account
Structures and legal entitiesThe deal you administer on a spreadsheetThe reason this engine exists
The guard rails

Architecture tests

Cross-feature references, static handlers and untyped ids fail the build.

Permission catalogue

A command with no permission entry is a build failure, not a hole.

Reachability gate

A handler no test dispatches fails the gate.

Standards register

Every deviation from a standard is a decision record.

Decision records

506 of them, the design history of the engine.

Test suites

9,227 tests, counted on every deploy.

The suites →
Greenfield or proven

A greenfield build gets you a ledger in months and the edge cases over years.

The edge cases are the product. The mistakes surface in month-end runs, audits and customer statements, and each is a data fix on a live book. Twenty-five years in production at one of the world's safest banks produced a handful of true defects. That record is the asset; the code is how it is delivered.

What this means for you: you get the years, not just the code. Your AI works inside the rules those years wrote.

Proven core, guarded development, AI on topThree stacked layers: AI on top, guarded development in the middle, the proven core at the bottom.AI on topskills that read the design and build within itGuarded developmentdecision records, four-seat review, architecture tests, gates on every changeProven coretransactions, accounting, value dating, day-end, twenty-five years in production
Three layers. The bottom one is the value.