Sovereign Climate Data

• Sovereign Climate Data — Overview
• Technical Quality
• P01 — Verifiability by Design
• P02 — FAIR Data Standards
• P03 — Full Provenance Traceability
• P04 — Methodological Sovereignty
• P05 — Temporal Persistence and Baseline Integrity
• Digital Sovereignty
• P06 — AI-Legibility
• P07 — Third-Party Anchoring
• Governance and Social Legitimacy
• P08 — Community and Indigenous Data Consent
• P09 — Regulatory Stack Alignment
• P10 — Resilience, Security and Data Governance
• API Reference

Sovereign Climate Data — Overview

What is Sovereign Climate Data?

Sovereign climate data is environmental and impact data that an organisation owns, controls, and can defend independently — regardless of which platforms, vendors, or partnerships it uses. In 2026, with the EU Green Claims Directive, CBAM, ISSB S2 mandates across LATAM, and Article 6 carbon market rules all entering force simultaneously, sovereign climate data has shifted from a competitive advantage to a baseline legal requirement.

This framework defines ten principles across three layers:

• Technical Quality (P1–P5): The data is correct, traceable, and yours to keep.
• Digital Sovereignty (P6–P7): The data is discoverable, citable, and AI-legible.
• Governance and Social Legitimacy (P8–P10): The data is ethically grounded, regulation-ready, and institutionally resilient.

Principles at a Glance

ID	Principle	Layer	Primary Standard
SCD-P01	Verifiability by Design If it cannot be checked, it does not count.	technical	EU Directive 2024/825 (Green Claims / EmpCo) — Art. 5, 6
SCD-P02	FAIR Data Standards Findable. Accessible. Interoperable. Reusable.	technical	FAIR Data Principles — Wilkinson et al., Scientific Data (2016)
SCD-P03	Full Provenance Traceability Without provenance, a number is a narrative.	technical	Verra VM0042 Methodology (2026 update) — Section 5 (MRV requirements)
SCD-P04	Methodological Sovereignty You own your data only if you own your method.	technical	IPCC AR6 — Annex II (Methodologies for GHG inventories)
SCD-P05	Temporal Persistence and Baseline Integrity A result without a baseline is a claim without evidence.	technical	ISSB IFRS S2 — Para. 22–28 (Transition provisions and comparatives)
SCD-P06	AI-Legibility If an AI agent cannot cite you, you do not exist.	digital	EU CSRD — Art. 8 (machine-readable XBRL tagging requirement)
SCD-P07	Third-Party Anchoring Your claim is only as strong as its external anchor.	digital	CBAM Regulation EU 2023/956 — Art. 10(3) (Accredited VVB requirement)
SCD-P08	Community and Indigenous Data Consent CARE complements FAIR. People before data.	governance	ILO Convention 169 — Indigenous and Tribal Peoples (ratified by Colombia, Peru, Bolivia, Mexico)
SCD-P09	Regulatory Stack Alignment Build once, report everywhere.	governance	EU Directive 2024/825 (EmpCo/Green Claims) — enforcement September 27, 2026
SCD-P10	Resilience, Security and Data Governance Sovereign data that can be lost is not sovereign.	governance	Climate Data Steering Committee — Common Carbon Credit Data Model (2024)

Technical Quality

• SCD-P01 — Verifiability by Design: If it cannot be checked, it does not count.
• SCD-P02 — FAIR Data Standards: Findable. Accessible. Interoperable. Reusable.
• SCD-P03 — Full Provenance Traceability: Without provenance, a number is a narrative.
• SCD-P04 — Methodological Sovereignty: You own your data only if you own your method.
• SCD-P05 — Temporal Persistence and Baseline Integrity: A result without a baseline is a claim without evidence.

Digital Sovereignty

• SCD-P06 — AI-Legibility: If an AI agent cannot cite you, you do not exist.
• SCD-P07 — Third-Party Anchoring: Your claim is only as strong as its external anchor.

Governance and Social Legitimacy

• SCD-P08 — Community and Indigenous Data Consent: CARE complements FAIR. People before data.
• SCD-P09 — Regulatory Stack Alignment: Build once, report everywhere.
• SCD-P10 — Resilience, Security and Data Governance: Sovereign data that can be lost is not sovereign.

API Access

This wiki is accessible via the BookStack REST API. All pages are public and require no authentication to read.

A static machine-readable version is also available at:
https://wiki.cleantechhub.net/data/principles.json
https://wiki.cleantechhub.net/data/principles_jsonld.json

How to Cite This Framework

