Run the fitted AI on the untouched held-out evidence.
More data made delivery ETAs worse.
On this delivery dataset, a high-volume but unreliable feed pushed predictions farther from the real delivery time. The proposed safeguard helped too little and failed other tests.
Watch one delivery change
when unreliable data reaches the AI.
This is real server-side inference. First run the trusted pipeline. Then run the full degraded scenario—retrained model plus matching degraded inputs—and test the safeguard.
Use the model retrained on the simulated unreliable feed and this delivery’s matching degraded inputs.
Weight trust, back off suspicious inputs, and check review risk.
Each step makes a fresh request to the online backend and evaluates the corresponding fitted model.
What is live? Training happened beforehand for speed and repeatability. Every button evaluates the exported fitted trees on the selected held-out delivery in the online Worker. The real outcome is never a model input.
Start with the conclusion.
Open the detail when you need it.
The key scenario is already selected: the noisy feed, with the safeguard off. Turn the safeguard on to see whether it recovers the loss.
Read the plain-language result first. The figures and timeline underneath are supporting evidence, not the headline.
The feed raises the average prediction miss by 2.1 minutes compared with the trusted-data reference.
Explore the detailed resultsTimeline, large misses, repeatability, and data-quality signals
The safeguard helps one test—and fails the overall decision.
We repeated the same comparison with trusted data, old data, the noisy feed, and both problems together.
Follow the failure,
not just the score.
Area history freezes. A low-reliability feed grows to 55% of records.
Distance and historical ETA drift away from the clean reference.
The noisy source contributes more examples than the accurate source.
ETA error and review workload change on the same future orders.
Trust data in proportion to its evidence.
The safeguard changes influence rather than deleting every suspicious record.
Low-trust training rows count less.
Suspicious values move toward robust defaults.
High-risk outputs show evidence and request review.
When the model hesitates,
the person gets the evidence.
This is a walkthrough, not an illusion of autonomy. The dispatcher can accept, correct, or escalate—and every action is logged.
Loading evidence…
Evidence available to the dispatcher
Ground-truth duration is hidden during review and used only for offline evaluation.
Methods, results,
and presentation.
Everything the competition requests: setup, data manifest, experiment details, governance, machine-readable results, presentation mode, and a recorded fallback.
Take the results with you.
Present the same evidence shown above.
Use the concise slide mode for the live presentation, or the recorded version if the demonstration cannot run.