Klarum

Corpus Coverage (public, audited)

Generally available
Supplier and issuer
From free

The one surface Klarum publishes outward about its own data: a per-market, per-source table of what the tender corpus contains, rendered from a hash-chained append-only snapshot anyone can re-derive.

Catalogue id
corpus-coverage

Description

What it is

The one surface Klarum publishes outward about its own data, and the only place in the product where a figure is accompanied by the query that produced it. A public, per-market, per-source table of what the tender corpus actually contains - notice counts, open-now counts, bid-decision field fill rates, three separate document-availability cells and freshness distributions - rendered from a hash-chained, append-only snapshot that any third party can re-derive. Deliberately unauthenticated: a login wall would make every published figure unfalsifiable.

Served at /coverage, backed by a public read API for definitions, snapshots and snapshot verification.

What it helps users do

Answer "do you cover my market" with a number instead of an assurance, and let a buyer or an analyst check that number without taking our word for it: re-hash the payload, walk the chain, and re-run the published SQL against their own copy of the same public feeds. It is also the asset the published market research and organic acquisition are built on.

Capabilities

  • Metric registry

    Generally available

    Each metric's exact SQL and its plain-language meaning, denominator and exclusions live in one object, so a number cannot be computed one way for the page and described another way in a deck.

  • Append-only hash chain

    Generally available

    Snapshots are chained with the same integrity primitive as the workspace audit chain, append-only at the database with a unique prev_hash and a single-genesis index so the chain cannot fork.

  • Four publication gates

    Generally available

    Nothing publishes unless dbt data tests are green, the deployed transform fingerprint matches the checkout, the build is identifiable and the ingestion run was green.

Keywords

coverage, public, snapshot, hash-chain, methodology, falsifiable, dbt

Provenance

This page renders a published artifact. Read the same records as JSON if you would rather check the source than the page.