> Kept by incident.synthetic@web-summit.dinis, 2026-11-11, 11:53 UTC **Invented person; not user research; never quote as a real reader.** Persona `deadline`: wire reporter in Madrid, 300-word update, 10 minutes, on a 390 px phone for this run (the persona table says laptop; the brief asked for phones). Version seen: v0.1.982. Page height /guide/: 10,638 px (16 screens). ## Path 1. /guide/ first screen (0 px): headline "In force now for Lisbon: RED rain warning, until 18:00 UTC; also orange wind." @170 px, "IPMA's warnings feed, read Wed 11 Nov 11:26 UTC" under it. 5 s. Has his lead sentence. 2. Tap "1 What is happening now" (#now-detail, 807 px): four IPMA levels with quoted IPMA text; government alert situation FACT @1333 px. 20 s. Has warnings + the national measures with a portugal.gov.pt-type source. 3. Scroll to "2 I have a flight" (1794 px): 208 cancelled at Lisbon by 09:20, EVIDENCE via cnnportugal, read 10:34 @1951 px. 10 s. 4. Scroll "3 Getting around" (2451 px): seven operator rows, mostly EVIDENCE, read 00:33 to 06:35 UTC. 30 s. Re-reads the Metro row twice (see Misread). 5. Tap "5 Web Summit" (#websummit, 5979 px): Day 3 "aims to proceed" FACT @6022 px; Day 2 cancelled FACT @6265 px; "Not yet announced" list @6595 px. 25 s. 6. Tap "7 I'm a journalist" (#press, 8688 px): one paragraph, "cite the source, and us for the record" @8784 px. 10 s. No changelog here. 7. Back up, tap "Deeper"/"the timeline" link (1730 px) to /incidents/2026-11-10-storm-charles/timeline.html (28,953 px, 91 rows). Reads top 3 rows. 60 s. Finds "IPMA's warnings unchanged" at 11:28, but the morning would mean scrolling ~15 screens. Total about 2 min 40 s, 4 taps, comfortably inside 10 minutes. ## In 10 seconds Red rain in Lisbon until 18:00 UTC, orange wind; IPMA is the source, read 11:26 UTC; the site is not a warning service. ## In 1 minute All IPMA levels for Lisbon with IPMA's own words; nationwide alert situation for 11 Nov (schools, public services, outdoor events); 208 Lisbon cancellations by 09:20 (press); summit Day 2 off, Day 3 "aims to proceed". ## Three things looked for - What stands now, with source and time: **found**. /guide/ 170 px and 807-1650 px; 5 s for the headline, 25 s for the full set; 0-1 taps. Each row has a domain and "read ... UTC". - What changed since this morning: **partly**. Not on /guide/ at all. The timeline (1 tap from 1730 px) has it, newest first, but 28,953 px long; only the top row tells him "IPMA unchanged since 07:16". About 90 s, 2 taps, and he still has no "since 06:00" summary. - Web Summit status: **found**. /guide/#websummit, 6022 px and 6265 px; 15 s; 1 tap. Organiser quotes with published and read times, and a clear "not yet announced" list. ## Misread - Metro row @2651 px: "Metro ... not announced Thursday 12 Nov transport after the storm (Metro, Carris, CP, ferries, bridges) FACT". He first took it as "Metro not running" before seeing it means Thursday's plans are not announced. Today's Metro status is not in the row at all. - "Parks, gardens, municipal culture (Lisbon city) running" @4898 px carries the tunnels sentence; he reads "parks running", which contradicts the alert situation's park closures @1333 px. Looks like a mis-joined row. - Day 3 tagged "running" @6022 px while the quote says only "aims to proceed ... further updates". He nearly wrote "Day 3 confirmed". - "published" vs "read": clear where both appear (Web Summit). On operator rows only "read" is shown, so "read Tue 10 Nov 23:33" for the CP row felt stale; he could not tell when CP said it. - FACT vs EVIDENCE understood from the "How this guide works" box, but that box is at 9396 px, at the very bottom; he guessed the meaning from context before then. - "not stated" vs "closed": understood (the sentence @5265 px says it plainly). ## Wanted, not found - A "changed since morning" line or list on /guide/ (or #press): e.g. the last change time for each warning and decision. - Today's Metro and Carris status (Carris "not stated"). - A ready citation line for the site ("PrompTugal Storm Charles, read HH:MM UTC") in #press; it only links elsewhere. - Ground totals from an authority (occurrences): only on the timeline, via the press. ## Reads like advice? Mostly no on /guide/. Borderline: - "go to the operator before you set off" @2547 px (a referral, but phrased as an instruction to travel). - "(12:00 to 15:00 forecast: heavy rain, strong wind)" @2769 px inside the CP row: a forecast in the operator's (press-reported) words, not attributed inside the parenthesis. - On the timeline (1 tap): HYPOTHESIS "the centre may pass south of Lisbon ... will settle it. Our analysis, not a forecast" @1491-1539 px. Labelled, but it is a track forecast in substance and sits near the top of the page a journalist will quote from. ## Words not understood "Panel"; "CAP" and "communiqué no. 2" on the timeline; "signal" / "official" / "team" kinds; "Deeper". ## What would make them act File now: the headline, the alert situation and the summit rows are citable with source and time. He would cite IPMA, the government and websummit.com directly, not the site, and come back at 18:00 UTC for the red rain's end. ## Score 4 / 5: what stands now and the summit are fast and citable; "since this morning" is missing from the guide and two rows would have put errors in his copy. ## Findings - costly | No "what changed since morning" on /guide/ | timeline 1 tap from 1730 px, 28,953 px long; 90 s and no summary | Add a short "Changed today (UTC)" list at the top of #press or under section 1, generated from decision rows. - costly | Mis-joined row: "Parks, gardens, municipal culture" shows the tunnels text, status "running" | /guide/ 4898 px | Fix the row mapping; show "not stated" if no park source. - costly | Day 3 status "running" overstates "aims to proceed" | /guide/ 6022 px | Use "planned" / "aims to proceed" status, not "running". - minor | Metro row reads as "not announced" about today | /guide/ 2651 px | Put today's Metro status in the row; move the Thursday line to the Thursday note only. - minor | Operator rows show only time read, not time published | /guide/ 2547-3700 px | Add "published" where known, as Web Summit rows do. - minor | CP row contains an unattributed "forecast" | /guide/ 2769 px | Attribute in-row ("CP/press: ...") or drop the parenthesis. - minor | Labels explained only at the bottom | 9396 px | One-line label key under the headline box. - held | Timeline hypothesis on the storm track near the top | timeline 1491 px | Editorial call for the meteorologist/conductor; labelled correctly.