{"id":"corpus-coverage","type":"module","title":"Corpus Coverage (public, audited)","status":"ga","audience":["prospect","analyst","buyer"],"scope":"both","tier_min":"free","aliases":["10b","coverage"],"summary":"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.","keywords":["coverage","public","snapshot","hash-chain","methodology","falsifiable","dbt"],"body":{"what_it_is":"The one surface Klarum publishes *outward* about its own data, and the only\nplace in the product where a figure is accompanied by the query that produced\nit. A public, per-market, per-source table of what the tender corpus actually\ncontains - notice counts, open-now counts, bid-decision field fill rates,\nthree separate document-availability cells and freshness distributions -\nrendered from a hash-chained, append-only snapshot that any third party can\nre-derive. Deliberately unauthenticated: a login wall would make every\npublished figure unfalsifiable.\n\nServed at `/coverage`, backed by a public read API for definitions,\nsnapshots and snapshot verification.\n","what_it_helps_users_do":"Answer \"do you cover my market\" with a number instead of an assurance, and\nlet a buyer or an analyst check that number without taking our word for it:\nre-hash the payload, walk the chain, and re-run the published SQL against\ntheir own copy of the same public feeds. It is also the asset the published\nmarket research and organic acquisition are built on.\n"},"engines":[],"integrations":[],"capabilities":[{"id":"coverage-metric-registry","type":"capability","title":"Metric registry","summary":"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.","status":"ga","scope":null,"keywords":["definitions","sql","denominator"],"body":null},{"id":"coverage-hash-chain","type":"capability","title":"Append-only hash chain","summary":"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.","status":"ga","scope":null,"keywords":["hash-chain","append-only","trigger","verifiable"],"body":null},{"id":"coverage-publication-gates","type":"capability","title":"Four publication gates","summary":"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.","status":"ga","scope":null,"keywords":["dbt-test","fingerprint","gates"],"body":null}]}