The pack for incident.sources@web-summit.dinis
Kept by incident.librarian@web-summit.dinis, 2026-11-11, 12:12 UTC: written by
tools/library-pack.mjson every push from the files it points at. Read start.md first, then this, then open only what you need. A pointer ispath(bytes, the first 10 hex digits of its sha256); any path opens atview/?path=<path>. The pack.
Your job
a section per source body, MeteoAlarm first: its feeds browsed, its API mapped, what changed over time, the licence (from agents/JOBS.md (16,087 B, cb88df47c9))
You may change: sources/**, app/sources/**, tools/source-*.mjs, agents/sources/**, accounts/ledger/sources.jsonl, transition/interviews/sources.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/sources/policy.md (8,450 B, fb21b8df35)
Where the work stands
- State: active: hourly rounds; MeteoAlarm's Portugal feed last changed at the 08:24 read (IPMA's messages sent 07:16:30 on 11 Nov) (its own date: 2026-11-11T11:28:00Z)
- Next: the government portal's section (communiqués, the alert declaration's address); ANEPC's occurrences map mapped (what the ArcGIS application calls)
- Next: MeteoAlarm: Spain's feed beside Portugal's
- Next: register the most-cited of the hosts not yet in the register
- Ask: Dinis: the read key of vault op6i3jfq (public by design; it lets the site's pages read the full feed copies) is not published: this session's permission check refused printing it from the creation …
- Ask: Dinis: Web Summit's terms (updated 27 October 2026, sections 48.2 and 52.1) forbid any 'bot, script ... scraper, artificial intelligence agent or other automated means' on its websites and apps, and …
- Ask: Dinis: MeteoAlarm's archive (where Madeira's Tuesday-afternoon warnings can be looked for) needs a key: a free MeteoGate account and API key (devportal.meteogate.eu), or a token asked of MeteoAlarm …
- Ask: incident.entities@: node ids are in sources/sources.json (
node: source:<id>) and sources/meteoalarm/source.json (nodes); tell me if you want another shape. - The whole status, with everything done:
agents/sources/status.json(9,146 B, 1a4e465e4b)
Open first, before any other file: the hand-over written by the session before yours: agents/sources/HANDOVER.md (4,336 B, ea12b02220)
Your files
18 files, 367,706 bytes in all (about 153,211 tokens to read every one): sources/meteoalarm/ 9, sources/ 3, tools/ 3, app/sources/ 2, agents/sources/ 1. The ones to open first:
sources/registry.json(34,196 B, 00312866ef): The hand-kept register of every outside body this site takes data from or cites: who they are (bodies only), …sources/README.md(19,465 B, 25301876dd): Kept by incident.sources@web-summit.dinis, 11 November 2026, 11:28 UTCsources/sources.json(68,614 B, 8212f6a835): Every outside body this site takes data from or cites, official bodies first. For each: who (bodies only, no …tools/source-meteoalarm.mjs(17,148 B, 71881f7c62): The MeteoAlarm reader: one polite read of a country's warning feed, kept as a dated record with a compact …tools/source-index.mjs(12,390 B, 2c526f0984): The index of sources: from the hand-kept register (sources/registry.json) and what the site already cites, …tools/source-pages.mjs(4,945 B, f894cf1222): A small page and a source.json for every body in the register that has no folder of its own yet, so each body …sources/meteoalarm/README.md(8,345 B, a56d1d39bd): Kept by incident.sources@web-summit.dinis, 11 November 2026, 02:30 UTCsources/meteoalarm/dataset.json(2,218 B, a5179f0d75): Where the full copies of MeteoAlarm's feeds are kept: a data vault (SG/Send, made with sgit), in the latest/ …sources/meteoalarm/source.json(8,280 B, b4d41f4955): source.jsonsources/meteoalarm/api-map.json(12,740 B, d84bbd54b3): A map of what MeteoAlarm publishes for machines, made by following its own pages and links: every address …
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.conductor@ (3 files of theirs):
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 …;incidents/2026-11-10-storm-charles/timeline.md(57,731 B, eeef690c18): Newest first (from 18:58, at the incident conductor's takeover). … - incident.weatherwatch@ (2 files of theirs):
research/weather-sites/terms.json(54,510 B, 79e2d0f7cc): Each site's own terms or licence page (the link printed on the site), …;research/weather-sites/meteoalarm-check.json(4,355 B, 8d16ffece1): Does this site's use of IPMA's warnings meet MeteoAlarm's Terms and … - incident.archivist@ (1 file of theirs):
data/vaults.json(2,638 B, 0e2d500a57): The vaults this site reads or keeps evidence in (SG/Send, encrypted … - incident.meteorology@ (1 file of theirs):
meteorology/licences.json(28,329 B, 0748f96df2): Licences as data: for each source in the meteorology lineage, the … - incident.wikipedia@ (1 file of theirs):
research/wikipedia/README.md(8,868 B, f19d1ce6c9): Every Wikipedia page on Storm Charles, in every language that has … - incident.meteorologist@ (1 file of theirs):
incidents/2026-11-10-storm-charles/data/weather/cap.json(46,620 B, 24ccddf354): IPMA's warnings for the Lisbon district as CAP messages (Common …
They read yours:
- incident.librarian@ (3 files of yours):
sources/README.md(19,465 B, 25301876dd): Kept by incident.sources@web-summit.dinis, 11 November 2026, 11:28 UTC;sources/meteoalarm/README.md(8,345 B, a56d1d39bd): Kept by incident.sources@web-summit.dinis, 11 November 2026, 02:30 UTC;sources/registry.json(34,196 B, 00312866ef): The hand-kept register of every outside body this site takes data … - incident.conductor@ (1 file of yours):
sources/meteoalarm/data/portugal/diffs/2026/11/11/082450.json(12,186 B, d2235592d6): What changed in MeteoAlarm's portugal feed between two reads of ours. … - incident.archivist@ (1 file of yours):
sources/meteoalarm/data/portugal/reads.json(8,448 B, 120451a6ee): Every read of MeteoAlarm's portugal feed by … - incident.meteorology@ (1 file of yours):
sources/registry.json(34,196 B, 00312866ef): The hand-kept register of every outside body this site takes data …
Open cards on the board
a-graph-3(ask, open): Sources/wikipedia/ has no page in the build (45 of 46 bodies do), so one registered-as link leads nowhere; waiting on incident.sources@a-meteoalarm-archive-key(ask, open): A key for MeteoAlarm's archive (an account in someone's name); waiting on Dinisa-sources-2(ask, open): Node ids are in sources/sources.json (node; waiting on incident.entities@a-sources-3(ask, open): One line for SECURITY.md section e, from the first handover; waiting on incident.identity@a-sources-4(ask, open): The read key of vault op6i3jfq (public by design; waiting on Dinisj-sources-11(job, open): Incident.sources@: the government portal's section (communiqués, the alert declaration's address)j-sources-12(job, open): Incident.sources@: MeteoAlarmj-sources-13(job, open): Incident.sources@: the read key of vault op6i3jfq into data/vaults.json (incident.archivist@'s file)j-sources-9(job, open): Incident.sources@: register the most-cited of the 142 hosts not yet in the registerj-sources-round-2(job, open): incident.sources@: A section per source body, MeteoAlarm first
Each card: board/items/<id>.json.
What this pack cost you
8,110 bytes (about 3,379 tokens, estimated at 2.4 bytes a token). It points at 26 files of 470,956 bytes; your own files are 367,706 bytes.