Lithium compliance evidence // SPOKE RECORD

Lithium CSDDD Value Chain Files

Organize lithium value-chain evidence for CSDDD-related human-rights and environmental due-diligence 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.

CSDDD evidence is broader than a single battery file. For lithium, it can include human-rights, environmental, supplier, and remediation records across the value chain. 1

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

Value-chain evidence

Directive (EU) 2024/1760 establishes corporate sustainability due-diligence duties for certain companies and value chains. Lithium Record can store documents that a customer associates with those duties: supplier policies, risk assessments, grievance information, mitigation plans, contractual controls, review summaries, or environmental evidence. The page should make clear that the customer uploaded the file and that the platform is not operating the due-diligence program.

Connection to batteries

Battery teams may need CSDDD-adjacent lithium evidence when procurement, legal, ESG, and product compliance functions converge. A value-chain file can link to origin records, custody documents, OECD evidence, and Battery Regulation pages. That cross-linking helps the team avoid duplicate records and gives reviewers a route through the evidence map.

Limits and attribution

The page should attribute policies and assessments to the issuer. Lithium Record should not say a company has satisfied CSDDD. It can say the vault preserves customer-uploaded documents that may support internal CSDDD due-diligence workflows.

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 CSDDD value chain files within the Lithium compliance evidence evidence context.

Last reviewed
2026-05-11
Source count
1
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

Does Lithium Record provide legal CSDDD compliance?

No. It stores evidence that may support a company’s due-diligence workflow.

Why include CSDDD in a lithium site?

Lithium supply chains can involve human-rights and environmental due-diligence questions that overlap with battery and raw-material regulation.

Should CSDDD files link to origin pages?

Yes. Value-chain risk review often needs origin and custody context.

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 CSDDD value chain files. 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]Directive (EU) 2024/1760 on corporate sustainability due diligenceeur-lex.europa.eu