Lithium compliance evidence // SPOKE RECORD

Lithium Origin Records

Preserve lithium origin statements, issuer details, material boundaries, and hash evidence for provenance review.

Permanent record copy

Evidence page

This page is part of the Lithium Record pillar-and-spoke content layer for provenance, carbon-footprint, due-diligence, and Battery Passport evidence.

An origin record should answer a narrow question: what origin evidence was uploaded, who issued it, what lithium material it covers, and how the verifier can inspect the file. 1 2

This spoke belongs to the Lithium Provenance Due Diligence pillar at /lithium-provenance-due-diligence/.

Origin is a bounded claim

Lithium origin can refer to country, site, project, processor, batch, shipment, or recycled source. A record page should not blur those categories. If a customer uploads a country-of-origin statement, the page should not rewrite it as mine-level proof. If a file covers a period average, the page should not imply shipment-level traceability. Boundary discipline is the difference between evidence and marketing.

Minimum record fields

A practical origin record should include issuer name, document date, material form, declared origin, covered period or batch, customer upload date, hash, permanent URL, and limitation note. The limitation note should say that Lithium Record stores the document and hash but does not independently verify the origin claim.

Linking out of the origin page

The origin page should link back to the provenance pillar and sideways to chain-of-custody, OECD due-diligence, and critical-raw-material resilience pages. That lets a reviewer move from the basic origin statement into stronger supply-chain context.

Compliance boundary

Stored evidence, not formal approval

Lithium Record should be described as a vault, record, hashing, hosting, indexing, and verifier-handoff layer. It should not be described as a certifier, auditor, regulator, notified body, conformity-assessment body, legal adviser, or automated compliance decision-maker. The page copy should keep the distinction between stored evidence and formal compliance determination explicit.

Source freshness register // evidence record

Last-reviewed evidence boundary for this record

Static source register reviewed for lithium origin records within the Lithium compliance evidence evidence context.

Last reviewed
2026-05-11
Source count
2
Review type
Static route and source-register inspection
StepSource categoryFreshness boundary
1Origin and custody referencesRecord source category reviewed for static availability and conservative boundary language.
2OECD due-diligence evidence cuesRecord source category reviewed for static availability and conservative boundary language.
3CSDDD value-chain recordsRecord source category reviewed for static availability and conservative boundary language.
4Critical-raw-material resilience notesRecord source category reviewed for static availability and conservative boundary language.

Evidence boundary

Reviewed for availability, not approval

This record-level freshness note confirms that the static route, source register, internal links, and compliance-boundary copy were reviewed for availability and conservative language. It does not certify compliance, approve the underlying documents, provide legal advice, or replace accredited verification.

Verifier next action: Inspect the source register on this page, compare related lane records, and route any formal determination to the responsible operator, qualified counsel, customer, or accredited review process.

Verifier questions

FAQ

What is the difference between origin and custody?

Origin names where the material is said to come from. Custody shows how it moved and who controlled it.

Can the vault confirm a mine site?

No. It can preserve a file that makes a mine-site statement, but the issuer remains responsible for that claim.

Should origin records include recycled lithium?

Yes, if the uploaded file states recycled origin or recycled-content context and the boundary is clear.

Evidence record FAQ // verifier Q&A

Common review questions for this record

These static answers explain how to interpret this individual evidence record, where it connects to the lane graph, and which compliance boundary remains outside Lithium Record.

Record FAQ

How should a verifier use this Lithium Record page?

Use this page as a static spoke evidence-record entry for lithium origin records. It organizes route metadata, source references, internal context, and verifier handoff links so the reviewer can decide which source files, vault records, or adjacent evidence pages to inspect next.

Record FAQ

What does this record not prove on its own?

On its own, this page does not certify EU Battery Regulation compliance, validate carbon-footprint calculations, approve provenance claims, or replace accredited verification. Lithium Record provides a vault, record, hashing, hosting, indexing, and verifier-handoff layer for review support.

Record FAQ

How does this record connect to the evidence lane?

This record belongs to the Provenance evidence lane at /records/provenance/. The lane page groups the pillar and spoke records so reviewers can move between regulation, carbon-footprint, provenance, and Battery Passport context without relying on a dynamic checkout or private dashboard route.

Record FAQ

What is the next handoff after reading this record?

A reviewer can follow the source register, open related records, use the verifier handoff route, or request manual onboarding. The static page preserves discovery and orientation; any formal determination remains with the appropriate verifier, customer, or accredited review process.

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.

RefReferenceSource domain
[1]Regulation (EU) 2023/1542eur-lex.europa.eu
[2]European Critical Raw Materials Actcommission.europa.eu