Coming soon · gated on the loop closing

The record your operation
already produces.

Every priced quote, delivered job and collected invoice writes one line to one unit's ledger. Do that for a year and you are holding something no lender has ever been able to get from an operator your size: per-unit performance, in order, that nobody could have edited after the fact.

01 · What it is

Not a report. A record.

A report is generated, so it can be generated differently. The ledger is append-only — a correction inserts a new line that supersedes the old one, and both stay. That property is worth nothing to you operationally and everything to whoever is deciding whether to lend against it.

SIX MODULES WRITE CPQprice Contractsterms Plan & Flowcost Cash Opscash Agentic ABMCAC Occupancydemand ONE UNIT’S LEDGER · APPEND-ONLY #0001revenue+ 48,200.00 #0002direct_cost− 21,900.00 #0003deploy_cost− 6,340.00 #0004acquire_cost− 4,110.00 #0005run_cost 1,020.00 superseded #0006run_cost− 1,140.00 supersedes #0005 · both retained contribution+ 14,710.00 payback11.4 months ATTESTED Signed claim over a set of events TAMPER-EVIDENT DISCLOSED SELECTIVELY PREDICATE “AR health ≥ 70%” TRUE books never opened LENDER Prices the risk weeks, not months
One unit, six modules writing, a correction that supersedes rather than overwrites — then a predicate proved without opening the books.
02 · Why it is worth anything

Asset-heavy operators are data-rich and capital-starved.

The two facts are related. A lender cannot price what it cannot see, so it prices the uncertainty instead — which is why a $30M manufacturer with real assets and real contracts waits months for a facility a software company gets in days.

What a lender asks forWhat you can send todayWhat the ledger sends
Per-unit performanceAn export, reconciled by handEvery event, in order, with lineage
Cohort behaviourA spreadsheet someone built onceUnits grouped by vintage, computed live
Realised vs modelledTwo numbers, no link between themActual and Target on the same object
Proof it was not editedAppend-only, supersessions recorded
Without opening the booksNot possibleA predicate, proved and signed
Selective disclosure is the part operators care about. You are not handing a lender your customer list, your margins or your pricing. You are proving one statement — that receivable health clears a threshold, that a cohort paid back inside a window — and proving it in a way they can verify without trusting you.
03 · Honest status

The engine exists. The ledger does not, yet.

We would rather tell you exactly where this is than let a roadmap page imply more than it should.

Built and tested

Attestation, selective disclosure, the proof-link flow and lender-facing tiers all exist in the platform with tests behind them. This is not vapour — it is the part that was easiest to build.

Not yet true

The ledger those tools sign over is empty. Events still live across six separate tables from before the ontology existed, and the backfill has not run. Until it does, any per-unit history is partial and we will say so on the page rather than in a footnote.

What unlocks it

One operator running the closed loop for long enough to have a record worth signing. That is the gate — not engineering. It is why the loop is priced whole and why we do not sell the capital story in a first conversation.

What we will not do. Offer a sample data tape we cannot produce, or quote a rate we have not been given. When a lender has actually priced off one of these, that number goes on this page with the date attached.
04 · Where it sits

Layer six. Everything under it comes first.

This is the last layer of the substrate for a reason: it is a consequence, not a product. Every layer beneath it has to be running before there is a record worth attesting.

The ledger starts with one quote, held to a floor.

A free Margin Scan tells you what your pricing is leaking. The record begins the first time you act on it.