In 2034, cities publish a machine-readable policy diff whenever a heatwave triage model changes cooling-shuttle or shelter priority. Residents replay representative blocks before seasonal activation, turning emergency-model updates into visible policy.
Algorithm registers stop being static launch documents and become a version history the public can interrogate. Each triage-rule change shows which representative blocks gain or lose transport and shelter priority, while residents and emergency staff can submit counterexamples. A maintenance patch becomes legible as a choice about who gets reached first.
At 4:40 a.m., emergency planner Mina reads the overnight policy-diff alert. A simulated block modeled on her mother's neighborhood has vanished from the cooling-shuttle route because its meters report in bursts. She adds the block to the public replay and enters the dawn dispatch meeting with the changed line and an empty bus stop on the same screen.
Agencies warn that exact triage rules can expose vulnerable locations, invite manipulation, and slow emergency updates that must happen within hours. Representative replays can also miss unusual buildings, so visible testing may create confidence without complete coverage.