CleantechHUB (2026). Sovereign Climate Data Principles, v1.0.0. CleantechHUB Climate Intelligence Wiki. Available at: https://wiki.cleantechhub.net/books/sovereign-climate-data. Licence: CC-BY 4.0.

Technical Quality

P01 — Verifiability by Design

Definition

Rationale

Implementation Steps

1. Map every reported metric to its primary data source (satellite, government dataset, sensor).
2. Ensure the source is publicly accessible without authentication.
3. Document the verification pathway: source → method → aggregation → reported figure.
4. Test: ask an independent analyst to verify your top 5 climate claims using only public data.
5. Resolve any metric that cannot be independently verified before publication.

Compliance Checklist

	Criterion	What it means
☐	Metric-to-source mapping exists	Every reported figure has a documented primary source.
☐	Sources are publicly accessible	No login or permission required to access primary sources.
☐	Verification pathway documented	Steps to reproduce any metric from scratch are written down.
☐	AI scan performed	Climate TRACE / GFW / EDGAR check confirms the org is findable.

Regulatory References

• EU Directive 2024/825 (Green Claims / EmpCo) — Art. 5, 6
• IPCC AR6 Working Group III — Chapter 2 (Emissions Methodologies)
• ISSB IFRS S2 — Para. 63 (Disclosure verification)

Recommended Tools and Platforms

Climate TRACE Global Forest Watch EDGAR (EU JRC) Copernicus / ESA

Keywords

verifiability greenwashing EU Green Claims Directive AI audit ESG verification

P02 — FAIR Data Standards

Definition

Rationale

Implementation Steps

1. Assign a persistent identifier (DOI or stable public URL) to every dataset.
2. Publish data in at least one open format: JSON, CSV, GeoJSON, or NetCDF.
3. Add schema.org or DataCatalog markup to all public data pages.
4. Declare a Creative Commons or equivalent open licence on every dataset.
5. Register datasets with a public catalogue (CKAN, DataCite, or national open data portal).

Compliance Checklist

	Criterion	What it means
☐	Persistent identifiers assigned	Every dataset has a DOI or stable URL that will not change.
☐	Open format export available	Data downloadable as JSON, CSV, or GeoJSON without login.
☐	schema.org markup present	Dataset metadata is readable by Google Dataset Search and AI agents.
☐	Licence declared	Explicit open licence (CC-BY 4.0 recommended) on every dataset.

Regulatory References

• FAIR Data Principles — Wilkinson et al., Scientific Data (2016)
• EU CSRD — Art. 8 Digital Tagging & Machine-Readable Reporting
• ISSB IFRS S2 — Appendix A (Definitions, data quality)

Recommended Tools and Platforms

schema.org DataCite CKAN Zenodo OpenAire

Keywords

FAIR principles open data interoperability schema.org machine-readable data catalogue

P03 — Full Provenance Traceability

Definition

Rationale

Implementation Steps

1. For each reported metric, create a provenance record with: source instrument, timestamp, analyst, methodology version, and transformations applied.
2. Store provenance records in a format that is exportable and machine-readable (JSON-LD recommended).
3. Link provenance records to the reported metric via persistent identifier.
4. Implement versioning: when methodology changes, create a new version record — never overwrite.
5. For satellite-derived data: record scene ID, sensor, orbit number, cloud cover, and NDVI delta.

Compliance Checklist

	Criterion	What it means
☐	Instrument/source documented	Every metric traces to a named instrument or dataset version.
☐	Timestamps recorded in UTC	All events use ISO 8601 UTC timestamps.
☐	Analyst/author attributed	Name and organisation of every analyst is recorded.
☐	Methodology version pinned	Specific version of methodology used is recorded, not just the name.

Regulatory References

• Verra VM0042 Methodology (2026 update) — Section 5 (MRV requirements)
• CBAM Regulation EU 2023/956 — Art. 10 (Embedded emissions calculation)
• dMRV Working Group — Planet2050 × BioCarbon (2025)

Recommended Tools and Platforms

ESA Sentinel-2 scene IDs NASA Landsat overpass metadata IDEAM Colombia GFW GLAD Lab

Keywords

provenance chain of custody MRV dMRV carbon verification Verra CBAM

P04 — Methodological Sovereignty

Definition

Rationale

Implementation Steps

1. Write your own methodology document — not a reference to a vendor's documentation.
2. Anchor every calculation to a specific section of a public standard (e.g. IPCC AR6 WG3 §2.3).
3. Have the methodology reviewed by an independent expert at least once per year.
4. When vendors update their models, log the change and restate historical figures if material.
5. Store the methodology document in your own systems, not exclusively on a vendor platform.

