01Trust
Four pages. Two of them are mostly gaps, and say so.
What we will put in writing.
Data ownership, execution measurement, security and what is not built yet. The point of this section is not to reassure you — it is to be specific enough that you can check.
- Data ownership and exitYour data is yours, and this page says what that means in entities and file formats rather than in a sentence.Read
- Execution transparencyWhat we measure about execution and what we do not measure yet, with every published figure carrying its own definition.Read
- Security and custodyWhat is settled about credentials, access, custody and withdrawal authorisation — and what is not settled about the operational detail behind them.Read
- RoadmapWhat does not exist yet, named — dated to the quarter, which is the precision we have.Read
02Current state
Counted on the index, not buried one page in.
How much of this is actually written.
- 4
- questions across data ownership, security and the roadmap that cannot be answered honestly today. Each one is on its page with what has to exist first, rather than answered with something that sounds like an answer.
- 4
- execution metrics defined but not published. A figure appears only once it carries its measurement endpoints, its statistic, its sample window and its sample size — until then it shows as a gap.
A trust section whose own state is unclear is not a trust section. If a gap here decides your purchase, ask about it directly.
03Next
The one worth reading first.
If you are evaluating a proprietary stack, the question underneath all the others is whether you can leave. That page is written as a specification rather than a reassurance, and it is the one to start with.