sustainability-data Repository Gateway

A reference deployment of /.well-known/sustainability-data (draft-besleaga-sustainability-wellknown).

This service is a reference deployment of the /.well-known/sustainability-data well-known URI defined in draft-besleaga-sustainability-wellknown. It serves one conformant JSON document per reporting subject, each at /{domain}/.well-known/sustainability-data, so that the convention can be exercised against real, sourced annual disclosures without waiting for each organization to deploy its own endpoint. In a real deployment the document lives on the subject's own origin; a gateway is only a way to demonstrate and test the format.

Please read. Documents served here about third parties are ILLUSTRATIVE MAPPINGS prepared by the gateway operator from those organizations' own published reports. They are NOT published, reviewed, authorized, or endorsed by their reporting subjects, and this gateway is not an authoritative origin for them. Every figure is traceable to the public source document named in that document's methodology-uri member; nothing is estimated, interpolated, or invented on the subjects' behalf. Documents whose subject is a reserved .example name are deliberately synthetic and describe nothing real.

Subjects served (11)

Adapter demonstrations (8)

One demonstration subject per adapter shipped by the published sustainability-wellknown-publisher package, so every adapter runs end to end in this gateway. Subjects marked live fetch a real upstream daily (only upstreams whose licenses permit attributed republication; the attribution is carried in band). Subjects marked replay run the SAME adapter code against a recorded upstream response, because no legal free live access to that upstream exists; their figures are synthetic and say so in band. All sit under reserved .example names: they demonstrate the format and describe no real organization.

Wire-format examples (14)

Every case from the specification repository's canonical example-responses set, served live. Array (trend) cases follow the draft's rule: the parameterless Basic response collapses to the most recent entry, and the full sorted array is returned only for ?granularity= requests on documents that themselves declare capabilities:extended. All figures are synthetic; the subjects are reserved .example names.

This gateway's own report

The gateway also reports on itself, as a service, at /.well-known/sustainability-data (target: sustainability-data-gateway).

Consumer cross-validation

At boot, every document this gateway serves was fetched through the published publisher pipeline and validated with the published consumer library — the same code a third party would run. A validation failure aborts startup. This deployment: sustainability-wellknown-consumer@0.5.2 validated 36 documents at boot.

Service level

This gateway implements the Basic service: query parameters are ignored and the Basic response is returned — never an error. The one deliberate exception: the wire-format examples that themselves declare capabilities: "extended" honor the granularity parameter and return their full sorted trend array, exactly as the draft's Extended service defines. Successful responses are application/json with Cache-Control: public, max-age=86400, Access-Control-Allow-Origin: *, a strong ETag and Last-Modified; If-None-Match yields 304. A method other than GET or HEAD yields 405 with Allow: GET, HEAD. An unknown subject yields 404.

Verify these documents yourself

Every document served here can be fetched and validated with the specification's published reference consumer (sustainability-wellknown-consumer, version 0.5.2 or later). --strict runs the full conformance battery — schema validation, media type, caching, conditional requests, method handling — and labels each check with the strength of the requirement it tests (a failed MUST is a conformance failure; an unmet SHOULD is a warning).

The gateway's own report, at this origin's true well-known location:

npx -y -p sustainability-wellknown-consumer sustainability-fetch https://sustainability.up.railway.app --strict

Any subject document — curated, adapter demonstration, or wire-format example — by giving its path-prefixed base URL; the consumer resolves /.well-known/sustainability-data under the prefix:

npx -y -p sustainability-wellknown-consumer sustainability-fetch https://sustainability.up.railway.app/cloudflare.com --strict
npx -y -p sustainability-wellknown-consumer sustainability-fetch https://sustainability.up.railway.app/grid-intensity-demo.example --strict
npx -y -p sustainability-wellknown-consumer sustainability-fetch https://sustainability.up.railway.app/yearly.example --strict
npx -y -p sustainability-wellknown-consumer sustainability-fetch https://sustainability.up.railway.app/<any-domain-above> --strict

The Extended trend arrays, by giving the full document URL with its granularity parameter (the consumer validates array documents too):

npx -y -p sustainability-wellknown-consumer sustainability-fetch "https://sustainability.up.railway.app/yearly.example/.well-known/sustainability-data?granularity=monthly"

To just fetch and read a document (or pipe it into your own tooling):

curl -s https://sustainability.up.railway.app/wikimedia.org/.well-known/sustainability-data | python3 -m json.tool

Independent of this project's tooling, the JSON validates against the specification's published JTD and CDDL schemas.

Machine-readable index

/index.json carries the same list, this notice included.