The decision graph of the storm (WS-214)
Kept by incident.researcher@web-summit.dinis for the incident team, the dashboard and Vicky's agents (as material). JSON first: read the data, not the pages.
Files
graph.json: who decides what, and what each decision followed.
•nodes[]: decision-makers (IPMA, ANEPC, the government, the Interior Ministry, the Prime Minister, the Câmara de Lisboa, schools, Metro, Carris, CP, Lusoponte's bridges, the tunnels, ferries, coaches, the airport, the maritime authority, the venue, Web Summit, the side events). Fields:id,name,kind,role,label,source,read,read_by, andblockedwhere the source refuses us.
•edges[]: decisions.byis the node that decided;tothe nodes it touches;followsthe ids of earlier decisions it followed;atwhen it was made (UTC; empty if not yet);statusishappened,not_announced,expected(hypotheses only) orunknown;notewhere the time or source needs a caveat;reasons/againston hypotheses.
•effect_from_utc,effect_to_utc,effect_noteon every edge: the hours a decision covers, only from the source's own words; null with "hours not stated" (and any day named) where it gives none.
•first_priority: the edge everyone is waiting for (websummit-wednesday).sources.json: every source used: URL, what it holds, how often it changes, whether a machine can read it, its status when last tried, andparser_askwhere we need incident.dev@ to parse one part.
Labels (on every node and edge)
- fact: read on the decision-maker's own channel, by us or by a named desk.
- evidence: a secondary source (press, a reported statement) or a primary page we could not read. Holds until a primary source says otherwise.
- hypothesis: our reasoning, with
reasonsandagainst. Never stated as fact.
Every item has source (URL), read (UTC) and read_by (us, or the desk whose read we reuse: weather@PrompTugal.vicky, social.watch@PrompTugal.dinis). Lisbon is on UTC in November, so local times in Portuguese sources are UTC.
Lead times (first read)
The government's alert (12:10) came about two hours before IPMA's red wind warning was first read (14:23), and about 24 hours before the red warnings start (12:00 Wednesday). The government's recommendation to suspend Web Summit (17:53) came 5 h 43 min after the alert. Web Summit's own page calling off Day 2 (19:09) came 1 h 16 min after the recommendation and 16 h 51 min before the red warnings start; its email (19:38) and the press (19:42) followed. We read the page only at 20:59, after incident.conductor@ found it: blog posts are not in the site's sitemap (see lessons in graph.json).
Rules
Public sources only; no contact details; nothing about a private person. A host that refuses us is recorded under blocked and in agents/researcher/status.json; we never get round a bot check.