Maintenance · UK
Every data-backed claim must trace from the current E2 manifest to one admitted artefact, source snapshot and transformation method. The trace retains source URL, version, retrieval time, content hash, licence, freshness and quality status. A broken trace removes the affected value; it does not become zero or inherit provenance from a nearby record.
Ofgem: Energy price cap unit rates and standing charges
Reviewed
For UK EV data reviewed on 13 August 2026, provenance begins at the single E2 build manifest and follows the listed artefact to its source version, public locator, content hash, licence and transformation method. Nulls keep reason codes and never mean zero. The limit is snapshot integrity: mixed builds, fixtures, missing hashes or uncovered fields are rejected rather than repaired editorially.
Ofgem: Energy price cap unit rates and standing charges
Consumers enter through one validated manifest and do not scan unlisted pipeline or fixture files for replacement data.
Ofgem: Energy price cap unit rates and standing charges
Driver and Vehicle Standards Agency: DVSA anonymised MOT testing data results
Each admitted source version retains a public URL, retrieval time, content hash, version and licence conclusion.
Ofgem: Energy price cap unit rates and standing charges
Driver and Vehicle Standards Agency: DVSA anonymised MOT testing data results
A derived value identifies the registered transformation method that produced it from its admitted inputs.
Every null leaf has an explicit reason, and unavailable or suppressed information is not replaced with zero.
Driver and Vehicle Standards Agency: DVSA anonymised MOT testing data results
How a published UK EV value is traced through the E2 manifest, source snapshot, licence, transformation method, quality status and null reason.
One build identifier and generation time bind every E2 artefact in a snapshot. The manifest lists each permitted path with its byte count, SHA-256, record count and stable artefact ID. Records from different builds are not spliced together.
The source-version record states which public source was retrieved, when it was retrieved, the source or snapshot version, its content SHA-256 and the applicable licence decision. Attribution follows the admitted source record; an audit-only or metadata-only source cannot contribute product values.
Provenance maps the data subtree to source identifiers, public locators and a registered transformation method. The method register retains a version and code hash, allowing a derived output to be tied to the implementation that created it rather than to an undocumented spreadsheet step.
A null reason distinguishes not available, not observed yet, not applicable, small-sample suppression, licence withholding and source unavailability. Quality and freshness travel with the artefact. Empty-state means no safely publishable records, not a confirmed count of zero.
Use provenance to audit a value's origin and transformation, not to infer vehicle condition beyond the published metric.
Immediate action: Follow the artefact's source version and method identifier before reusing a value.
One build identifier and generation time bind every E2 artefact in a snapshot. The manifest lists each permitted path with its byte count, SHA-256, record count and stable artefact ID. Records from different builds are not spliced together.
The source-version record states which public source was retrieved, when it was retrieved, the source or snapshot version, its content SHA-256 and the applicable licence decision. Attribution follows the admitted source record; an audit-only or metadata-only source cannot contribute product values.
Provenance maps the data subtree to source identifiers, public locators and a registered transformation method. The method register retains a version and code hash, allowing a derived output to be tied to the implementation that created it rather than to an undocumented spreadsheet step.