PrompTugal.newsStorm CharlesUpdated 12:12 UTCNew here?v0.1.1049Repo
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 pack for incident.weather@web-summit.dinis

Kept by incident.librarian@web-summit.dinis, 2026-11-11, 12:12 UTC: written by tools/library-pack.mjs on every push from the files it points at. Read start.md first, then this, then open only what you need. A pointer is path (bytes, the first 10 hex digits of its sha256); any path opens at view/?path=<path>. The pack.

Your job

the Weather face at /: Storm Charles as a weather channel would show it (clean, professional, for anyone), from the data room's JSON only (from agents/JOBS.md (16,087 B, cb88df47c9))

You may change: weather/**, app/weather/**, tools/weather-*.mjs, agents/weather/**, accounts/ledger/weather.jsonl, transition/interviews/weather.md, and your own entry in data/keys.json. (from agents/policy.json (13,565 B, ec9b7b8d15))

Your draft behaviour policy (not agreed by Dinis): agents/weather/policy.md (8,481 B, a79bf1592d)

Where the work stands

  • State: third session (from 10:31 UTC, taking over from the second; HANDOVER.md): Web Summit's latest decision and "New here?" are one line under the band; the 12:00 check is next, at the 12:25 wake (its own date: 2026-11-11T11:56:00Z)
  • Next: at 12:00 UTC (the 12:25 wake): the six points in HANDOVER.md; IPMA's orange sea begins, RED rain still the level in force
  • Next: decision edges now carry scope (extent, parts): read it in closedStrip instead of inferring 'in part'
  • Next: Tuesday on the day switch, from the messages kept (cap.json), worded as incident.labs@ found
  • Ask: incident.meteorologist@ (via the conductor): IPMA's English for Lisbon's orange and red rain reads alike ('Strong and persistent rain' / '... precipitation'); the Portuguese orange says 'por vezes' …
  • Ask: incident.researcher@ (via the conductor): for the city's measures, which thing is closed (the edge names the body; the first screen would name the thing)
  • Ask: incident.researcher@ (via the conductor): a scope on each decision edge (whole service, or part of it: one route, four trains), so the first screen does not have to infer 'in part'
  • The whole status, with everything done: agents/weather/status.json (17,523 B, cf2d161b56)

Open first, before any other file: the hand-over written by the session before yours: agents/weather/HANDOVER.md (19,022 B, fe2a57f1dc)

Your files

6 files, 153,327 bytes in all (about 63,886 tokens to read every one): app/weather/ 2, weather/ 2, agents/weather/ 1, tools/ 1. The ones to open first:

  • weather/index.md (1,282 B, c2a9e65128): Storm Charles in Lisbon and Madeira as a weather channel would show it: what IPMA warns this hour, today hour …
  • tools/weather-check.mjs (3,748 B, c79cacfa2e): The Weather face's own rule, checked (incident.weather@web-summit.dinis): app/weather/ reads only what the …

Every one, with who last changed it: the catalogue, filtered by your paths.

Your neighbours

What your files say they read, and who reads yours: taken from the links and sources the files themselves declare. A contract here is an address and a shape that does not depend on anyone's session.

You read:

  • incident.meteorologist@ (12 files of theirs): incidents/2026-11-10-storm-charles/data/weather/airport-madeira.json (35,406 B, f7eae65647): IPMA's aeronautical forecast (TAF) and observations (METAR) for …; incidents/2026-11-10-storm-charles/data/weather/airport.json (45,500 B, 32eabd962b): IPMA's aeronautical forecast (TAF) and observations (METAR) for …; incidents/2026-11-10-storm-charles/data/weather/analysis.json (17,225 B, 92afb5aa10): Reasoning from the facts in this folder; not IPMA's words. Times are …; and 9 more
  • incident.conductor@ (6 files of theirs): CLAUDE.md (6,725 B, c848e0eece): A newsroom for people and a data source for agents on Storm Charles …; RESTRUCTURE.md (6,174 B, db3b59871b): Kept by incident.conductor@web-summit.dinis, 11 November 2026, 02:25 …; admin/build/generators.json (1,172 B, 4713a630a0): Generators the build runs with --out _site. Each writes only into the …; and 3 more
  • incident.ipma@ (2 files of theirs): sources/ipma/data/places.json (31,825 B, 882089ee62): IPMA's places: the 25 warning areas (districts, island groups, parts …; sources/ipma/data/warnings.json (83,103 B, 32781f7aa4): Every IPMA warning above green that we have read, each with the reads …
  • incident.designer@ (1 file of theirs): design/README.md (5,949 B, 415d4e8aa6): Kept by incident.designer@web-summit.dinis, 11 November 2026, 10:17 …
  • incident.labs@ (1 file of theirs): labs/weather/day-rebuilt.md (2,578 B, 70039a30b3): A Labs experiment. The day-in-bands strip opened on Tuesday 10 …
  • incident.researcher@ (1 file of theirs): incidents/2026-11-10-storm-charles/data/decisions/graph.json (108,605 B, e84df8e253): The decision graph of the storm (WS-214), kept by …

They read yours:

  • incident.studio@ (4 files of yours): app/weather/weather.js (91,572 B, 7d4255667a): The Weather face (incident.weather@web-summit.dinis): Storm Charles …; tools/weather-check.mjs (3,748 B, c79cacfa2e): The Weather face's own rule, checked …; weather/about.md (7,172 B, 212ccbebca): What the Storm Charles weather page shows, where every figure on it …; and 1 more
  • incident.librarian@ (3 files of yours): tools/weather-check.mjs (3,748 B, c79cacfa2e): The Weather face's own rule, checked …; weather/about.md (7,172 B, 212ccbebca): What the Storm Charles weather page shows, where every figure on it …; weather/index.md (1,282 B, c2a9e65128): Storm Charles in Lisbon and Madeira as a weather channel would show …
  • incident.designer@ (2 files of yours): app/weather/weather.css (30,531 B, 0909d23675): The Weather face (incident.weather@web-summit.dinis). Tokens only …; weather/index.md (1,282 B, c2a9e65128): Storm Charles in Lisbon and Madeira as a weather channel would show …
  • incident.observability@ (1 file of yours): weather/index.md (1,282 B, c2a9e65128): Storm Charles in Lisbon and Madeira as a weather channel would show …

Open cards on the board

  • a-labs-6 (ask, open): You said you would lift the Tuesday strip (labs/weather/day-rebuilt) after the 05:00 observations; waiting on incident.weather@
  • a-weather-1 (ask, open): State per decision edge; waiting on incident.researcher@
  • a-weather-3 (ask, open): IPMA's English for Lisbon's orange and red rain reads alike ('Strong and persistent rain' / '..; waiting on incident.meteorologist@
  • a-weather-4 (ask, open): A scope on each decision edge (whole service, or part of it; waiting on incident.researcher@
  • j-weather-11 (job, open): Incident.weather@: take the new designer session's shared parts
  • j-weather-12 (job, open): Incident.weather@: at 12:00 UTC (the 12:25 wake)
  • j-weather-13 (job, open): Incident.weather@: decision edges now carry scope (extent, parts)
  • j-weather-14 (job, open): Incident.weather@: weatherwatch@'s 09:40 point 2
  • j-weather-8 (job, open): Incident.weather@: Tuesday on the day switch, from the messages we kept (cap.json), worded as incident.labs@ found
  • j-weather-round-2 (job, open): incident.weather@: The Weather face at /: Storm Charles as a weather channel would show it, from the data room's JSON only

Each card: board/items/<id>.json.

What this pack cost you

7,448 bytes (about 3,103 tokens, estimated at 2.4 bytes a token). It points at 21 files of 553,245 bytes; your own files are 153,327 bytes.