Compliance Checklist

	Criterion	What it means
☐	Own methodology document exists	A document you wrote describes how each metric is calculated.
☐	Anchored to public standard	Each calculation references a specific section of IPCC AR6 / GRI / ISSB.
☐	Independently reproducible	A qualified analyst could reproduce your results using only your document.
☐	Vendor-change log maintained	Changes to vendor models that affect your figures are documented.

Regulatory References

• IPCC AR6 — Annex II (Methodologies for GHG inventories)
• GRI 305 (Emissions) — 2016, mandatory methodology disclosure
• World Bank — Sovereign Climate and Nature Reporting Framework (2022)

Recommended Tools and Platforms

GHG Protocol Corporate Standard IPCC Emission Factor Database (EFDB) GRI 305 reporting tool

Keywords

methodology sovereignty vendor lock-in GRI 305 IPCC AR6 carbon accounting reproducibility

P05 — Temporal Persistence and Baseline Integrity

Definition

Rationale

Implementation Steps

1. Define and document your baseline before any intervention — not retroactively.
2. Store at least 3 years of historical data in systems you own and control.
3. When changing providers, negotiate full historical data export as a contractual condition.
4. Apply ISSB S2's transition provisions: restate comparatives when methodology changes.
5. Conduct an annual baseline review to confirm it remains defensible against current standards.

Compliance Checklist

	Criterion	What it means
☐	Baseline documented pre-intervention	Baseline was set before the activity it measures, with date stamp.
☐	3+ years of history owned	Historical data is in your own systems, not exclusively with a vendor.
☐	Methodology consistent or reconciled	Any methodology changes are logged with impact on historical figures.
☐	Annual baseline review conducted	Baseline reviewed annually against current IPCC / GRI standards.

Regulatory References

• ISSB IFRS S2 — Para. 22–28 (Transition provisions and comparatives)
• CEPAL — Sustainable Bonds LAC: Decade of Growth 2014–2024
• GRI 305-1 (Scope 1 GHG) — Section 3.3 (Base year recalculation policy)

Recommended Tools and Platforms

EDGAR time series GFW Hansen dataset v1.11+ IDEAM national GHG inventory series

Keywords

baseline temporal consistency historical data GHG inventory bond verification ISSB S2

Digital Sovereignty

P06 — AI-Legibility

Definition

Rationale

Implementation Steps

1. Add schema.org/Dataset JSON-LD to every public data page (see JSON-LD reference below).
2. Submit datasets to Google Dataset Search via schema.org markup.
3. Register with at least one global open data index (CKAN, DataCite, GFW API).
4. Maintain a public llms.txt file (analogous to robots.txt) guiding AI agents to authoritative sources.
5. Run quarterly AI scans: query Climate TRACE, GFW, and EDGAR to confirm your data is indexed.

JSON-LD Reference Example

{
  "@context": "https://schema.org",
  "@type": "Dataset",
  "name": "Colombia Deforestation Alerts 2024",
  "description": "GLAD-L primary forest loss alerts for Colombia, 2024.",
  "url": "https://data.cleantechhub.net/datasets/colombia-deforestation-2024",
  "identifier": "https://doi.org/10.XXXX/cth-col-def-2024",
  "creator": { "@type": "Organization", "name": "CleantechHUB" },
  "datePublished": "2025-01-15",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "spatialCoverage": { "@type": "Place", "name": "Colombia" },
  "temporalCoverage": "2024-01-01/2024-12-31",
  "keywords": ["deforestation", "Colombia", "GLAD-L", "primary forest", "sovereign data"],
  "distribution": [{
    "@type": "DataDownload",
    "encodingFormat": "application/json",
    "contentUrl": "https://data.cleantechhub.net/api/v1/datasets/colombia-deforestation-2024"
  }]
}

Compliance Checklist

	Criterion	What it means
☐	schema.org/Dataset markup live	JSON-LD is present on all public data pages and passes Google Rich Results test.
☐	Listed in open index	Dataset appears in at least one: GFW API, Climate TRACE, EDGAR, DataCite.
☐	llms.txt published	A public llms.txt file at cleantechhub.net/llms.txt guides AI agents.
☐	Quarterly AI scan	Last scan date recorded; data confirmed indexed in at least one major platform.

Regulatory References

• EU CSRD — Art. 8 (machine-readable XBRL tagging requirement)
• TCFD Recommendations — Pillar 4 (Metrics and Targets, digital disclosure)
• IICSR AI+ESG Market Report 2025

Recommended Tools and Platforms

