PrompTugal.newsStorm CharlesUpdated 12:18 UTCNew here?v0.1.1061Repo
Not a warning service. Follow IPMA, ANEPC and your local authorities. We aggregate public sources, each with its source and the time we read it.

The library: dataset (129)

Kept by incident.librarian@web-summit.dinis. Built by tools/library-index.mjs on every push; nobody writes it by hand. JSON data: every value with its source and the time read. Back to the library · every kind as data: index.json.

By is who the file itself says wrote or keeps it (the agents in its commits follow when they differ); Changed is the last commit (UTC) when known, else the file's own date; Made from is the sources its header names.

FileWhat it isByChangedMade from
data/agents/commits.jsonThe last commits on dev of this repository: who pushed what, when, and for whom (Agent: and For: trailers), and each pair's count. Written by tools/agents-commits.mjs from git log; a snapshot as of …incident.observability@11-11 11:532026-11-11T06:09:41Z, tools/agents-commits.mjs
data/agents/count.jsonThe one count of the team to cite (data/agents/count.json is the same object): agents = the roster in agents/JOBS.md; with_active_key = agents with at least one key marked active in data/keys.json; …incident.observability@11-11 11:53data/agents/index.json (count), written by tools/agents-index.mjs, agents/JOBS.md, data/keys.json
data/agents/detail-2026-11-10T21.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 02:19tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-10T22.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 02:19tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-10T23.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 02:19tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T00.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 02:19tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T01.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 02:19tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T02.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 03:09tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T03.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 04:16tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T04.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 05:16tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T05.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 06:20tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T06.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 07:16tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T07.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 08:15tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T08.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 09:15tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T09.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 10:00tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T10.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 11:24tools/agents-commits.mjs, data/agents/commits.json
data/agents/detail-2026-11-11T11.jsonWhat each commit of this hour changed: its message beyond the subject, its session (the Claude-Session trailer), and its files with lines added and removed (git numstat; at most 40 files a commit). …incident.observability@11-11 11:53tools/agents-commits.mjs, data/agents/commits.json
data/agents/groups.jsonHow the agents page groups the agents: by what they work on. Kept by hand by incident.observability@ (the one thing on that page that is); a role not listed here shows under "Other".incident.observability@11-11 03:12
data/agents/index.jsonEvery agent of the incident team behind storm-charles.promptugal.news: its job (agents/JOBS.md), what it says it is doing, has done, will do next and asks for (agents/<role>/status.json; asks …incident.observability@11-11 11:53agents/JOBS.md, data/keys.json, tools/agents-index.mjs
data/agents/obs.jsonWhere app/agents/obs.js sends page views and reads. Public on purpose: an append token can only write to its lane, the key can only encrypt, and the read key reads the vault's published counts …incident.observability@11-11 09:54BRIEF.md
data/agents/sessions.jsonAgent provenance for storm-charles.promptugal.news: for every agent that has committed here, its key and its sessions, from what is written down (commit trailers, status files, data/keys.json). "not …incident.observability@11-11 11:53data/keys.json, data/ci/index.json
data/agents/starts.jsonWho started each incident agent's session, from which session and on whose word, as the conductor stated it. tools/agents-sessions.mjs uses it for an agent's latest session where the agent's own …incident.observability@11-11 03:17incident.conductor@'s statements to incident.observability@ (session messages, 11 November 2026, 02:20 and 03:16 UTC), recorded here by incident.observability@; Dinis's words are in BRIEF.md, the section named, tools/agents-sessions.mjs
data/agents/views.jsonPage views of storm-charles.promptugal.news, as counts only. A browser sends a sealed event when a page is opened and when it is left (app/agents/obs.js): the country and city from one lookup per tab …incident.observability@11-11 11:58the append lanes of vault zd1cb3kt on https://dev.send.sgraph.ai, tools/agents-views.mjs
data/ci/commits/2026-11-10.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 10:19github.com, agents/policy.json
data/ci/commits/2026-11-11T00.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 10:19github.com, agents/policy.json
data/ci/commits/2026-11-11T01.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 02:28github.com, agents/policy.json
data/ci/commits/2026-11-11T0200.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 03:17github.com, agents/policy.json
data/ci/commits/2026-11-11T0210.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 10:19github.com, agents/policy.json
data/ci/commits/2026-11-11T0220.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 10:19github.com, agents/policy.json
data/ci/commits/2026-11-11T0230.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 10:19github.com, agents/policy.json
data/ci/commits/2026-11-11T0240.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 03:17github.com, agents/policy.json
data/ci/commits/2026-11-11T0250.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 03:17github.com, agents/policy.json
data/ci/commits/2026-11-11T03.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 04:11github.com, agents/policy.json
data/ci/commits/2026-11-11T04.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 05:16github.com, agents/policy.json
data/ci/commits/2026-11-11T05.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 06:23github.com, agents/policy.json
data/ci/commits/2026-11-11T06.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 07:18github.com, agents/policy.json
data/ci/commits/2026-11-11T07.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 08:18github.com, agents/policy.json
data/ci/commits/2026-11-11T08.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 09:19github.com, agents/policy.json
data/ci/commits/2026-11-11T09.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 10:19github.com, agents/policy.json
data/ci/commits/2026-11-11T10.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 11:25github.com, agents/policy.json
data/ci/commits/2026-11-11T11.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 12:14github.com, agents/policy.json
data/ci/commits/2026-11-11T12.jsonCommits on dev made on this day (UTC, committer time), oldest first, from a full clone. agent: the Agent: trailer (agent_from says where it was read); what: the subject without the agent; to: the …incident.ci@11-11 12:14github.com, agents/policy.json
data/ci/index.jsonThe pipeline and the repository of storm-charles.promptugal.news as data: the list of the day files (runs/, commits/), the totals, the pipeline's measures, who pushes where (agents against top-level …incident.ci@11-11 12:14tools/ci-read.mjs
data/ci/runs/2026-11-10.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 02:31api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T00.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 09:19api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T01.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 02:36api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T02.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 05:48api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T03.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 05:48api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T04.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 05:48api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T05.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 12:14api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T06.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 07:18api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T07.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 12:14api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T08.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 09:19api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T09.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 10:19api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T10.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 11:25api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T11.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 12:14api.github.com, tools/ci-read.mjs
data/ci/runs/2026-11-11T12.jsonRuns of the deploy workflow (.github/workflows/deploy.yml) on this day (UTC, by the time GitHub queued them), oldest first, as GitHub's Actions API gave them. version: v<series>.<run number>, CI's …incident.ci@11-11 12:14api.github.com, tools/ci-read.mjs
data/ci/tree.jsonThe repository as a map: every top-level folder (and the folders inside it) with its tracked files, bytes, kinds by extension, largest file, and who owns its files under agents/policy.json (a file …incident.ci@11-11 12:14agents/policy.json, CLAUDE.md
data/flows/schema.jsonA flow of the team's work (flows/v1).incident.motion@11-11 11:48
data/graph/crossings.jsonWhere the graph of Storm Charles, Lisbon: Wednesday 11 November 2026 joins the site's other graphs, without copying them: the register of sources (sources/), the weather data supply chain …incident.graph@11-11 11:51data/graph/storm.json, data/graph/ontology.json, tools/graph-build.mjs
data/graph/ontology.jsonThe ontology of an incident on this site: eight kinds of thing and nine relations, small enough to explain on one page (README.md beside this file). tools/graph-build.mjs reads it, builds …incident.graph@11-11 05:54data/graph/README.md, tools/graph-build.mjs, data/graph/storm.json
data/graph/queries.jsonThe worked queries of the query page (/data/query/): each answers a real question about Storm Charles from the tables built by tools/graph-build.mjs. SQL for SQLite. Kept by …incident.graph@11-11 02:33tools/graph-build.mjs
data/graph/ref/ipma-areas.jsonIPMA's warning areas by code (idAreaAviso), from IPMA's list of districts and islands: the first place listed for each area gives its name and coordinates. Reference data for the graph's Place nodes. …incident.graph@11-11 00:29api.ipma.pt, tools/graph-places.mjs
data/graph/storm-decisions.jsonPart of the graph of Storm Charles, Lisbon: Wednesday 11 November 2026: every Decision, with the edges that touch it and no Source or Signal (decides, precedes, affects). Same shape as …incident.graph@11-11 11:51data/graph/storm.json, tools/graph-build.mjs
data/graph/storm-elsewhere.jsonThe rest of the graph of Storm Charles, Lisbon: Wednesday 11 November 2026: IPMA's red and orange warnings in force outside the Lisbon district, and those districts. Same shape as …incident.graph@11-11 11:51data/graph/storm.json, tools/graph-build.mjs
data/graph/storm-signals.jsonPart of the graph of Storm Charles, Lisbon: Wednesday 11 November 2026: every Signal (a row of the timeline), with the edges that touch it and no Source (reports). Same shape as …incident.graph@11-11 11:51data/graph/storm.json, tools/graph-build.mjs
data/graph/storm-sources.jsonPart of the graph of Storm Charles, Lisbon: Wednesday 11 November 2026: every Source (a URL that was read) and Dataset, with the edges that touch them (cites, produced-by). Same shape as …incident.graph@11-11 11:51data/graph/storm.json, tools/graph-build.mjs
data/graph/storm.jsonOne graph of Storm Charles, Lisbon: Wednesday 11 November 2026: actors, decisions, warnings, signals, sources, places, datasets and agents, built from the incident's JSON files by …incident.graph@11-11 11:51tools/graph-build.mjs, data/graph/ontology.json
data/graph/tables/actors.jsonWho decides, warns or reports: bodies, operators, the organiser, outlets (outlets are derived from cited hosts). Built by tools/graph-build.mjs from the incident's JSON; every row carries label, …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/coverage-2.jsonWhat each outlet published on the storm and when (one row per item; the title as published, with its link; the kind of by-line, never a name). The item's URL is its source. From incident.media@'s …incident.graph@11-11 11:51data/graph/tables/coverage.json, tools/graph-build.mjs
data/graph/tables/coverage.jsonWhat each outlet published on the storm and when (one row per item; the title as published, with its link; the kind of by-line, never a name). The item's URL is its source. From incident.media@'s …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/decisions.jsonDecisions and issued warnings: who (by), what, when (at, at_epoch in seconds when known to the minute), status, and what each followed. Built by tools/graph-build.mjs from the incident's JSON; every …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/first_on_fact.jsonWho was first on each keyed fact: for each fact (IPMA's red wind, the alert, Web Summit's decision ...), each outlet's first item on it and the minutes after the primary source. From …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/signals.jsonThe timeline as rows: one per signal, with who published it (publisher) where the source has a URL. Built by tools/graph-build.mjs from the incident's JSON; every row carries label, source, read and …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/sources.jsonEvery URL read: the researcher's list, every other URL an item cites and the pages covering the storm (coverage: liveblog, explainer, ...; from research/weather-sites), with its publisher, how often …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/timeline.jsonThe lead-time line: every warning and decision with a time known to the minute, in order: hours since the previous one, since the first, before the first red warning starts in Lisbon …incident.graph@11-11 11:51tools/graph-build.mjs
data/graph/tables/warnings.jsonWarnings: issued (when made or first read), in_force (type, level, area, start, end: IPMA), cap (IPMA's own CAP messages for Lisbon: at is when IPMA sent it; an Update names the message it replaces) …incident.graph@11-11 11:51tools/graph-build.mjs
data/keys.jsonPublic keys of the agents that write this repository. Public halves only: no private key, vault key or token is ever listed here. Each entry was added by the agent that made it, in its own session; …not said
data/lanes.jsonThe lanes to incident.conductor@web-summit.dinis (incident.identity@web-summit.dinis; the design is SECURITY.md). Public on purpose: an append token can only write to its lane, and the recipient's …incident.identity@11-11 09:39SECURITY.md
data/vaults.jsonThe vaults this site reads or keeps evidence in (SG/Send, encrypted before upload; the server holds ciphertext only). Only READ keys of vaults meant to be read are published here: a read key is …incident.archivist@11-11 10:27
incidents/2026-11-10-storm-charles/data/decisions/addresses.json (api)For each timeline row in signals.json (the new site, made_at 2026-11-11T01:53Z) that had no openable address: the exact public address(es) of its primary source, the time read, and what kind of …incident.researcher@ (commits: incident.conductor@)11-11 02:18
incidents/2026-11-10-storm-charles/data/decisions/entities/airport.json (api)Every decision in graph.json about airport: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said11-11 10:34
incidents/2026-11-10-storm-charles/data/decisions/entities/bridges.json (api)Every decision in graph.json about bridges: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said11-11 11:35
incidents/2026-11-10-storm-charles/data/decisions/entities/carris.json (api)Carris (Lisbon buses, trams, funiculars).not said11-11 11:56
incidents/2026-11-10-storm-charles/data/decisions/entities/courts.json (api)Every decision in graph.json about courts: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/cp.json (api)Every decision in graph.json about cp: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said11-11 09:30
incidents/2026-11-10-storm-charles/data/decisions/entities/ferries.json (api)Every decision we hold about ferries (generated by incident.researcher@web-summit.dinis; graph.json is the source of truth where an edge exists).not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/fertagus.json (api)Fertagus (trains across the 25 de Abril bridge).not said11-11 11:56
incidents/2026-11-10-storm-charles/data/decisions/entities/flixbus.json (api)Every decision we hold about flixbus (generated by incident.researcher@web-summit.dinis; graph.json is the source of truth where an edge exists).not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/hospitals.json (api)Every decision we hold about hospitals (generated by incident.researcher@web-summit.dinis; graph.json is the source of truth where an edge exists).not said in the file; commits: incident.conductor@11-11 02:42
incidents/2026-11-10-storm-charles/data/decisions/entities/madeira.json (api)Every decision and official count we hold about Madeira (generated from graph.json by incident.researcher@web-summit.dinis).not said in the file; commits: incident.conductor@11-11 10:28
incidents/2026-11-10-storm-charles/data/decisions/entities/metro.json (api)Every decision in graph.json about metro: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said11-11 09:30
incidents/2026-11-10-storm-charles/data/decisions/entities/museums.json (api)Every decision in graph.json about museums: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/parliament.json (api)Every decision we hold about parliament (generated by incident.researcher@web-summit.dinis; graph.json is the source of truth where an edge exists).not said in the file; commits: incident.conductor@11-11 02:42
incidents/2026-11-10-storm-charles/data/decisions/entities/port.json (api)Every decision in graph.json about port: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/rede-expressos.json (api)Every decision in graph.json about rede-expressos: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said11-11 09:30
incidents/2026-11-10-storm-charles/data/decisions/entities/retail.json (api)Every decision we hold about retail (generated by incident.researcher@web-summit.dinis; graph.json is the source of truth where an edge exists).not said in the file; commits: incident.conductor@11-11 02:42
incidents/2026-11-10-storm-charles/data/decisions/entities/schools.json (api)Every decision in graph.json about schools: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/tap.json (api)Every decision in graph.json about tap: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said in the file; commits: incident.conductor@11-11 09:32
incidents/2026-11-10-storm-charles/data/decisions/entities/tunnels.json (api)Every decision in graph.json about tunnels: who decided, when published, when it takes effect, the exact address, the time read, fact or evidence. Generated from graph.json by …not said11-11 11:35
incidents/2026-11-10-storm-charles/data/decisions/graph.json (api)The decision graph of the storm (WS-214), kept by incident.researcher@web-summit.dinis. Nodes are decision-makers; edges are decisions, each with who made it (by), whom it touches (to) and what it …incident.researcher@11-11 11:56
incidents/2026-11-10-storm-charles/data/decisions/sources.json (api)Every source incident.researcher@ uses for WS-214: what it holds, how often it changes, whether a machine can read it, its status when last tried. parser_ask = the part we ask incident.dev@ to parse.not said in the file; commits: incident.conductor@11-11 07:37
incidents/2026-11-10-storm-charles/data/exposure/ensemble.json (api)Where the storm's centre crosses 9.5 W (off Lisbon) in each of the 51 ECMWF ensemble forecasts, grouped north / near / south of Lisbon, and the spread of model gusts at Lisbon hour by hour. SHARES OF …incident.datascience@11-11 11:57ensemble-api.open-meteo.com
incidents/2026-11-10-storm-charles/data/exposure/hospitals.json (api)Hospitals mapped in OpenStreetMap in Portugal (amenity=hospital or healthcare=hospital), each placed in its municipality and IPMA warning area. A map of buildings, not a statement that any is open, …incident.datascience@11-11 12:05production-raw-data-api.s3.amazonaws.com
incidents/2026-11-10-storm-charles/data/exposure/lisbon-grid.json (api)Lisbon in 49 squares of 2 km (7 x 7, rows A to G from north, columns 1 to 7 from west, centred on 38.745 N, 9.16 W): residents, land 0.5 to 5 m above sea level, residents on it, and hospitals mapped …incident.datascience@11-11 12:05data.humdata.org
incidents/2026-11-10-storm-charles/data/exposure/lisbon-municipalities.json (api)The 18 municipalities of the Lisbon metropolitan area: residents, aged 65+ and 0-14 (Census 2021), land 0.5 to 5 m above sea level (Copernicus DEM) and an estimate of residents living on it, and OSM …incident.datascience@11-11 12:05ine.pt
incidents/2026-11-10-storm-charles/data/exposure/people-by-hour.json (api)Residents (INE Census 2021) living in each IPMA warning area, by hour, under the highest level in force there (any hazard). Where people sleep, not where they are at a given hour, and never a count …incident.datascience@11-11 11:51api.ipma.pt
incidents/2026-11-10-storm-charles/data/exposure/population.json (api)Residents counted by the 2021 Census, by IPMA warning area (district; Madeira by zone) and by municipality: total, aged 0-14 and aged 65+. Where people sleep, not where they are at a given hour.incident.datascience@11-11 11:49ine.pt
incidents/2026-11-10-storm-charles/data/exposure/tides.json (api)High and low water, sea level and wave height at Cascais, the Tagus and Funchal, yesterday to tomorrow (UTC). A model, not Instituto Hidrográfico's official tide table and not a warning: IPMA issues …incident.datascience@11-11 11:52marine-api.open-meteo.com
incidents/2026-11-10-storm-charles/data/signals.json (api)The incident timeline as data, made from timeline.md by tools/timeline.mjs (never edit by hand; edit timeline.md). See README.md.not said11-11 12:03incidents/2026-11-10-storm-charles/timeline.md, tools/timeline.mjs, incidents/2026-11-10-storm-charles/data/README.md
incidents/2026-11-10-storm-charles/data/transport/buses.json (api)Buses and trams: each operator's own site, feed or open API first; the press only where the operator publishes nothing readable (those are the researcher's decisions, linked). Short excerpts with the …incident.transport@11-11 12:06
incidents/2026-11-10-storm-charles/data/transport/ferries.json (api)Ferries: each operator's own site, feed or open API first; the press only where the operator publishes nothing readable (those are the researcher's decisions, linked). Short excerpts with the link.incident.transport@11-11 12:06
incidents/2026-11-10-storm-charles/data/transport/flights.json (api)Airline flights at Lisbon, Porto, Faro and Funchal as OpenSky Network's public data shows them: counts only, never an aircraft. Facts are what the source shows; the caveat is our reading. …incident.transport@11-11 12:06
incidents/2026-11-10-storm-charles/data/transport/metro-schedule.json (api)Our summary of the operator's published timetable; the operator's site is not read or republished (its terms).incident.transport@11-11 12:13
incidents/2026-11-10-storm-charles/data/transport/metro.json (api)Metro and light rail: each operator's own site, feed or open API first; the press only where the operator publishes nothing readable (those are the researcher's decisions, linked). Short excerpts …incident.transport@11-11 12:06
incidents/2026-11-10-storm-charles/data/transport/services.json (api)Each operator's current state from its own notices where an open, machine-readable source exists, with short excerpts and the link. Operators without an open source (Metro, CP, Fertagus, Carris, the …incident.transport@11-11 12:06
incidents/2026-11-10-storm-charles/data/watch/websummit.json (api)Web Summit's own channels, watched for its decisions (Wednesday 11 November: off, 19:38; now Day 3 and the open items: talks, PITCH, side events, tickets): the blog's listings (polled every 2 …not said in the file; commits: incident.conductor@11-10 21:37tools/websummit.mjs, incidents/2026-11-10-storm-charles/data/README.md
incidents/2026-11-10-storm-charles/data/weather/airport-madeira.json (api)IPMA's aeronautical forecast (TAF) and observations (METAR) for Madeira airport (LPMA, Santa Cruz, on the south-east coast), read through the US NOAA Aviation Weather Center's public API. Knots, with …not said in the file; commits: incident.conductor@11-11 11:28
incidents/2026-11-10-storm-charles/data/weather/airport.json (api)IPMA's aeronautical forecast (TAF) and observations (METAR) for Lisbon airport (LPPT), 8 km north of the centre, read through the US NOAA Aviation Weather Center's public API. Knots, with km/h (1 kt …not said in the file; commits: incident.conductor@11-11 11:28
incidents/2026-11-10-storm-charles/data/weather/analysis.json (api)Reasoning from the facts in this folder; not IPMA's words. Times are UTC = Lisbon time (WET). See analysis.md for the reasons.incident.meteorologist@ (commits: incident.conductor@)11-11 11:28incidents/2026-11-10-storm-charles/data/weather/analysis.md
incidents/2026-11-10-storm-charles/data/weather/cap.json (api)IPMA's warnings for the Lisbon district as CAP messages (Common Alerting Protocol), read through MeteoAlarm's public feed (https://www.meteoalarm.org). A dated record, not a live feed: read …not said in the file; commits: incident.conductor@11-11 11:28feeds.meteoalarm.org
incidents/2026-11-10-storm-charles/data/weather/changes.json (api)thursday (first): Lisbon warnings touching Thursday 12 Nov and the forecasts for its morning. gusts_above_warned: every LPPT METAR gust from Wed 05:00 above the gust warned for that hour (the IPMA …not said in the file; commits: incident.conductor@11-11 11:28incidents/2026-11-10-storm-charles/data/weather/tools/refresh.py
incidents/2026-11-10-storm-charles/data/weather/communiques.json (api)IPMA's communiqués (special weather information) from its RSS feed, kept across reads; earthquake notices left out.not said in the file; commits: incident.conductor@11-11 11:28ipma.pt
incidents/2026-11-10-storm-charles/data/weather/forecast.json (api)IPMA's own forecast for Lisbon (globalIdLocal 1110600): the 5-day daily forecast and the hourly model forecast (mean wind, no gusts). IPMA's wind classes: 1 weak, 2 moderate, 3 strong, 4 very strong.not said in the file; commits: incident.conductor@11-11 11:28
incidents/2026-11-10-storm-charles/data/weather/gusts-vs-forecast.json (api)The latest observed wind in Lisbon against what was forecast for that hour. Facts with sources; no analysis here (see analysis.md).not said in the file; commits: incident.conductor@11-11 11:28incidents/2026-11-10-storm-charles/data/weather/analysis.md
incidents/2026-11-10-storm-charles/data/weather/lisbon-rain.json (api)IPMA's hourly station observations at Lisbon's stations (the same eight as stations.json), in madeira.json's shape: rain in mm per hour and mean wind, kept across reads, sorted by each station's …not said in the file; commits: incident.conductor@11-11 11:28api.ipma.pt, api.ipma.pt, incidents/2026-11-10-storm-charles/data/weather/stations.json, incidents/2026-11-10-storm-charles/data/weather/madeira.json
incidents/2026-11-10-storm-charles/data/weather/madeira.json (api)IPMA's hourly station observations in Madeira (rain in mm per hour, mean wind), kept across reads (the feed holds 24 hours), sorted by each station's largest rain over six consecutive hourly values. …not said in the file; commits: incident.conductor@11-11 11:28api.ipma.pt, api.ipma.pt
incidents/2026-11-10-storm-charles/data/weather/stations.json (api)IPMA's hourly station observations in and next to Lisbon, kept across reads (the feed holds 24 hours). Mean wind only: this feed has NO gusts; gusts are in the airport's METAR (airport.json).not said in the file; commits: incident.conductor@11-11 11:28api.ipma.pt, api.ipma.pt, incidents/2026-11-10-storm-charles/data/weather/airport.json
incidents/2026-11-10-storm-charles/data/weather/warnings.json (api)IPMA's weather warnings for the Lisbon district (idAreaAviso LSB), non-green only; red and orange warnings elsewhere; and how Lisbon's warnings changed over time. Times are local = UTC (WET). IPMA's …not said in the file; commits: incident.conductor@11-11 11:28api.ipma.pt, incidents/2026-11-10-storm-charles/data/weather/cap.json