Suppliers answer in their own format; the STS label makes their emissions data machine-readable, traceable and comparable.
What it is
Suppliers answer with what they already have; the customer reads one label along the chain.
STS Exchange Platform is a demo that makes the Sustainability Transaction Standard tangible for the STS working group. A battery maker sends one STS label for one container to its mine, its refiner and its carrier; each answers with the document it already has, in its own layout, and an AI reads it into the label. The customer sees labelled values only, follows them along the chain to its Scope 3, asks questions in plain words and exports the data. Today about one supplier in a hundred answers a questionnaire; here no supplier fills in a form.
The idea in one picture
One container travels from the mine to the customer. At every stop the party sends the document it already has; the AI reads it into an STS transaction; the emissions embedded in the material grow with it — and the customer reads its Scope 3 at the end, every figure citing the transaction behind it.
24 t lithium concentrateCNT-BR-0417 · 15.6 t lithium carbonateCNT-BR-0417 delivered
Q
Quillara LithiumMine · extraction
Its own documentSite energy and fuel records“Direct emissions, fuel at site” 18.4 · “Scope 2” 4.9
Its own documentQuarterly environmental statement“Process fuel” 3.6 · “Purchased electricity” 8.8
AI reads it into the label
STS-PR-0001Own Scope 1–2measured and estimated12.4+ arrived with the materialSTS-EX-000123.3= passes on35.7 tCO2e
Embedded so far
F
Ferrovane FreightCarrier · sea and road
Its own documentShipment emission statement“Transport emissions, sea and road” 2.5
AI reads it into the label
STS-SH-0001Transport of the containerestimated2.5+ arrived with the materialSTS-PR-000135.7= passes on38.2 tCO2e
Embedded so far
V
Velmora Battery WorksCustomer · end of the chain
Scope 3 for this container38.2 tCO2e
Category 14
Category 1 · mine and refiner35.7Category 4 · carrier2.5
Show Category 1 emissions by supplier.citesSTS-EX-0001 · STS-PR-0001
The customer sees labelled values — never the suppliers’ files.
Answers in any format
Each supplier uploads its own document; the label makes it machine-readable — no shared template first.
Labelled, never raw
The customer works with labelled values only — six fields, eight questions — never the supplier’s file.
Every number cited
An answer names the STS transactions behind each figure; the chain mine → refiner → carrier is the audit trail.
Missing means missing
A value the document lacks is an error, named item by item — never a guessed figure.
Who uses it
One presenter plays every party: the customer and its three suppliers.
ML
Presenter
Maya Lindqvist, for the STS working group
Walks the working group through the demo and plays every party in turn with the switch; starts over.
Web, on a large screen
DW
Customer
Dana Whitfield, Velmora Battery Works
Keeps or changes the example, sends the request, follows the chain, reviews each response, asks the queries, exports.
Web
LF
Supplier · mine
Lucía Ferraro, Quillara Lithium
Extraction: answers the request with its own document; first in the chain, with no upstream party.
Web, its own screen
KA
Supplier · refiner
Kenji Arai, Brisemont Refining
Processing into battery-grade material; the customer’s direct supplier of the material, Category 1 with the mine.
Web, its own screen
TB
Supplier · carrier
Tomás Brandt, Ferrovane Freight
Transportation from the refiner to the customer, Category 4; last in the chain, its total is the customer’s Scope 3. Replaces its document after an error — and after a clarification, if time allows.
Web, its own screen
Modules
Six parts, all in the core; what each adds if time allows.
Setup
Two prepared industries, the four parties with their IDs, renamed without the AI; the container; the presenter’s switch and start-over.
CoreIf time allows:Live generation for an industry that is not prepared.
Label and request
The STS label for one container — its profile, six fields, eight questions, its definition — sent to all three suppliers; the chain and its roll-up.
Core
Supplier response
Each supplier’s own screen: the request and what arrives with the container, the upload, its status and its label, the customer’s outcome.
CoreIf time allows:A file of the presenter’s own; the answer to a clarification with a replacement.
Interpretation
The AI reads each document into one STS transaction; a missing value puts it in error.
Core
Review
Labelled values and context, never the file; accept, or request clarification with a note.
CoreIf time allows:The review of a replacement that answers a clarification, with the note beside it.
Queries and export
Questions in plain words answered with cited transactions; the labelled data out as CSV.
CoreIf time allows:Excel and JSON beside CSV; the times on each transaction.
How it works
Set up, request, respond, interpret, review, ask — one loop for one container.
Set up
The prepared lithium example is in place; the customer may change the industry and the four names.
Request
One label for one container goes to the mine, the refiner and the carrier at once.
Respond
Each supplier uploads its own document, in any layout, with its own emissions only: what it received arrives with the container.
Interpret
The AI fills the label — six fields, eight answers, a method flag per figure — or names what is missing.
Review
The customer reads labelled values only, and accepts or asks for clarification.
Ask and export
Five questions answered with cited transactions; the data goes out as a file.
The chain of STS transactions — mine → refiner → carrier → customer — holds it together: every figure rolls up along it and every answer cites it.
Sample company
A fictional battery maker and its lithium chain; every figure is synthetic.
Velmora Battery Works — a battery maker in Austin, Texas, and its lithium chain: Quillara Lithium extracts lithium concentrate at Salar Quillara in Chile and delivers it to Brisemont Refining in Mejillones, which turns it into battery-grade lithium carbonate; Ferrovane Freight carries the container by sea to Houston and by truck to Austin. One container, CNT-BR-0417, 15.6 t of lithium carbonate; every figure in tCO2e.
The chain, upstream
Velmora Battery WorksCustomer
Ferrovane FreightCarrier · transportation
Brisemont RefiningRefiner · processing
Quillara LithiumMine · extraction
People
Maya Lindqvist · Presenter
Dana Whitfield · Customer
Lucía Ferraro · Supplier · mine
Tomás Brandt · Supplier · carrier
Kenji Arai · Supplier · refiner
“Today” on every screen is 2026-10-25.
From the concept you saw
What the demo keeps of the design concept shown on 15 October, and why the rest waits.
On 15 October you saw our design concept of a full product. The demo takes its look and the parts that show STS at work; the rest waits for the PoC or MVP.
Concept screen
In the demo
Why
STS Dictionary
The label definition: meaning, unit, where each value comes from — the demo’s own, no versions
No STS dictionary exists yet; the working group defines it
Data mapping
The document’s term beside each value in the review; no conversion — each supplier states its own allocation
Labelling, not a template; conversions and checks are for the MVP
Create request
One label for one container, sent to all three suppliers at once
One clear Scope 3 example, not a request builder
Exchange records
The chain view and the review drawer: status chips, the response’s timeline
The chain is the audit trail
Supplier response
Request, upload, status and outcome on the supplier’s own screen
Clarification is a note, not a chat; an answer by a new document if time allows
Reports
Queries in plain words and the export of labelled data
Any format is fine, says AKFI: the customer uses BI or AI
Accounts, dashboards, integrations and per-item sharing belong to the PoC or MVP; one presenter plays every party
About this site
Every page of this site, and how to read it.
This site shows the product before it is built: the idea in one picture, the product in use — its flows, step by step, and its screens — how it is built, and its charts; then the questions we ask you to confirm, the demo specification and the next steps. Where it proposes something the product does not have yet, it says “proposed”.
Product
What the product is, who it is for, what it is built with, how its parts fit together — and the product in use: its flows step by step, then its screens.
Theme.The switch in the top bar sets light, dark or follow the device; every page follows.
Navigation.The menu lists every section; a root section is one page, its items scroll to its parts, and opening one folds the one that was open. ← → step through them; each page ends with previous and next.
Presentation.Press P, or add ?present=1 to the address: the page alone, larger. Escape leaves it.
Sample data.Names and figures are invented for a fictional company.