Google Rich Results Test schema.org validator llms.txt specification DataCite

Keywords

AI legibility schema.org JSON-LD ESG AI llms.txt due diligence NLP

P07 — Third-Party Anchoring

Definition

Rationale

Implementation Steps

1. Identify the authoritative external source for each reported metric type (forest: GFW/IDEAM; emissions: Climate TRACE/EDGAR; energy: IEA/national grid operator).
2. Cross-reference your data against the external anchor at least quarterly.
3. Document discrepancies between your data and the anchor, with explanation.
4. For carbon credits: work only with verifiers accredited under Verra, Gold Standard, or a national carbon market standard.
5. For CBAM compliance: obtain third-party verification from an EU-accredited VVB.

Compliance Checklist

	Criterion	What it means
☐	External anchor identified per metric	Each metric type has a named authoritative external source.
☐	Quarterly cross-reference performed	Last reconciliation date recorded with discrepancy log.
☐	Verifier accreditation confirmed	Any third-party verifier's accreditation status has been checked.
☐	CBAM VVB in place (if applicable)	EU-accredited VVB identified for CBAM-relevant goods.

Regulatory References

• CBAM Regulation EU 2023/956 — Art. 10(3) (Accredited VVB requirement)
• Verra VCS Standard v4.1 — Section 4.2 (Validation and Verification)
• GFW GLAD-L Alert Methodology (Hansen et al. 2013, updated 2024)

Recommended Tools and Platforms

Global Forest Watch API Climate TRACE API EDGAR REST API Copernicus CDS API IDEAM Colombia INPE PRODES

Keywords

third-party verification IDEAM GFW EDGAR CBAM VVB carbon credits Verra

Governance and Social Legitimacy

P08 — Community and Indigenous Data Consent

Definition

Rationale

Implementation Steps

1. Map all data collection activities against community land rights before beginning.
2. Obtain documented FPIC from affected communities before any data collection on their land.
3. Establish a data governance agreement that specifies community rights to access, correct, and withdraw consent for their data.
4. Ensure community members can access and challenge data about their territories.
5. Report on CARE compliance in the same place as FAIR compliance.

Compliance Checklist

	Criterion	What it means
☐	Community land map completed	Data activities mapped against indigenous and community land rights.
☐	FPIC documented	Free, Prior, and Informed Consent obtained and documented before data collection.
☐	Data governance agreement signed	Agreement specifies community rights and responsibilities of the collector.
☐	Community access enabled	Communities can view, challenge, and request correction of data about their land.

Regulatory References

• ILO Convention 169 — Indigenous and Tribal Peoples (ratified by Colombia, Peru, Bolivia, Mexico)
• TNFD Framework v1.0 (2023) — Core Disclosure B (Stakeholder engagement)
• Global Indigenous Data Alliance — CARE Principles for Indigenous Data Governance (2019)
• CBD Kunming-Montreal Framework (COP15, 2022) — Target 22 (Indigenous rights)

Recommended Tools and Platforms

RAISG Indigenous Territories Map FAO FPIC Guidelines CARE Data Maturity Model

Keywords

CARE principles indigenous data sovereignty FPIC community consent TNFD ILO 169 LATAM

P09 — Regulatory Stack Alignment

Definition

Rationale

Implementation Steps

1. Audit your regulatory exposure: which of the 2026 stack applies to your organisation?
2. Map each regulatory requirement to specific data fields (see Regulatory Mapping Table below).
3. Design data collection to capture all required fields from the start — not retrofit.
4. Use ISSB S2 as the baseline (it has the broadest adoption) and layer CBAM and GCD requirements on top.
5. Review the stack annually: add new requirements as they come into force.

Regulatory Mapping Table — 2026 Stack

Regulation	Jurisdiction	In Force	Key Data Requirement	Penalty
EU Green Claims Directive 2024/825	EU (affects global exporters)	Sept 2026	Substantiation of all environmental claims with verifiable evidence	Up to 4% annual turnover
CBAM (EU 2023/956)	EU imports — global exporters	Jan 2026 (full)	Embedded GHG per tonne for 6 product categories	Default tariff + penalties
ISSB IFRS S2	Brazil (CVM), Mexico (CNBV), Chile (CMF)	FY2025 data, reported 2026	Climate risks, Scope 1/2/3 emissions, scenario analysis	Securities regulator sanctions
EU CSRD	EU + large non-EU subsidiaries	2029 (third-country)	Full ESG disclosure per ESRS standards with XBRL tagging	EU market access risk
Paris Agreement Art. 6	LATAM sovereign govts	COP29 rules, 2025	Sovereign-grade MRV for internationally transferred mitigation outcomes (ITMOs)	Exclusion from international carbon markets

