The position, the readers it serves, and the commitments that decide the architecture. Everything after this page is evidence for it.
Every platform in this market sells the transaction. A permissioned vault, an audit log, a Q&A thread — and they compete, genuinely, on how much control survives a download.
But that is the last ninety days of a process whose price was decided in the two years before them. An owner-operated business sells for what a buyer can underwrite: numbers that reconcile, add-backs that survive a challenge, customer concentration that is not fatal, a key person who is not the whole company. Nobody sells that work, because it is judgement rather than storage, and judgement does not demo.
The judgement is the product. The vault is a feature of it.
Grouped by the eight stages a mandate moves through, because that order is the product — the state machine is the single authority on whether a move is legal, and a company cannot enter MARKET until every blocking readiness gate is green.
Nine platforms, drawn from the market scan. Read the bottom half rather than the top: almost every rival is the same object — a permissioned document vault with an audit log — and they separate on how much control survives a download. The rows they cannot fill are the ones upstream of the vault.
Rival capabilities are from published material and the market scan of August 2026; pricing models and post-download control are the two dimensions buyers report as decisive.
Three phases, divided by the READER each one adds rather than by the features it contains. A feature list reorders itself every quarter; a reader is a decision about who the product is for, and it holds. What is already built is summarised per phase and enumerated under Capabilities — it is not repeated here, because the same list maintained twice is the same list wrong in one place.
Tick remaining items as they land; progress is saved in this browser.
Nothing ticked yet.