Flows

A failed response and its retry

Edge case · The AI cannot read Quillara’s response; it fails, says why, and the retry is interpreted.

Who: The presenter, acting as the mine, Quillara Lithium, then as the customer, then as the mine again
Starts at: Quillara’s request
Ends with: The retry interpreted (14:31)

if time allows The core failure is The AI did not answer (step 5). The unreadable scan of steps 1–4 is a file of the presenter’s own, dropped in the zone — that path is built if time allows.

Step 1 of 6 This screen is not drawn yet

1 An unreadable file
STS ExchangeSustainability data network

QQuillara LithiumActing as the mine

Request

WalkthroughLithium-ion batteries
Synthetic data

Quillara LithiumRequest
Presenter’s control

Request
From Velmora Battery Works · the lithium concentrate that went into container CNT-BR-0417 · 24 t
Requested

Request
Upload
Interpretation
Outcome

What arrives with the materialNothing: you are first in the chain, and your own figures start it.

What the label asksSix mandatory fields and eight questions · label definition

Mandatory fields
Originating company IDTaken from this request, not from your documentRequired
Units of measurementAs your document gives them; nothing is convertedRequired
Source of dataWhere a value came from, in your document’s wordsRequired
VerificationSelf-verified, or third-party verified / auditedRequired
Scope 3 emissionsEmbedded at hand-over: your own figure plus what arrivedRequired
How the Scope 3 were producedYour own figure — Scope 1–2 or transport — and its methodRequired

QuestionsOptionalNot given in your document reads “not stated”
1Who generated the emissions?
2What activity caused them?
3Which product do they impact?
4Where did they occur?
5How were they calculated?
6When did they occur?
7Which STS transactions support the calculation?
8How do they roll up into Scope 3 reporting?

Your responsePick a prepared document or upload your own
Prepared documents
Mine response documentquillara-lithium-response.pdf · PDF
Your own file
Drop your response document here or browseAny simple text document in your own format, e.g. PDF
Picking a document or uploading a file submits it as it is — there is nothing to review first.
if time allows On Quillara’s request drops a file of its own in the zone 1: quillara-site-photo-scan.pdf, a scan with no text in it. Uploading is submitting; nothing is checked first.
2 Failed — nothing readable
STS ExchangeSustainability data network

QQuillara LithiumActing as the mine

Request

WalkthroughLithium-ion batteries
Synthetic data

Quillara LithiumRequest
Presenter’s control

Request
From Velmora Battery Works · the lithium concentrate that went into container CNT-BR-0417
Failed

What the label asksSix mandatory fields and eight questions

Request
Upload
Interpretation
Outcome

quillara-site-photo-scan.pdfSubmitted · only you see it

Response statusFailed

Nothing readable in the fileThe file is empty or cannot be read, so there is nothing to interpret. Pick another file.

SubmittedYour document is in and handed to the AI.
FailedNothing was read. No transaction is made and no value is guessed.

Your label is readable once interpreted, as the customer sees it.

Outcome

No outcomeA failed response has no transaction, so there is nothing for the customer to decide. A new upload is the way on.
The customer’s decision — accepted, or clarification requested with a note — appears here. Nothing alerts you; it is there when you open the screen.
You answer only with a new upload — there is no reply in words.
Sees the status Failed and which it was: Nothing readable in the file, so the way on is another file. It is not In error: there was nothing to read. No transaction is made and no value is guessed. Presses Customer 1 in the presenter’s control.

3 The customer’s chain

Presenter’s control

Chain view

CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

Chain incomplete

Q
Quillara LithiumMine · extraction

24 t lithium concentrate

Failed
Nothing readable in the fileNo transaction, no review status.
B
Brisemont RefiningRefiner · processing

24 t concentrate → 15.6 t lithium carbonate

Requested
No transaction yet
F
Ferrovane FreightCarrier · transportation

CNT-BR-0417 · 15.6 t, Mejillones → Austin

Requested
No transaction yet
V
Velmora Battery WorksCustomer · end of the chain

CNT-BR-0417 delivered

No transaction of its own

Roll-upIncomplete · no category sum

