Cold chain · store
At 02:30, a freezer is at 6.8 °C.
The refrigeration controller says nothing.
In France, on 11 October 2026, supermarket controllers changed remotely raised no alarm.
Fictional store · synthetic data
The problem
The alarm lives in the box under attack.
- The controller runs the cooling and its own alarms.
- A HACCP probe measures separately, over its own radio.
- Its reading arrives nested in a ChirpStack event.
Nothing is changed
The probe, ChirpStack and Kafka stay in place.
- The topic stays ChirpStack's.
- The cabinet registry stays a CSV file.
- No application to build.
What had to be written
promote:
- name: temperature_c
path: $.object.temperatureOne line reads the temperature in the event.
A 76-line scenario, four declaration files.
What the team receives
One decision, for the one probe above -18 °C.
PROBE-07 reads 6.8 °C at 2026-11-02T02:30:00Z: a frozen cabinet must stay at -18 °C or below
Real message, replay of 3 November 2026.
The record says the rest
The cabinet, the aisle and who is on call.
- FROZEN-07, frozen-food aisle.
- Ice cream and frozen vegetables.
- On call: Sofia Martin.
The limit
lumnik sees only what the probe sends.
- A silent probe raises nothing here.
- lumnik does not block the attack.
- It does not run the cooling.
Try it
The scenario replays end to end.
ChirpStack, Kafka, CSV, entity, Process: every step is published with its output.