Six organisations move one temperature-sensitive vaccine consignment from Melbourne to a Sydney hospital. Every custody handover, sensor read and certificate lands on a shared tamper-evident ledger. A decision-support system scores the risk from that evidence - but the ledger can only prove what was recorded, not what is true. You make the final call.
1 · Watch the ledgerEvents stream in from each organisation, signed and chained.
2 · Read the DSSWeighted risk factors and a confidence level, assembled from the evidence.
3 · DecideAccept, inspect, hold, reject or quarantine. You may override the DSS.
4 · Face the truthThe hidden physical reality decides the outcome. Immutable data can still be wrong data.
Cold lane · Melbourne to Westmead
Briefing
100Trust & compliance
0Patients exposed
$0Intervention cost
0Game score
Cold-chain telemetry (on ledger)
Chain of custody
Risk factors the DSS can prove
What the DSS cannot prove
Blockchain guarantees the record has not been changed since it was written. It cannot guarantee the sensor was calibrated, the typist was honest, or the box on the truck matches the box on the ledger.
Make a decision to see its consequences.
Six-consignment trail
About this game
The concept
A blockchain gives independent organisations one shared, append-only history: signed events that no single party can quietly rewrite. A decision-support system turns that history into a risk score and a recommendation - the decision itself stays human.
How it works
Each scenario streams real ledger events. The DSS applies weighted, explainable rules - temperature exposure, custody gaps, signature and certificate checks, recall matches - and reports risk with a confidence level based on evidence coverage.
Winning strategy
Follow the evidence, not the recommendation. The DSS is well-calibrated when evidence is complete - but at least one consignment proves that an immutable record of a faulty sensor is still faulty data. Cheap is not always safe; safe is not always fast.