Compliance Checklist

	Criterion	What it means
☐	Regulatory exposure audit completed	Applicable regulations from the 2026 stack identified.
☐	Regulatory-to-data field mapping	Each regulation's key data requirements mapped to existing or planned fields.
☐	ISSB S2 baseline in place	Data architecture covers all ISSB S2 mandatory disclosures.
☐	CBAM readiness assessed	Embedded carbon calculation capability assessed for all relevant export products.

Regulatory References

• EU Directive 2024/825 (EmpCo/Green Claims) — enforcement September 27, 2026
• CBAM Regulation EU 2023/956 — definitive regime January 1, 2026
• ISSB IFRS S2 — S&P Global LATAM Adoption Map, June 2025
• Paris Agreement Article 6 — COP29 Rulebook (Belém, November 2025)

Recommended Tools and Platforms

ISSB IFRS S2 disclosure checklist CBAM Registry EU CSRD ESRS standards LATAM NDC tracker (CEPAL)

Keywords

CBAM ISSB S2 EU Green Claims CSRD Article 6 COP29 regulatory compliance LATAM 2026

P10 — Resilience, Security and Data Governance

Definition

Rationale

Implementation Steps

1. Write a Data Governance Policy covering: access control (who can do what), dispute resolution, retention schedule, backup frequency, and sharing rules.
2. Implement role-based access: at minimum, separate read and write permissions.
3. Run automated backups to a system you control at least weekly; test recovery quarterly.
4. Maintain an access log: every read and write to sensitive climate data is recorded.
5. For shared data: use a Data Sharing Agreement (DSA) that specifies permitted uses, attribution requirements, and data return/destruction obligations.

Compliance Checklist

	Criterion	What it means
☐	Data Governance Policy written	Document covers access control, disputes, retention, backup, and sharing.
☐	Role-based access implemented	At minimum: separate read vs. write access for climate data systems.
☐	Automated backups running	Weekly backup to a system you own, with quarterly recovery tests.
☐	Access log active	All reads and writes to sensitive climate data are recorded with timestamp.

Regulatory References

• Climate Data Steering Committee — Common Carbon Credit Data Model (2024)
• dMRV Working Group Phase 2 Roadmap (Planet2050 × BioCarbon, 2025)
• GDPR Art. 5 (Data integrity and confidentiality) — applicable to EU-adjacent organisations
• ISO/IEC 27001 (Information Security Management) — international baseline

Recommended Tools and Platforms

Infisical (secrets management) Backblaze B2 / Rclone (backup) Keycloak (access control) Audit log frameworks

Keywords

data governance security resilience backup access control data sharing agreement ISO 27001

API Reference

API Reference — Sovereign Climate Data Wiki

All pages in this book are publicly accessible via the BookStack REST API. No authentication is required for read access.

Base URL

https://wiki.cleantechhub.net/api

Common Queries

Purpose	Endpoint
List all principles pages	GET /api/pages?filter[book_slug]=sovereign-climate-data
Get a principle by slug	GET /api/pages?filter[slug]=verifiability-by-design
Get full page content	GET /api/pages/{id}
Search all principles	GET /api/search?query=CBAM+embedded+carbon
List chapters	GET /api/chapters?filter[book_id]=860
Get book metadata	GET /api/books/860

Static Machine-Readable Files

Format	URL	Use case
Flat JSON	https://wiki.cleantechhub.net/data/principles.json	General API consumers, dashboards
JSON-LD (schema.org)	https://wiki.cleantechhub.net/data/principles_jsonld.json	AI agents, Google Dataset Search, semantic web

Example: Fetch Principle P01 as JSON

curl -s "https://wiki.cleantechhub.net/api/pages?filter[slug]=verifiability-by-design" \
  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['data'][0]['name'])"

Example: Search for CBAM-related principles

curl -s "https://wiki.cleantechhub.net/api/search?query=CBAM" \
  | python3 -m json.tool | grep -A3 '"name"'

Example: Pull principles.json for RAG ingestion

import requests
data = requests.get("https://wiki.cleantechhub.net/data/principles.json").json()
for p in data["principles"]:
    print(p["id"], p["title"])

Rate Limits

BookStack imposes no rate limit on read-only API calls. Be courteous: add a 100ms delay between calls in scripts.

Licence

All content in this wiki is published under CC-BY 4.0. Cite as: CleantechHUB (2026). Sovereign Climate Data Principles, v1.0.0.