Party	Own emissions	Embedded received	Reported total	Review
QQuillara	Quillara Lithium is missing from the sum: the response failed, no transaction			Failed
BBrisemont	—	—	—	Requested
FFerrovane	—	—	—	Requested

Quillara’s step reads Failed, with no transaction and no review status; the other steps are as they were. The roll-up names Quillara Lithium as missing. Nothing to act on here: the way on is the supplier’s. Presses Mine 1.

4 Retry
STS ExchangeSustainability data network

QQuillara LithiumActing as the mine

Request

WalkthroughLithium-ion batteries
Synthetic data

Quillara LithiumRequest
Presenter’s control

Request
From Velmora Battery Works · the lithium concentrate that went into container CNT-BR-0417
Failed

What the label asksSix mandatory fields and eight questions

Request
Upload
Interpretation
Outcome

quillara-site-photo-scan.pdfSubmitted · only you see it

Response statusFailed

Nothing readable in the fileThe file is empty or cannot be read, so there is nothing to interpret. Pick another file.

SubmittedYour document is in and handed to the AI.
FailedNothing was read. No transaction is made and no value is guessed.
Pick another file
Mine response documentquillara-lithium-response.pdf · PDF
Picking a prepared document submits it at once; a new upload after a failure is not confirmed.

Outcome

No outcomeA failed response has no transaction, so there is nothing for the customer to decide. A new upload is the way on.
The customer’s decision — accepted, or clarification requested with a note — appears here. Nothing alerts you; it is there when you open the screen.
You answer only with a new upload — there is no reply in words.
Back as the mine, the failed status stands and the prepared document is offered. Picks it 1. A new upload after Failed is not confirmed.
5 The AI did not answer (alternative)
STS ExchangeSustainability data network

QQuillara LithiumActing as the mine

Request

WalkthroughLithium-ion batteries
Synthetic data

Quillara LithiumRequest
Presenter’s control

Request
From Velmora Battery Works · the lithium concentrate that went into container CNT-BR-0417
Failed

What the label asksSix mandatory fields and eight questions

Request
Upload
Interpretation
Outcome

quillara-lithium-response.pdfSubmitted · only you see it

Response statusFailed

The AI did not answerThe file is fine; the AI service returned nothing usable in time. Upload the same file again.

SubmittedYour document is in and handed to the AI.
FailedThe AI did not answer in time. No transaction is made and no value is guessed.

Your label is readable once interpreted, as the customer sees it.

Outcome

No outcomeA failed response has no transaction, so there is nothing for the customer to decide. A new upload is the way on.
The customer’s decision — accepted, or clarification requested with a note — appears here. Nothing alerts you; it is there when you open the screen.
You answer only with a new upload — there is no reply in words.
The core failure; an alternative to step 4’s outcome, not continued. The retry meets the other cause: Failed says The AI did not answer in time. The file is fine, so the way on is to upload the same file again 1. The flow goes on from step 6.
6 Interpreted
STS ExchangeSustainability data network

QQuillara LithiumActing as the mine

Request

WalkthroughLithium-ion batteries
Synthetic data

Quillara LithiumRequest
Presenter’s control

Request
From Velmora Battery Works · the lithium concentrate that went into container CNT-BR-0417
Interpreted

What the label asksSix mandatory fields and eight questions

Request
Upload
Interpretation
Outcome

quillara-lithium-response.pdfSubmitted Oct 25 14:30 · only you see it

Response statusInterpreted

SubmittedYour document is in and handed to the AI.Oct 25 14:30
InterpretedThe AI read it into a transaction for the customer to review.Oct 25 14:31

Your label is readable, as the customer sees it. The status stays as it is when the customer decides.

Outcome

No decision yetThe customer has not accepted the response or asked for clarification.
The customer’s decision — accepted, or clarification requested with a note — appears here. Nothing alerts you; it is there when you open the screen.
Until the customer acts, this screen shows the status only.
The retry is submitted (14:30) and interpreted (14:31): the status Interpreted, and its label readable. On the customer’s side Quillara’s step takes its transaction STS-EX-0001, review pending. Nothing to act on: the end of the flow.