Dartmouth Advisory PartnersDartmouth Advisory PartnersContact
Dartmouth Advisory Partners
Contact
Menu
Contact

Data / The Ledger

The Ledger is live.

Ledger

Everything published compiles.

Live

Since 17 October 2026 / Updated weekly

See the climb

The point

  1. 01

    We map what is already said.

    Only what vendors publicly claim. Every claim cited to its page, every product placed on the DAP Standard.

  2. 02

    We find the white space.

    Where the public record is silent: the questions nobody has asked yet, and the tools nobody has built.

  3. 03

    Discovery is the bottleneck.

    Knowing which questions are worth asking is the scarce skill. The Ledger is how we find them.

Read the paper Read the methodology

The climb

The market publishes. We compile it.

On 17 October 2026 the Ledger read its first page. It reads what institutional software vendors publish, turns each capability into a cited record, and tests whether that capability can be rebuilt from public material alone.

The lake, day by day

Claims compiled since 17 October 2026

Claims compiled rose from 97 on 17 Oct 2026 to 3,228 on 30 Oct 2026.

View as table
Claims compiled since 17 October 2026
DaySources readPages compiledClaims compiledProducts mappedCapabilities mappedRebuild tests run
17 Oct 202655971140
18 Oct 202655971140
19 Oct 20262626805187029
20 Oct 20262627851197029
21 Oct 20262627851197029
22 Oct 202630351,0672272134
23 Oct 202630351,0672272134
24 Oct 202630351,0672272134
25 Oct 2026851002,3796187185
26 Oct 2026851012,3996187271
27 Oct 2026851022,4196187271
28 Oct 2026851022,4196187271
29 Oct 2026911293,0096489329
30 Oct 2026911393,2286489359

Source: the Ledger lake, as of 30 Oct 2026.

Sources read
91
Products mapped
64
Claims compiled
3,228
Rebuild tests run
359

Follow the climb. Every run adds to it.

The method

How it works

  1. 01

    Read

    Public material only: product pages, documentation, release notes, regulatory filings and package registries. Nothing behind a login or a paywall. A site that asks automated readers to stay out is left alone.

  2. 02

    Capture

    An exact, dated copy of every page, with a fingerprint, so each record traces back to what was published.

  3. 03

    Compile

    A model reads each page twice and turns it into short claims. Every claim points to the passage it came from. A claim with no passage is dropped.

  4. 04

    Check

    Fixed rules check every batch against its source. A batch that fails any rule goes to a person.

  5. 05

    Map

    Each claim is matched to one capability on DAP’s list of 118, in 12 families, on the DAP Standard 2026.2.

  6. 06

    Test

    A separate process tries to rebuild each capability from the checked claims alone, never from the vendor’s pages. What does not rebuild gets a reason: data, integration, operations, trust or judgment.

Anonymize: the golden rule

We never name a vendor or a product. Every number we publish about vendors rests on at least three products. Nothing we rebuild goes into a DAP product. (We do not sell products. We are not a SaaS company, and we never will be.)

Read the methodology

You buy the outcome. We compile the system that delivers it, and the evidence that it did.

Discover a higher standard