Integration runbook
The data engineering team running Snowflake, Databricks or an EDW.
Treat TWMD as an upstream source with lineage, documentation and verifiability.
Each step below says which surface carries it and whether it works today. Every "Works today" step was probed against the live API on 2026-08-21; the rest say what is missing. Nothing here is written in the present tense because it is planned.
Land the Parquet files in your object store and mount them as an external table; the files carry their own schema.
As above: an enterprise delivery that a public probe cannot reach.
Each dataset has a Gebru-format datasheet: composition, collection, cadence and freshness, point-in-time semantics, recorded gaps, licence and access. They live at /datasets/<slug>/datasheet in both languages, composed from the registry and the coverage measurement rather than written per dataset, so they cannot say something the registry does not.
Any batch can be checked against /v2/proof/inclusion to show a row really is in the signed snapshot. The hashing rules are at /v2/proof/recipe and the signing key at /v2/proof/public-key, neither of which needs a key.
A consistency proof shows one tree is an extension of an earlier one — that history was not quietly rewritten.
Not served. The checkpoint's own does_not_prove says it cannot establish this. See the Standards & Interop page.
Emit provenance as W3C PROV so Collibra or Purview can ingest it directly.
The lineage available today is the lineage and source_role fields in the REST envelope. Asking for ?format=prov-jsonld returns 400 unsupported_format and names what is supported, csv and ndjson, so there is no way to think you received PROV-O and actually receive ordinary rows. (Before 2026-08-21 the parameter was silently ignored, which was the misleading version.)
A push notification when a batch lands, with a documented schedule SLA.
Not served.
There is no VPC peering, private link or on-premises delivery. The two delivery modes are the SaaS API and files.
For how the proofs map onto published standards, see Standards & Interop.
