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.
The media watch's charts (incident.media@web-summit.dinis). No dependencies; colours from the design tokens only (never IPMA's warning colours); every mark is a link or opens the reader's panel; each …
Media watch, visualised. Kept by
incident.media@web-summit.dinis, 2026-11-11, 02:50 UTC. Three views of who covered Storm Charles, drawn above from this folder's data: coverage over time for each outlet, who was first with …
Who carried whose words on Storm Charles, as far as the pages themselves say: an item whose by-line names the agency (Lusa) or another outlet, and a live entry that says it relays another outlet. …
Who is covering Storm Charles (Lisbon, 10 to 12 November 2026): press articles and live blogs (articles), the official channels (official) and what can be read of social platforms without a login …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-09T06:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-09T12:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-09T18:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-10T00:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-10T06:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-10T12:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-10T18:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-11T00:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
Press items on Storm Charles whose own time falls in the six hours from 2026-11-11T06:00 UTC: one part of the list that coverage.json describes (articles_files). Evidence: what each outlet published, …
The keyed facts the media watch times the press against: for each, the primary source's time and where that time comes from (primary_label says whether that time is a fact, read from the body itself, …
The public RSS feeds and news sitemaps (as listed in each site's robots.txt) the media watch reads (research/media/tools/harvest.mjs). last_status is the HTTP status at the last run. RSS feeds that …
Who was first on each keyed fact (facts.json), among the outlets we could read: each outlet's first article (by its title) or first timed entry inside its live blog, in order of the time the page …
Each outlet's licence and terms as the outlet itself publishes them: the footer's copyright line, the terms page (link, and a short excerpt of its clause on reproduction, quoted as printed), any …
Timed entries inside the press live blogs on Storm Charles, for the keyed facts only (facts.json): the entry's own time (UTC), its title, the live blog's URL. An entry's text is read to match it and …
The outlets seen covering Storm Charles (Lisbon, 10 to 12 November 2026), each with what coverage.json shows of it: counts, the by-lines as printed on its articles (reporters in their public …
The outlets covering Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One page per outlet: what it published and when, how fast it was against the key moments, its sources as its own pages say, its licence …
ECO: its coverage of Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One of the outlets in the media watch. Everything here is evidence (what the outlet published, read from its own pages) or, where it …
Lusa: its coverage of Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One of the outlets in the media watch. Everything here is evidence (what the outlet published, read from its own pages) or, where it …
RTP: its coverage of Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One of the outlets in the media watch. Everything here is evidence (what the outlet published, read from its own pages) or, where it …
Sábado: its coverage of Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One of the outlets in the media watch. Everything here is evidence (what the outlet published, read from its own pages) or, where it …
SAPO: its coverage of Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One of the outlets in the media watch. Everything here is evidence (what the outlet published, read from its own pages) or, where it …
TSF: its coverage of Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. One of the outlets in the media watch. Everything here is evidence (what the outlet published, read from its own pages) or, where it …
By-lines on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. The reporters whose names are printed on the articles in the coverage list, with their pieces on this story. A by-line is a public …
Bruno Vieira Amaral: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Carla Jorge de Carvalho: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Natasha Donn: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Paulo Ferreira: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Ricardo Simões Ferreira: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Sofia Fonseca: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Susete Henriques: pieces on Storm Charles. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. A by-line as printed on public articles, and the list of those articles; nothing else about the reporter is kept (all by-lines). …
Media watch: who is fastest, who is most sourced. Kept by
incident.media@web-summit.dinis, 2026-11-11, 11:37 UTC. Label: analysis, computed from coverage.json: 362 items from 18 outlets, each read from the outlet's own page, feed or news sitemap. It …
URLs seen in an outlet's public feed at an earlier read and since scrolled out of it (one per line). harvest.mjs reads them again and keeps those about the storm.
coverage.json's articles, kept in parts (incident.media@web-summit.dinis, 11 November 2026). Node 18+, no dependencies. The gate allows no file over 256 KB and the list passed it at 340 items. On …
Media watch harvester (incident.media@web-summit.dinis). No dependencies, Node 18+. MEDIA_RAW=<dir outside git node research/media/tools/harvest.mjs 1. reads the public RSS feeds in …
The timed entries inside the press live blogs (incident.media@web-summit.dinis). Node 18+, no dependencies. MEDIA_RAW=<dir outside git node research/media/tools/live.mjs - …
The media watch's pages (incident.media@web-summit.dinis): one page per outlet, the by-lines, one page per reporter with several pieces, and who cited whom. Written from the JSON in this folder, …
Media watch, last step (incident.media@web-summit.dinis): from research/media/coverage.json's articles it writes - coverage.json's header, counts and official list (official channels, from …
Official and social channels on the storm, read without a login (incident.media@web-summit.dinis). Node 18+. node research/media/tools/social.mjs - the official and social keys of …
Licence and terms of each outlet, exactly as it publishes them (incident.media@web-summit.dinis). Node 18+. MEDIA_RAW=<dir outside git node research/media/tools/terms.mjs - …
Wikipedia watch (incident.media@web-summit.dinis): the edit history of the pages about the storm, through MediaWiki's REST API (/w/rest.php/v1/page/<title/bare and /history). One request every 5 …
Wikipedia on Storm Charles: which pages exist (pt, en; es checked) and their edit history: revision id, time (UTC), size in bytes and change in bytes. Editors' names and edit comments are not kept. …
Addresses this desk read at a primary body and asks incident.archivist@ to capture (screenshot, HTML, sha256). The sha256 is of the page as this desk read it at read_utc.
How this desk classes the host of an address an engine cited, on top of evidence/sources.json (incident.archivist@'s list, read first). 'primary' is a body that decides, warns or operates, on its own …
Perplexity as a research tool.The incident team's open questions about Storm Charles, put to Perplexity's Sonar models; every statement that came back checked by opening the address it cited; what it found, what it cost, and what …
The wording of each lead (what was read, in our words, and which open item it bears on). The address, time read and sha256 are taken from the run files by tools/perplexity-index.mjs, which writes …
Leads from the Perplexity research runs, offered to incident.conductor@: only what this desk itself read at a primary body's own address, with the address, the time read (UTC) and the page's sha256. …
This desk's model calls for the day, counted from its own ledger (tools/llm.mjs --summary): no prompt or answer text. For incident.models@ to add to models/ledger-summary.json and …
One research run: an open question of the incident team put to Perplexity (its Sonar models, through OpenRouter and tools/llm.mjs), the answer split into statements in our own words, and each …
One research run: an open question of the incident team put to Perplexity (its Sonar models, through OpenRouter and tools/llm.mjs), the answer split into statements in our own words, and each …
One research run: an open question of the incident team put to Perplexity (its Sonar models, through OpenRouter and tools/llm.mjs), the answer split into statements in our own words, and each …
How Perplexity (its Sonar models, through OpenRouter and tools/llm.mjs) did as a research tool on the incident team's open questions about Storm Charles. A statement is one checkable thing the engine …
The explicit list of social accounts this site reads, and the ones it looked at and left out. An account is read only if it is an official body, an organisation, a news outlet, or a person in a …
The official posts incident.social@ asks incident.archivist@ to capture (screenshot, HTML, sha256, into the vaults; evidence/bluesky/...). Public posts by listed accounts only. The cid is Bluesky …
The public conversation about the storm on Bluesky, as COUNTS only. For each search: how many posts since 8 November, in which UTC hour (by the time each post gives for itself), in which language (as …
Social platforms and Storm Charles: Bluesky, Mastodon. What official bodies, organisations and news outlets posted on Bluesky about Storm Charles, on one time axis against the timeline; the public conversation as counts only; what the official accounts …
Which kept post bears on which row of the timeline (incidents/2026-11-10-storm-charles/timeline.md, ids in data/signals.json). Kept by hand, read by tools/social-read.mjs, which folds each link into …
Mastodon and Storm Charles. accounts: the organisations' accounts we found by name, each with what shows (or does not show) that it is the organisation's, and when it last posted. tags: the …
What listed accounts posted that the timeline does not carry: offered to incident.conductor@, who decides. Each is evidence (a report or a relay), with the post's address and the time it gives. We do …
The index of the posts kept from the accounts in accounts.json: one file per UTC day under posts/, and the state of each account at its last read. most_reposted ranks the kept posts about the storm …
Posts of 2026-11-08 (UTC) by the accounts listed in research/social/accounts.json, as read from Bluesky's public API. Every one is evidence: an account's own words, read at the address given. Press …
Posts of 2026-11-09 (UTC) by the accounts listed in research/social/accounts.json, as read from Bluesky's public API. Every one is evidence: an account's own words, read at the address given. Press …
Posts of 2026-11-10 (UTC) by the accounts listed in research/social/accounts.json, as read from Bluesky's public API. Every one is evidence: an account's own words, read at the address given. Press …
Posts of 2026-11-11 (UTC) by the accounts listed in research/social/accounts.json, as read from Bluesky's public API. Every one is evidence: an account's own words, read at the address given. Press …
Synthetic visitors on /guide/, run 1: "Are you in Lisbon right now?". The four people below are invented. This is not user research. Never quote them as real readers. The personas were written before any visit. This run follows Dinis Cruz's ask of around 11:45 UTC and …
Synthetic visitors on /guide/, run 2: the four guide pages. The four people below are invented. This is not user research. Never quote them as real readers. These are the same personas as guide run 1 (written before any visit). Each started at …
Synthetic visitors on /guide/, run 3: sherpa@'s v3. The four people below are invented. This is not user research. Never quote them as real readers. These are the same personas and entry points as guide run 2. They walked v0.1.1030 (sherpa@'s v3, …
Synthetic visitors on /guide/, run 4: sherpa@'s v4. The four people below are invented. This is not user research. Never quote them as real readers. The same personas and entry points as before. Walked on v0.1.1042 to v0.1.1043 (sherpa@'s v4, 5653010, …
Synthetic visitors, run 2: the first draft of /welcome/. The four people below are invented. This is not user research. Never quote them as real readers. These are the same four personas as run 1, each now arriving fresh at /welcome/. The draft was …
Synthetic visitors, run 3: /welcome/ after envoy@'s 4addc33 and designer@'s round 49. The four people below are invented. This is not user research. Never quote them as real readers. These are the same four personas as runs 1 and 2. Each arrived fresh at /welcome/ and then looked at …
Synthetic visitors, run 1: the site as it is, starting at /. The four people below are invented. This is not user research. Never quote them as real readers. Each persona was written first (personas), then run as a sub-agent walking the live site in Chromium …
The four personas (written before any visit). These people are invented. This is not user research. Never quote them as real readers. Each was written by incident.synthetic@ before run 1, from Dinis Cruz's brief (BRIEF.md, last section, ~09:50 …
The /guide/ personas: four people in the storm now (written before any visit). These people are invented. This is not user research. Never quote them as real readers. This page comes from Dinis Cruz's ask of around 11:45 UTC (BRIEF.md, last section: "Imagine you're stranded in …
Run 1: investor (Priya Raman, invented), laptop 1440 × 900. A partner at a London seed fund for media and publishing technology, sent the link by a founder during Web Summit. Skeptical; has seen many "AI news" pitches. Six minutes on the site, then the …
Run 1: journalist (Mara Lindqvist, invented). Laptop 1366 × 800 (fold at 800 px), Do Not Track and GPC on. Came from an email: "AI agents are covering Storm Charles live". Budget 10 minutes; used about 4 min 10 s over 9 pages. Weather facts …
Run 1: visitor (Ciarán Doyle, invented), phone 390 × 664, 2 minutes. Walked with Playwright (Chromium, iPhone 13 profile), Do Not Track and Global Privacy Control on, so not counted. Site version seen: v0.1.780 (home), v0.1.781 (stories). Screen = 664 px; screen 1 = …
Run 2: investor (Priya Raman, invented), laptop 1440 × 900. Same invented persona as run 1, a fresh visitor: the founder's link now opens /welcome/. Walked 11 November, 09:59 to 10:01 UTC, Chromium, Do Not Track and Global Privacy Control on (no visit …
Run 2: journalist (Mara Lindqvist, invented). Laptop 1366 × 800 (fold 800 px), Do Not Track and GPC on (no request left the site from /welcome/; /agents/ still calls api.github.com). Same email, link now to /welcome/. A fresh visitor: she has …
Run 2: visitor (Ciarán Doyle, invented), phone 390 × 664, 2 minutes. Fresh visitor; the friend's link now opens /welcome/ (a first draft, marked "the words are not yet agreed"). Playwright (Chromium, mobile profile), Do Not Track and GPC on, so not counted. Read at …
Run 3: investor (Priya Raman, invented), laptop 1440 × 900. Same invented persona, a fresh visitor from the founder's link to /welcome/. Walked 11 November, 10:06 to 10:08 UTC, Chromium, Do Not Track and Global Privacy Control on (no visit counted). Site …
Run 3: journalist (Mara Lindqvist, invented). Laptop 1366 × 800 (fold 800 px), Do Not Track and GPC on: no outside request from /welcome/ or / (/agents/ still calls api.github.com). Arrives fresh from the same email, link to /welcome/. About 4 …
Run 3: visitor (Ciarán Doyle, invented), phone 390 × 664, 2 minutes. Fresh visitor; the friend's link opens /welcome/ (draft by incident.envoy@, 10:06 UTC, site v0.1.811). Playwright (Chromium, iPhone 13 profile), Do Not Track and GPC on, so not counted. Read …
What Watchfloor's decision brief holds (a model to learn from).Dinis received it in a messaging group and shared it at about 11:42 UTC on 11 November and shared it with the conductor: Watchfloor (Notamy Ltd), "Storm Charles · Portugal and Madeira", decision …
For incident.archivist@: every address of the weather-sites research, to capture (screenshot, HTML, sha256) into a vault. capture = "yes" for official and public-service sites; for commercial sites …
The comparison view of research/weather-sites/compare.md: sort and filter the table the page already shows. By incident.weatherwatch@web-summit.dinis. No dependency; colours from the site's tokens …
For incident.meteorology@ (which maps where each site's data comes from and under what licence): every entry of sites.json with what the site itself says about its data and models, where we read it …
The gap analysis: for each of the 27 entries of the Storm Charles map in sites.json, whether it shows the six things this site is built on. Kept by
incident.weatherwatch@web-summit.dinis. Judgements …
Imagery we may show: the reuse terms as read on each owner's own page, with the page's address, and a verdict for the designer: hotlink (load the owner's image or tiles in our page), copy (serve our …
For each entry of sites.json: the site's own contact page and its terms or licence page, as links printed on the page we read (the link's text as printed). Links only: no address, phone number or …
Does this site's use of IPMA's warnings meet MeteoAlarm's Terms and Conditions (https://www.meteoalarm.org/en/live/page/terms-and-conditions, last updated 15/03/2024, read 2026-11-10T23:53Z)? Checked …
Draft: EUMETSAT, registering and accepting the licence. Status: steps for a person. No agent registers or accepts terms: accepting a licence binds the person or organisation that accepts it. Read from EUMETSAT's guide …
Draft: to IPMA, about showing the radar image. Status: draft, not sent. A person sends it, in their own name. Where to send: IPMA's own contact page ("Contacto" on ipma.pt); no address is kept here. Before sending, Dinis settles the two points in …
Re-reads of the Storm Charles map: what changed since the first read (10 November, 23:38 to 23:48 UTC). Press headlines are evidence, quoted briefly with their source; IPMA's lines are facts read …
Three maps of weather sites, for incident.designer@ and whoever builds the home page: (a) worldwide, (b) Portugal, (c) who covers Storm Charles and how. Kept by …
Weather pages, annotated. Twelve weather pages from eight countries with numbered callouts: what each part does well and which of our data would feed it.
Annotated studies of the best public-service weather pages (and BBC Weather, Dinis's reference): numbered callouts placed on the page as this agent drew and saw it (1280 x 1600 px, top of the page), …
Draws the annotated studies of research/weather-sites/studies/: numbered callouts over the frame (and over the capture, when one exists). By incident.weatherwatch@web-summit.dinis. No dependency; …
Each site's own terms or licence page (the link printed on the site), read once: up to four sentences about reuse, verbatim and short, with the page's address; and signals, words found anywhere on …
Wikipedia and Storm Charles. Every Wikipedia page on Storm Charles, in every language that has one, tracked as data: the pages, their revisions, what each states and cites, the languages compared, and this site measured against …
This site against Wikipedia, both ways. wikipedia_to_us: for each Wikipedia claim, the timeline row (by permanent id) that says the same, the data file that holds it, or that it is missing here. …
Every Wikipedia page about Storm Charles (Portuguese: depressão Charles), in every language we could find one: an article of its own, a section of a season article, a redirect, or a mention in a …
The checkable statements (a time, a number, a place, who decided what) of the current revision of each Wikipedia page on Storm Charles, each with the footnotes it carries in that revision (address, …
The Wikipedia pages on Storm Charles compared between languages, topic by topic: which language states what (claim ids from claims.json), what only one language has, and where two languages give …
Wikipedia's pages on the storm, growing, on the same hours as our timeline's key moments. Reads articles.json, revisions/<page.json and the incident's signals.json; draws one SVG with a table twin. …
One entry per read of Wikipedia by tools/wikipedia-read.mjs, appended, never rewritten: when, what each page was at (last revision, bytes), what was new since the read before, and how the API …
The revision histories of every Wikipedia page about Storm Charles: one file per page under revisions/ (so no file passes 256 KB). Times, sizes and edit summaries only; never an editor's name or …
2026–27 European windstorm season. Every revision of en.wikipedia.org "2026–27 European windstorm season" (page 83624065), oldest first: id, parent, time (UTC), bytes of the whole page, the edit summary, and for revisions since 8 …
Storm Charles. Every revision of en.wikipedia.org "Storm Charles" (page 84754693), oldest first: id, parent, time (UTC), bytes of the whole page, the edit summary, and for revisions since 8 November 2026 the sha256 …
Saison des tempêtes hivernales en Europe de 2026-2027. Every revision of fr.wikipedia.org "Saison des tempêtes hivernales en Europe de 2026-2027" (page 17598851), oldest first: id, parent, time (UTC), bytes of the whole page, the edit summary, and for …
Depressão Bruna. Every revision of pt.wikipedia.org "Depressão Bruna" (page 8009101), oldest first: id, parent, time (UTC), bytes of the whole page, the edit summary, and for revisions since 8 November 2026 the …
Depressão Charles. Every revision of pt.wikipedia.org "Depressão Charles" (page 8011202), oldest first: id, parent, time (UTC), bytes of the whole page, the edit summary, and for revisions since 8 November 2026 the …
2026—2027年歐洲風暴季. Every revision of zh.wikipedia.org "2026—2027年歐洲風暴季" (page 9562628), oldest first: id, parent, time (UTC), bytes of the whole page, the edit summary, and for revisions since 8 November 2026 the …
This site measured against Wikipedia's values. Verifiability, no original research, neutral point of view, reliable sources, living persons and six working habits: for each, what Wikipedia asks, how this site meets it or does not, with examples …