Methodology
We map what the market has already said. The point is what it has not.
We map what is already said.
Only what vendors publicly claim. Every claim cited to its page, every product placed on the DAP Standard.
We find the white space.
Where the public record is silent: the questions nobody has asked yet, and the tools nobody has built.
Discovery is the bottleneck.
Knowing which questions are worth asking is the scarce skill. The Ledger is how we find them.
What we read
Public material only: product pages, documentation, release notes, regulatory filings and package registries.
Nothing behind a login, a sign-up form or a paywall. A site that asks automated readers to stay out is left alone. A block is recorded, never worked around.
Every source is checked against its terms first. If a source’s terms limit reuse, nothing from it reaches anything public.
How a capability gets in
- Capture: an exact, dated copy of each page, with a fingerprint.
- Compile: a model reads each page twice and writes short claims. Every claim cites the passage it came from. A claim with no passage is dropped.
- Check: fixed rules check every batch against its source. A batch that fails any rule goes to a person.
- Map: products and claims go onto the DAP Standard, as set out below.
How it maps to the DAP Standard
- Products: each one is placed on the DAP Standard 2026.2, by what it is.
- Claims: when a claim says who a capability is for, that is recorded on the Standard too.
- Capabilities: each claim is matched to one capability on DAP’s own list of 118, in 12 families, built on the Standard.
How we test a rebuild
A separate process tries to rebuild each capability from the checked claims alone. It never sees the vendor’s pages, code or patents.
- Rebuilt: a working specification and passing tests, from public claims alone.
- Partial: the core rebuilt; something it depends on did not.
- Did not compile: the public claims are not enough.
- Not attempted: the claims are too vague to test, or only a patent describes it.
Anything short of rebuilt gets a reason: data, integration, operations, trust or judgment.
Anonymize: the golden rule
We never name a vendor or a product, in a page, a chart, a file or a table.
Every number we publish about vendors rests on at least three products. Below three, we hold it back.
What we never do
- Contact a vendor about the Ledger.
- Read gated material, or work around a block.
- Publish a vendor’s own words.
- Put anything we rebuild into a DAP product. (We do not sell products. We are not a SaaS company, and we never will be.)