@digital4better/data 1.3.66 → 1.3.68

package/data/mix/world-monthly-green.csv

@@ -92,3 +92,4 @@ period,Bioenergy,Hydro,Solar,Wind
 2026-07,0.0509,0.4976,0.2661,0.1853
 2026-08,0.0509,0.4976,0.2661,0.1853
 2026-09,0.0509,0.4976,0.2661,0.1853
+2026-10,0.0509,0.4976,0.2661,0.1853

package/data/mix/world-monthly-green.json

@@ -556,5 +556,11 @@
     "Hydro": 0.4976,
     "Solar": 0.2661,
     "Wind": 0.1853
+  },
+  "2026-10": {
+    "Bioenergy": 0.0509,
+    "Hydro": 0.4976,
+    "Solar": 0.2661,
+    "Wind": 0.1853
   }
 }

package/data/mix/world-monthly.csv

@@ -92,3 +92,4 @@ period,Bioenergy,Coal,Gas,Hydro,Nuclear,Other Fossil,Other Renewables,Solar,Wind
 2026-07,0.015,0.2444,0.3108,0.1469,0.0516,0.0911,0.0069,0.0786,0.0547
 2026-08,0.015,0.2444,0.3108,0.1469,0.0516,0.0911,0.0069,0.0786,0.0547
 2026-09,0.015,0.2444,0.3108,0.1469,0.0516,0.0911,0.0069,0.0786,0.0547
+2026-10,0.015,0.2444,0.3108,0.1469,0.0516,0.0911,0.0069,0.0786,0.0547

package/data/mix/world-monthly.json

@@ -1021,5 +1021,16 @@
     "Other Renewables": 0.0069,
     "Solar": 0.0786,
     "Wind": 0.0547
+  },
+  "2026-10": {
+    "Bioenergy": 0.015,
+    "Coal": 0.2444,
+    "Gas": 0.3108,
+    "Hydro": 0.1469,
+    "Nuclear": 0.0516,
+    "Other Fossil": 0.0911,
+    "Other Renewables": 0.0069,
+    "Solar": 0.0786,
+    "Wind": 0.0547
   }
 }

package/data/mix/world-yearly-green.csv

@@ -6,4 +6,4 @@ year,Bioenergy,Hydro,Solar,Wind
 2023,0.0663,0.5886,0.1486,0.1965
 2024,0.0634,0.5638,0.1747,0.1981
 2025,0.0598,0.5298,0.2095,0.2009
-2026,0.0547,0.5038,0.2423,0.1992
+2026,0.0544,0.5031,0.2448,0.1977

package/data/mix/world-yearly-green.json

@@ -42,9 +42,9 @@
     "Wind": 0.2009
   },
   "2026": {
-    "Bioenergy": 0.0547,
-    "Hydro": 0.5038,
-    "Solar": 0.2423,
-    "Wind": 0.1992
+    "Bioenergy": 0.0544,
+    "Hydro": 0.5031,
+    "Solar": 0.2448,
+    "Wind": 0.1977
   }
 }

package/data/mix/world-yearly.csv

@@ -6,4 +6,4 @@ year,Bioenergy,Coal,Gas,Hydro,Nuclear,Other Fossil,Other Renewables,Solar,Wind
 2023,0.0164,0.2689,0.3264,0.1457,0.0534,0.0966,0.0072,0.0368,0.0486
 2024,0.0164,0.2646,0.3215,0.1462,0.053,0.0945,0.007,0.0453,0.0514
 2025,0.0163,0.2599,0.3153,0.1442,0.053,0.0928,0.0069,0.057,0.0547
-2026,0.0157,0.2501,0.3119,0.1447,0.0518,0.092,0.007,0.0696,0.0572
+2026,0.0157,0.2496,0.3118,0.1449,0.0518,0.0919,0.0069,0.0705,0.0569

package/data/mix/world-yearly.json

@@ -78,13 +78,13 @@
   },
   "2026": {
     "Bioenergy": 0.0157,
-    "Coal": 0.2501,
-    "Gas": 0.3119,
-    "Hydro": 0.1447,
+    "Coal": 0.2496,
+    "Gas": 0.3118,
+    "Hydro": 0.1449,
     "Nuclear": 0.0518,
-    "Other Fossil": 0.092,
-    "Other Renewables": 0.007,
-    "Solar": 0.0696,
-    "Wind": 0.0572
+    "Other Fossil": 0.0919,
+    "Other Renewables": 0.0069,
+    "Solar": 0.0705,
+    "Wind": 0.0569
   }
 }

