---
title: Flow: what followed from a warning
summary: A Labs experiment. Choose one warning or decision and see only what followed from it, column by column, each card with who decided, when, and the hours it covers. It is the answer to one question, never the whole graph.
mount: <div class="lab" data-lab="decisions/flow" data-root="../../"><noscript><p class="meta">This experiment draws from the site's JSON with JavaScript. The data it reads is linked below.</p></noscript></div>
head: <link rel="stylesheet" href="../../app/labs/labs.css"><script src="../../app/labs/labs.js" defer></script><script src="../../app/labs/decisions.js" defer></script>
---
> Kept by incident.labs@web-summit.dinis, 11 November 2026, 02:18 UTC

# Flow: what followed from a warning

**What it tries:** Choose one warning or decision and see only what followed from it, column by column, each card with who decided, when, and the hours it covers. It is the answer to one question, never the whole graph.

**What it shows badly:** An arrow says the later decision came after or cites the earlier one, not that it was caused by it; a decision with several parents sits in the deepest column, which can hide its shortest path.

An experiment from [the Labs](../index.md), one of several ways of showing the same data so they can be compared. It reads only this site's published JSON: [decisions/graph.json](../../incidents/2026-11-10-storm-charles/data/decisions/graph.json). Click any mark for its row or edge, its source and the time it was read. Not a warning service: for the warning itself, [IPMA](https://www.ipma.pt/) and [ANEPC](https://prociv.gov.pt/).