Online map imagery · fictional case
Design a flight scenario
Change the route, indicative aircraft fuel intensity, SAF origin and blend. The aircraft moves on the actual Cesium globe.
Paris → New York
Waiting for the globe…
Select an action to preview a human decision note.
From one flight to a decision horizon.
Change the route, aircraft profile, SAF share or incident on the globe. The flight case, annual volume, carbon proxy and evidence status below update together. All values are illustrative.
Flight scenario
Loading the scenario…
Method: flight fuel × SAF share × comparable flights/day × 365. Assumed repeated identical flights; capacity and buyer participation are hypothetical.
The horizon gap, year by year.
Example only: 12-year producer horizon versus 3-year buyer commitment. The years after buyer coverage are open, not lost fuel.
—
Potential is not an approved claim.
Illustrative arithmetic: assignable SAF tonnes × 3.827 tCO₂e/t fuel (89 gCO₂e/MJ CORSIA jet baseline × assumed 43 MJ/kg) × assumed lifecycle reduction. Real claims require an agreed method, energy content, eligible quantity, lifecycle data, rights, registry retirement and review.
One case, four controlled questions.
This browser demo reads the flight case locally. It does not retrieve live flights, producer capacity, commercial contracts, certificates or registry records. The detailed exploratory modules below have their own controls and assumptions.
From the globe to the decision.
The linked scenario above reads the globe controls. The exploratory Systems Twin, Intelligence and Mission Control modules below have their own controls and assumptions; their figures do not automatically inherit that flight case.
See the gap.
Follow the evidence.
One assumption travels through strategy, the evidence chain and a meeting. This journey shows where a decision could rely on verifiable information, and where it must still wait.
Exploratory demonstration. Figures, evidence and meeting content are fictional. Cards show statements in the simulator, not reviewed records or certified reductions.
The question that opens the case.
The scenario reads Systems Twin controls. Rates below are illustrative parameters, never a market forecast.
Load a scenario to reveal the gap between the represented horizons.
Evidence of physical delivery is separate from a displayed percentage.
A reduction needs a chain of evidence.
Six prototype questions follow the selected Systems Twin controls. Marked present does not mean verified.
From discussion to a reviewable note.
Paste only fictional or authorized text. Local rules process it; no audio is recorded and no remote AI is called.
One assumption.
One team. One decision.
A Systems Twin scenario becomes a working space: discussion, evidence requests, attribute ownership alerts and a decision note. Change the scenario and see what must be clarified before anyone acts.
One disruption. Five connected steps.
Move step by step: each fictional event changes the case, alerts and conversation. At the end, choose a response and see what it can actually establish.
Which response should the team explore?
An action in this demonstration creates no delivery or claim right. Choose the question to document.
SAF corridor · example case
Fictional roles: Operations · Finance · Compliance · CopilotThis prototype sends no messages. A real messenger needs accounts, permissions, a server, suitable security and an audit.