package/llms-full.txt

@@ -0,0 +1,239 @@
+# Digital4Better Open Data — complete npm package reference
+
+> Offline usage documentation for the reference datasets shipped in `@digital4better/data`. Data are plain JSON and CSV files. They support environmental modeling; many values are references or estimates rather than direct measurements.
+
+## Scope and version
+
+This reference describes the collections in this package. Read [package.json](./package.json) for the installed version and [README.md](./README.md) for source families and provider assumptions. The [website](https://digital4better.github.io/data/) and its [catalog](https://digital4better.github.io/data/catalog.json) can change independently of an installed package. Verify online examples and file inventories against the local files. Reading these local datasets requires no account or network connection.
+
+There is no exported query function or runtime service. Open the desired file under `data/`. JSON preserves nested objects, arrays and source keys. CSV is a tabular projection: some nested fields are omitted and lists can use `|` separators. Use JSON for complete structured records. Do not infer a field is absent from JSON merely because CSV omits it.
+
+## Finding the right data
+
+1. Identify the collection matching the question. Electricity impact factors are in `factor`; electricity technology shares are in `mix`; cloud regions are in `cloud`; geographic identifiers are in `country`.
+2. Inspect the collection's file inventory. Opening one file does not establish the coverage of the whole package.
+3. For temporal data, select geography, yearly or monthly granularity, and actual-mix or renewable-only scenario explicitly.
+4. Check that the exact source key, requested period and requested indicator are present and usable. File-level availability is not record-level availability. Inspect each file rather than assuming all variants have identical coverage.
+5. If the requested record is unavailable, report the file and keys checked. A result can be absent even when the collection exists. Do not silently turn an absent value into zero or use another territory, period or scenario.
+6. If the consuming application authorizes a fallback, record the requested and selected geography/period, source file, indicator and reason. A search may proceed from subdivision to country, continent and world, but broader averages are substitutions, not equivalent observations. There is no universally correct fallback order across time and geography.
+
+Use the exact identifiers in each source file. Cloud files can use lowercase country codes and aliases; electricity country keys use source country identifiers. Do not apply one collection's identifier normalization blindly to another. Geographic mappings are provided in `data/country/`; confirm membership from the actual records.
+
+## Missing values, zero and time
+
+- A missing property, `null` or an empty CSV cell denotes unavailable data. Preserve that distinction in calculations and exports.
+- An explicit numeric zero must be preserved. Some provider or hardware zeros are dataset conventions, not independently verified zero environmental impacts; review the relevant assumptions.
+- Do not use truthiness checks such as `if (!value)` to detect absence: that also rejects numeric zero. Check null/undefined and the value's type explicitly.
+- Years are string keys such as `2025`; months are string keys such as `2025-01`. Do not silently mix annual and monthly series.
+- The current year can be partial. Available periods may contain estimated or carried-forward values; they do not guarantee new observations. The current series do not individually flag all filled values.
+- File modification dates, package release dates and source observation dates have different meanings. A daily rebuild does not mean every source was refreshed.
+- For reproducibility, retain the exact package version or file snapshot, source keys, period, indicator, unit and any fallback. Public download URLs can change.
+
+## Units and environmental impact indicators
+
+Impact values combine an indicator-specific unit with a functional unit. For example, a `gwp` value in a transport record whose `unit` is `pkm` is expressed in `kg CO2 eq/pkm`. The `unit` field is therefore the denominator of every impact present in that record, not the unit of the impact indicator itself.
+
+### Functional units by collection
+
+| Files | Functional unit | Meaning |
+| --- | --- | --- |
+| [`data/energy/energy-impacts.*`](./data/energy) | `kWh` | Impact per kilowatt-hour of electricity generated by the specified technology. The fixed functional unit is not repeated in each record. |
+| [`data/factor/*`](./data/factor) | `kWh` | Impact per kilowatt-hour of electricity consumed for the specified geography and period. The fixed functional unit is not repeated in each record. |
+| [`data/facility/factors.*`](./data/facility) | `kWh` | Impact per kilowatt-hour of electricity or fuel energy. For fuels, `-pci` and `-pcs` in the factor ID identify the lower or higher calorific value basis. |
+| [`data/transport/factors.*`](./data/transport) | `pkm` or `vkm` | Impact per passenger-kilometre for collective and active transport, or per vehicle-kilometre for individual motor vehicles. |
+| [`data/equipment/embodied.*`](./data/equipment) | `/s` or `/GB/km` | Embodied impact allocated per second for equipment and virtual machines, or per gigabyte-kilometre for networks. |
+| [`data/equipment/energy.*`](./data/equipment) | `W` or `Wh/GB/km` | Operational power for equipment and virtual machines, or electricity used per gigabyte-kilometre for networks. These fields are energy values, not environmental impacts. |
+
+`pkm` means one passenger transported over one kilometre. `vkm` means one vehicle travelling one kilometre, independently of its passenger count. `GB/km` means one gigabyte transferred over one kilometre.
+
+### Common impact indicators
+
+The following indicators and native units are shared by the energy, electricity factor, facility, transport, and equipment collections. They follow the Environmental Footprint impact-category conventions documented by the [European Commission Joint Research Centre](https://publications.jrc.ec.europa.eu/repository/bitstream/JRC130796/JRC130796_01.pdf).
+
+| Field | Environmental impact | Native unit |
+| --- | --- | --- |
+| `adpe` | Resource use, minerals and metals | `kg Sb eq` |
+| `ap` | Acidification | `mol H+ eq` |
+| `ctue` | Freshwater ecotoxicity | `CTUe` |
+| `ctuh-c` | Human toxicity, cancer | `CTUh` |
+| `ctuh-nc` | Human toxicity, non-cancer | `CTUh` |
+| `gwp` | Climate change, global warming potential over 100 years | `kg CO2 eq` |
+| `ir` | Ionising radiation, human health | `kBq U-235 eq` |
+| `pm` | Particulate matter, human health | `disease incidence` |
+| `wu` | Water use | `m3 world eq` |
+
+The complete unit is obtained by dividing the native unit by the collection's functional unit. Examples include `kg CO2 eq/kWh`, `mol H+ eq/kWh`, `kg CO2 eq/pkm`, and `kg CO2 eq/vkm`.
+
+An absent JSON property or an empty CSV cell means that the indicator is not available for that factor. It must not be interpreted as zero. An explicit numeric `0` is a known zero value.
+
+### Additional equipment indicators
+
+[`data/equipment/embodied.*`](./data/equipment) also contains the following indicators. Their native units are divided by the `unit` stored in the same equipment record.
+
+| Field | Environmental impact | Native unit |
+| --- | --- | --- |
+| `adpf` | Resource use, fossils | `MJ` |
+| `epf` | Eutrophication, freshwater | `kg P eq` |
+| `epm` | Eutrophication, marine | `kg N eq` |
+| `ept` | Eutrophication, terrestrial | `mol N eq` |
+| `gwpb` | Climate change, biogenic | `kg CO2 eq` |
+| `gwpt` | Climate change, total | `kg CO2 eq` |
+| `gwplu` | Climate change, land use and land-use change | `kg CO2 eq` |
+| `lu` | Land use, soil quality index | `Pt` (dimensionless) |
+| `odp` | Ozone depletion | `kg CFC-11 eq` |
+| `pocp` | Photochemical ozone formation | `kg NMVOC eq` |
+| `mips` | Material input per service unit | `kg` |
+
+### Cloud sustainability metrics
+
+Cloud region files use additional operational indicators which are not life-cycle impact categories:
+
+| Field | Metric | Unit |
+| --- | --- | --- |
+| `pue` | Power Usage Effectiveness | Ratio, dimensionless |
+| `wue` | Water Usage Effectiveness | `L/kWh` |
+| `ref` | Renewable Energy Factor | Ratio from `0` to `1` |
+
+## Electricity impact factors: `data/factor/`
+
+Files use `<geography>-<frequency>[-green].json`, with matching CSV files:
+
+- Geography: `subdivision`, `country`, `continent`, `world`.
+- Frequency: `yearly`, `monthly`.
+- Scenario: no suffix for the modeled full mix; `-green` for the renewable-only scenario.
+
+For example, [subdivision-yearly.json](./data/factor/subdivision-yearly.json) and [subdivision-monthly.json](./data/factor/subdivision-monthly.json) contain sub-national series. Reading only [country-yearly.json](./data/factor/country-yearly.json) is insufficient to determine whether sub-national factors exist. Coverage of one subdivision does not imply coverage of all subdivisions or periods.
+
+Country, continent and subdivision JSON use `{ territory: { period: { indicator: value } } }`. World JSON uses `{ period: { indicator: value } }`, without an extra world wrapper. Check the existing continent names instead of assuming continent codes are used as time-series keys.
+
+The shared indicators are `adpe` (resource use, minerals and metals), `ap` (acidification), `ctue` (freshwater ecotoxicity), `ctuh-c` and `ctuh-nc` (human toxicity, cancer and non-cancer), `gwp` (climate change), `ir` (ionising radiation), `pm` (particulate matter) and `wu` (water use). These are distinct impact categories with different native units. Electricity factors are per kWh; `gwp` is in kg CO2 equivalent/kWh. Check the source methodology for other indicator units and characterization methods before combining datasets. Do not infer physical liters of water from a water-impact indicator or add different impact categories together.
+
+Impact = electricity consumption in kWh × factor per kWh. Educational example: 100 kWh × 0.05 kg CO2e/kWh = 5 kg CO2e. The example factor is fictional; read the dataset value for a real calculation.
+
+Node.js example in a project that depends on this package:
+
+```js
+const factors = require('@digital4better/data/data/factor/subdivision-yearly.json');
+const territory = 'CA-QC';
+const period = '2023';
+const factor = factors[territory]?.[period]?.gwp;
+if (typeof factor !== 'number' || !Number.isFinite(factor)) {
+  throw new Error(`No usable gwp factor for ${territory} / ${period}`);
+}
+const result = { territory, period, factor, kWh: 100, kgCO2e: 100 * factor };
+```
+
+### Renewable-only scenario
+
+The `-green` variant keeps Bioenergy, Hydro, Solar and Wind and renormalizes their shares to total 100%. Factors are computed from this hypothetical mix. It describes neither the territory's actual electricity mix nor a green electricity contract, and its lifecycle impacts are not zero. If no selected renewable source is available, a green value can be unavailable. Do not silently use `-green` as a replacement for the full mix.
+
+### Sources and boundaries
+
+Electricity series are derived from [Ember](https://ember-climate.org/data-catalogue/) and lifecycle references including [UNECE 2021](https://unece.org/sed/documents/2021/10/reports/life-cycle-assessment-electricity-generation-options). Generation and imports are processed by the repository's methodology. Factors are modeled lifecycle references, not instantaneous grid measurements, marginal emissions or a guarantee of hourly coverage. The [impact assessment methodology](https://digital4better.github.io/methodology/en/) provides further context.
+
+## Electricity mixes: `data/mix/`
+
+The same 16 geography/frequency/scenario filename combinations and temporal JSON nesting apply. For example, [country-yearly.json](./data/mix/country-yearly.json) contains country series and [world-monthly.json](./data/mix/world-monthly.json) contains period-keyed world values.
+
+Values are shares, normally between 0 and 1, rather than percentages or impact factors. Technology keys include `Bioenergy`, `Coal`, `Gas`, `Hydro`, `Nuclear`, `Other Fossil`, `Other Renewables`, `Solar` and `Wind`. Preserve their spelling. Shares can differ slightly from a total of 1 because of rounding. Missing values must not be filled with zero without justification. Renewable-only variants follow the scenario definition above.
+
+## Cloud infrastructure: `data/cloud/`
+
+The provider prefixes are `aws`, `azure`, `gcp`, `oracle`, `ovhcloud` and `scaleway`. Each has `<provider>-regions.json` and `<provider>-vms.json`, with matching CSV files. Shared [cpus.json](./data/cloud/cpus.json) and [accelerators.json](./data/cloud/accelerators.json) describe hardware. JSON roots are arrays of records. Provider catalogs describe reference offerings and may include historical entries, not a real-time availability check.
+
+### Regions
+
+Common fields include `id`, `name`, optional `aliases`, `provider`, `location`, `country`, `lat`, `lon`, `pue`, `wue` and `ref`. Match provider-specific identifiers and aliases before joining to another catalog. Coordinates are reference locations, not exact datacenter addresses.
+
+- `pue`: total datacenter energy divided by IT energy, dimensionless.
+- `wue`: water use relative to energy; check the provider's reporting boundary and source unit before comparison.
+- `ref`: renewable-energy-related fraction from 0 to 1 in this referential. Regional CFE figures are used for Google; CFE and renewable matching are not interchangeable measures.
+
+Provider conventions retained in this checkout:
+
+- AWS: regional 2024 PUE/WUE disclosures; REF remains zero by convention. It does not establish that AWS uses no renewable electricity.
+- Azure: regional fact sheets, including previously curated values where old PDFs are no longer retrievable.
+- GCP: regional CFE for REF and previously derived water figures pending clearer regional disclosures.
+- Oracle: uniform PUE 1.07 and provisional WUE zero, which does not establish no water use.
+- OVHcloud: FY25 published KPI assumptions.
+- Scaleway: datacenter figures supplemented by impact reports.
+
+Check reporting year, regional versus global scope, method and units before comparing providers. Lower PUE alone does not establish lower total environmental impact. The [README cloud section](./README.md#cloud-infrastructure) links source disclosures and detailed assumptions.
+
+### Machines and hardware
+
+Machine fields can include `id`, `name`, `family`, `category`, `vcpus`, `ocpus`, `memory`, `ssd`, `hdd`, `cpu`, `accelerator`, `accelerators`, `virtual` and `embodied`. Not every field occurs in every provider. Some provider machine files include bare-metal entries: check `virtual` rather than treating every entry as virtual. Memory and storage are documented in GB. `embodied` describes a modeled embodied climate impact in tCO2e, not electricity use or a per-kWh factor.
+
+CPU references include manufacturer, series/model, architecture/platform, cores, threads, TDP, process, die area, transistors and socket support where available. Accelerator references include type, manufacturer, model, memory and hardware characteristics. TDP is a thermal design envelope in W, not a workload-specific electricity measurement. Check the actual record types: some source fields are strings or lists. Do not silently reinterpret zero placeholders, comma decimal strings, scalar CPU references or arrays.
+
+## AI models: `data/ai/`
+
+[models.json](./data/ai/models.json) is an array of model records; [models.csv](./data/ai/models.csv) is its tabular projection.
+
+- `name`, `vendor`, `type`, `architecture`: source identifiers and model classification.
+- `pattern`: a name-recognition expression, not a provider API endpoint.
+- `parameters.active` and `parameters.total`: active and total parameters in billions. Distinguish these for mixture-of-experts architectures.
+- `context`: context capacity in tokens, not a guaranteed output length.
+- `input`, `output`: supported modalities.
+- `reasoning`, `tools`: recorded capabilities.
+- `providers`: hosting-provider identifiers and variants, not universal identifiers.
+- `estimated`: fields identified as estimates. Check it before presenting parameters or context as vendor disclosures.
+- `sources`: URLs for provenance and further verification.
+- `open`: an openness flag; it does not substitute for the model's license.
+
+Not every model has every field. Legacy models and historical/restricted provider references can remain. Check current provider availability separately. Model size alone is insufficient to calculate environmental impacts; no per-model environmental footprint is supplied. Preserve upstream attribution for adapted estimates. This includes EcoLogits contributors and Samuel Rince where their estimates or family proxies are retained; do not present these as vendor disclosures. Read the [AI audit](./data/ai/README.md), [parameter provenance](./data/ai/provenance.md) and [cloud coverage inventory](./data/ai/cloud-coverage.md) for their boundaries and unresolved historical assumptions.
+
+The [README AI section](./README.md#ai-models) links provider catalogs, vendor documentation, model cards and technical sources.
+
+## Equipment: `data/equipment/`
+
+[energy.json](./data/equipment/energy.json) and [embodied.json](./data/equipment/embodied.json) are objects keyed by equipment or infrastructure category, with corresponding CSV files. These are modeling references, not measurements of every device.
+
+Energy entries contain `description`, `value` and `unit`. A value in W is operational power: divide by 1000 and multiply by operating hours to obtain kWh. Some network entries use `Wh/GB/km`; preserve their stated convention and check the model's traffic/distance allocation before use.
+
+Embodied entries contain a description, `unit` and environmental indicators. Many factors use `/s` to allocate embodied impacts per second of use, while network factors can use `/GB/km`. A `/s` factor is not a device's total manufacturing impact. Keep allocation duration and the model's network unit convention explicit. Additional indicators include `adpf`, `epf`, `epm`, `ept`, `gwpb`, `gwpt`, `gwplu`, `lu`, `odp`, `pocp` and `mips`. Verify their source units before comparison; do not treat energy values as environmental impact factors.
+
+## Energy technologies: `data/energy/`
+
+[energy-impacts.json](./data/energy/energy-impacts.json) maps generation technology names to the nine shared environmental indicators, with a matching CSV file. Factors are lifecycle impacts per kWh of electricity generation. They are inputs to electricity mix modeling and do not describe instantaneous emissions of an individual power plant. Use the exact technology keys and preserve indicator-specific units. See the electricity source references above and the [README energy section](./README.md#electricity-mix-and-impact-factors).
+
+## Building energy: `data/facility/`
+
+[factors.json](./data/facility/factors.json) is an array of annual records, with a matching CSV file. Select by `id`, `location` and `period`. Each record provides a functional `unit` of `kWh`, available environmental indicators, `source` and `sourceUrl`.
+
+`electricity-grid` records for France (`FR`) and Europe (`EU`) retain all nine annual electricity impacts. The generator synchronizes them with `factor/country-yearly.json` at `FR` and `factor/continent-yearly.json` at `Europe`. Combustible factors are maintained separately from ADEME Base Carbone total records: upstream and combustion components are included, and only GWP is published when the other indicators cannot be verified on the same boundary.
+
+Fuel identifiers such as `natural-gas-pci`, `natural-gas-pcs`, `heating-oil-pci`, `propane-pci` and `wood-pellets-pci` encode lower (PCI) or higher (PCS) calorific value bases. Match the base of the input energy to the selected factor. Periods vary by fuel and location; do not assume all factors have the latest electricity year. District heating/cooling and an EU wood-pellet equivalent are absent. See the [facility source notes](./data/facility/README.md) for exact records and boundaries.
+
+## Transport: `data/transport/`
+
+[factors.json](./data/transport/factors.json) is an array of annual employee travel references, with a matching CSV file. Select by `id`, `location` and `period`; read `unit`, available indicators, `source` and `sourceUrl` from that record.
+
+Collective and active transport uses passenger-kilometres (`pkm`), while individual motor vehicles use vehicle-kilometres (`vkm`). GWP is therefore kg CO2 equivalent/pkm or kg CO2 equivalent/vkm respectively. Do not multiply a vehicle-kilometre factor by passenger-kilometres without an explicit occupancy conversion. Missing non-GWP indicators are unavailable, not zero.
+
+The French catalogue covers four flight distance bands, rail, coach, bus, tram, metro, cars, two-wheelers and active travel. ADEME Impact CO2 source requests exclude vehicle construction; flight factors retain radiative forcing. Source periods and transport mode assumptions vary. `location` describes the reference context, not the origin/destination of a trip. There is no published European equivalent or implicit French-to-European fallback. See the [transport source notes](./data/transport/README.md) for mode identifiers, aviation bands and source mappings.
+
+## Geographic references: `data/country/`
+
+- [continents.json](./data/country/continents.json): array of continent codes and names.
+- [countries.json](./data/country/countries.json): array of country names, alpha-2/alpha-3 codes and continent names.
+- [regions.json](./data/country/regions.json): array of world, continent, country or subdivision reference records with type-specific identifiers, geographic mappings and coordinates. Inspect `type` and the record's actual fields before joining.
+- [regions-paths.json](./data/country/regions-paths.json): SVG path geometry keyed by source territory identifiers; a visualization asset, not emission factors.
+- [country-to-country-distances.json](./data/country/country-to-country-distances.json): approximate distances keyed by concatenated origin/destination country identifiers.
+- [region-to-region-distances.json](./data/country/region-to-region-distances.json): approximate distances keyed by concatenated region identifiers; identifier lengths can vary.
+- [user-to-datacenter-distances.json](./data/country/user-to-datacenter-distances.json): approximate distance references keyed by source region identifier.
+
+Distance values use kilometers and are modeling approximations, not measured internet routes, latency or routing guarantees. Confirm origin/destination membership before splitting composite keys; do not assume every identifier is two characters long. Matching CSV files exist for these references except `regions-paths.json`. A geographic record or map outline does not prove electricity factor coverage for that geography.
+
+## Reuse, attribution and online references
+
+The database is licensed under [ODbL 1.0](./LICENCE). Read the license for reuse, attribution and sharing conditions. Preserve source URLs, assumptions and any upstream credits accompanying adapted data. Suggested dataset attribution: Digital4Better Open Data — collection/file — installed package version — ODbL 1.0 — https://github.com/digital4better/data.
+
+Useful online entry points:
+
+- [Website documentation index](https://digital4better.github.io/data/llms.txt).
+- [Complete website reference](https://digital4better.github.io/data/llms-full.txt).
+- [Current website catalog](https://digital4better.github.io/data/catalog.json), with dataset fields, coverage summaries and absolute download URLs. It describes the deployed site, not necessarily this installed package.
+- [English methodology](https://digital4better.github.io/data/en/methodology/) and [French methodology](https://digital4better.github.io/data/fr/methodology/).
+- [English electricity guide](https://digital4better.github.io/data/en/guides/electricity/), [cloud metrics guide](https://digital4better.github.io/data/en/guides/cloud-metrics/) and [AI models guide](https://digital4better.github.io/data/en/guides/ai-models/).
+- [Repository and issue tracker](https://github.com/digital4better/data).

package/llms.txt

@@ -0,0 +1,31 @@
+# Digital4Better Open Data — npm package
+
+> Reference JSON and CSV datasets for digital sustainability: electricity impacts and mixes, cloud infrastructure, AI models, equipment, energy technologies, building energy, transport and geography.
+
+This file describes the installed `@digital4better/data` package. Read files by path; there is no query API. Check the installed `package.json` for its version. Local files are authoritative for that version; the website may describe newer data.
+
+Before reporting missing data, inspect the relevant collection and check the exact territory, period and indicator. Electricity factors and mixes include subdivision, country, continent and world files, with yearly, monthly and `-green` variants. The existence of a subdivision file does not guarantee coverage of every subdivision. Missing values are not zero; never silently substitute another geography or period. Green variants describe a hypothetical renewable-only mix. Preserve source identifiers, units, estimates and attribution. License: ODbL 1.0.
+
+## Local documentation
+
+- [Complete package reference](./llms-full.txt): File inventory, schemas, lookup procedure, examples, sources and limitations; readable offline.
+- [Package overview](./README.md): Collections, source families and provider assumptions.
+- [Package metadata](./package.json): Installed version and release metadata.
+- [License](./LICENCE): ODbL 1.0 terms.
+
+## Data collections
+
+- [Electricity impact factors](./data/factor/): Impacts per kWh, by geography and period. For sub-national data inspect `subdivision-yearly.json` or `subdivision-monthly.json`.
+- [Electricity mixes](./data/mix/): Technology shares using the same geography/period naming scheme.
+- [Cloud infrastructure](./data/cloud/): Provider regions and machines, CPU and accelerator references.
+- [AI models](./data/ai/): Model characteristics, provider identifiers, estimates and source URLs.
+- [Equipment](./data/equipment/): Operational energy and allocated embodied impacts; read each entry's `unit`.
+- [Energy technologies](./data/energy/): Lifecycle impact factors by electricity generation technology.
+- [Building energy](./data/facility/): Purchased electricity and fuel factors per kWh, with explicit PCI/PCS bases.
+- [Transport](./data/transport/): Employee travel factors per passenger-kilometre or vehicle-kilometre.
+- [Geography](./data/country/): Country, continent and subdivision references, SVG paths and approximate distances.
+
+## Optional online documentation
+
+- [Website documentation index](https://digital4better.github.io/data/llms.txt): Bilingual collection pages and guides for the current website snapshot.
+- [Website catalog](https://digital4better.github.io/data/catalog.json): Current published dataset metadata and download URLs; check against the installed package before use.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@digital4better/data",
-  "version": "1.3.66",
+  "version": "1.3.68",
   "description": "Digital4Better Open Data",
   "license": "ODbL-1.0",
   "repository": {
@@ -40,8 +40,10 @@
     "data/*",
     "package.json",
     "README.md",
+    "llms.txt",
+    "llms-full.txt",
     "LICENSE"
   ],
-  "releaseDate": "2026-10-31T00:03:22.215Z",
+  "releaseDate": "2026-11-06T13:43:16.631Z",
   "packageManager": "yarn@1.22.21+sha512.ca75da26c00327d26267ce33536e5790f18ebd53266796fbb664d2a4a5116308042dd8ee7003b276a20eace7d3c5561c3577bdd71bcb67071187af124779620a"
 }