Tier 2-4 // LITHIUM RECORD

The Lithium Record Vault

Vault landing page explaining record contents, OEM-facing verification URLs, sample records, verifier handoff, and hash-chain logic.

Evidence architecture

Structured for producers, verifiers, OEMs, and machines

01

What a vault entry contains

A vault entry contains producer identity, mine or brine source, product type, extraction method, processing route, carbon footprint, water context, verifier status, and a SHA-256 evidence hash.

02

What OEM customers see

An OEM customer sees a clean verification page with the record summary, material details, verification status, supporting document references, and schema markup for machine readability.

03

Worker boundary

This static page explains the vault. Live /vault/lr_* records are intended to be rendered by the later Cloudflare Worker layer.

Audit register

Core fields in the record layer

Every page in this static layer points back to the same operating premise: lithium compliance evidence needs a stable, readable, citation-friendly URL rather than a disposable file export.

Record fieldWhy it matters
kgCO₂/kg LCETranslates site evidence into OEM carbon-footprint workflows.
GPS and extraction routeHardens provenance and supports due-diligence review.
Verifier signatureShows independent assurance status and review trail.
SHA-256 hashConnects documents, metadata, and permanent record identity.
Source register

Primary regulatory references

Lithium Record content is written as technical infrastructure guidance, not legal advice. Formal compliance decisions should be reviewed with qualified counsel and accredited verifiers.

ReferenceRelevance
Regulation (EU) 2023/1542EU batteries and waste batteries regulation establishing sustainability, performance, safety, information, and lifecycle obligations.
Battery Passport Content GuidancePractical guidance on Article 77 battery passport scope, responsible operators, and February 18, 2027 readiness.