How it works
What is proven
One chain runs on live data from a provider’s feed to a public page. The others stop earlier, and this page says where each one stops and what closes the gap.
How to read this page
Proven on live data - Every step, from the provider to where a reader meets it, has run on live data.
Partly proven - The first steps run on live data. The rest has not yet been shown end to end.
Not yet proven - The software exists, but live data has not yet flowed through it.
Simulated only - It runs end to end against a simulation, not real equipment.
Each chain’s state was recorded in the platform audit of 12 September 2026. Where a chain ends somewhere public, it is also re-checked against the live service, and the date of that check is shown beside it.
From acquisition to every end
Provider feeds to the public map and current information
Partly proven - Furthest step proven
- Fetched, scanned, stored as it arrived, standardised, published, projected and served by the public API to the map and the current information page.
- Where it stops
- A single recorded run from one provider’s feed all the way to the map has not been captured since the latest changes to the service.
- What closes it
- Run the live map check and record its run.
- Checked 2026-09-12
- 12 public records served by the public API.
Source delivery to source availability
Proven on live data - Furthest step proven
- Every source product is served by the public API and shown on the source availability page.
- Where it stops
- Nowhere. This chain is complete.
- What closes it
- Nothing is outstanding.
- Checked 2026-09-12
- 22 source products served by the public API.
Fuel treatments to the map and community plans
Partly proven - Furthest step proven
- A thousand treatment locations on the map, and 3,193 treatment records retrieved for the community plans page.
- Where it stops
- No adopted community plan has been published yet.
- What closes it
- A plan published by the authority that adopted it.
Satellite detections to incident coordination
Not yet proven - Furthest step proven
- None on live data yet.
- Where it stops
- Detections are fetched, but not yet stored as observations. Candidate fires carry no location, and grouping detections into one fire has not been validated.
- What closes it
- Store detections as observations, which is engineering work, and a set of fires labelled by people to validate against.
Data to training, evaluation and a model card
Not yet proven - Furthest step proven
- Registered datasets and their acquisitions, on live data.
- Where it stops
- The live experiment ledger holds no runs. Training, evaluation and qualification run on reference data today.
- What closes it
- The rights to train on provider data, the training infrastructure, and independent review of the results.
A drone mission to aviation evidence
Simulated only - Furthest step proven
- The mission protocol runs end to end against a simulation of the aircraft.
- Where it stops
- Nothing has flown on real hardware, and the drone subsystem is not yet connected to aviation evidence.
- What closes it
- That connection, testing with hardware in the loop, and the aviation approvals that sit outside this project.
Protected workspaces with real sessions
Partly proven - Furthest step proven
- Deployed, and every protected capability refuses a caller who has not signed in.
- Where it stops
- The signed-in end-to-end test suite has not yet been run against the live site.
- What closes it
- Run the signed-in suite against the live site and record the result.
- Checked 2026-09-12
- 3 of 3 protected capabilities refused an anonymous caller.