Where This Is Going

Shipped

Running today. You can test every one of these in the sandbox, and each is backed by a receipt in the product itself.

• The system itself refuses an unbalanced entry before it can be saved. The rule is built into the foundation, not into a screen that can be bypassed.

  The rule lives in the foundation of the system, so nothing built on top of it — including next year's features — can route around it.

• Close readiness is read from the books themselves, so a step cannot be ticked off while the work behind it is still undone: unposted entries, unreconciled accounts, subledgers that don't tie.

  Readiness is computed from the ledger rather than stored as a checkbox, so it cannot be ticked away.

• Analytical review runs over the posted books and surfaces what looks wrong, whether unusual amounts, shapes or timings, with every finding resolved on the record.

  A ledger that keeps its complete history is what an analytical review needs to have anything to compare against.

• Budgets, forecasts and variance analysis work off the same ledger the statements come from, so plan and actual cannot disagree about what actually happened.

  Plan and actual read the same journal lines, so a variance is a real difference rather than two systems disagreeing.

• Borrowing-base certificates are computed from live AR and inventory against your facility's own advance rates and ineligibility rules.

  Live AR and inventory are already in the system under real controls, so the certificate is derived rather than assembled.

• Every pack you issue is recorded with a unique seal, so you can say exactly what you sent, when, and prove it has not changed since.

  Every issued document is sealed and registered at the moment it is issued, which is the only time that record can be made honestly.

• A recipient checks a delivered package on their own computer, with a tool that travels inside the package, installs nothing and contacts no one.

  Graduated from building on 2026-09-03: the checking tool travels inside every sealed package, so a recipient runs it without an account here and without contacting us.

• A recipient can ask whether the package they hold is still the current one, and be told if it has been superseded or if the books have moved since it was issued.

  The issuance register already records what was sent and when, so answering whether a held copy has been superseded is a lookup rather than a new system.

• A readiness score answers whether the books could go to an auditor today, from eight signals: open anomalies, unexplained movements, control exceptions, attestation coverage, close status, depreciation posted, approval backlog and open review notes. It refuses to show a number when too little has been measured.

  Eight signals the close already computes, read together and recorded on a schedule, so the score is a fact about the books rather than a feeling about them.

• An auditor works the trial balance in one place: what supports each line, where the gaps are, tickmarks against the lines they have tested, and a seal that freezes the schedule they concluded on under two signatures — against live records rather than exported spreadsheets.

  Graduated from building on 2026-09-04: the coverage engines the close already runs, read across the whole trial balance at once, which is the view no single workpaper could produce.

• An independent timestamp authority attests that a package existed on the date it claims. The recipient checks that attestation with standard tools, against a certificate fetched from the authority rather than from us — so the last step of the proof rests on someone we do not control.

  Graduated from building on 2026-09-04: the verifier already proved a package was unchanged, and a signature from an authority we do not control is what extends that to proving we did not rewrite it ourselves.

• You can ask not just what the books say now, but what they said on any date since the books were opened here — and see exactly what changed between the two.

  Graduated from building on 2026-09-04: history is never overwritten and every change is sealed into the record, so reconstructing a past date is replaying what is already kept rather than storing a second copy of the books.

Building

Under active development, and the reason each is tractable is that the foundation it needs already exists. Design partners shape these — if one of them is the reason you would buy, tell us.

Nothing sits here today — every line that was in this column has shipped, the last of them on 4 September 2026. That is a statement about the labels on this page, not a claim that the product is finished; work continues, and the next thing we commit to publicly will appear here with its label before it appears anywhere else on the site.

Where This Is Going

Direction, not commitment. These are the reasons the earlier columns are built the way they are, and none of them is something you can buy today.

• The destination is routine accounting work that runs itself, through the same approvals and the same ability to undo that a person is held to.Where this is going

  Automation already posts through the same single door, approvals and ability to undo as a person — the guardrails are the part that is built.

• The destination is a network where the recipient of a statement — a lender, an investor, an acquirer — verifies it directly, and trust stops being bilateral.Where this is going

  A recipient can already check a document we issue without an account here. What a network needs beyond that is other parties doing the same, which is adoption rather than engineering — so it stays direction.

• Privacy-preserving benchmarking against comparable companies, computed without any party handing over its books.Where this is going

  Comparable data has to be structured and trustworthy before comparing it means anything.