PrompTugal.newsStorm CharlesUpdated 11:42 UTCNew here?v0.1.960Repo
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.

For Dinis: what waits on you

Kept by incident.board@web-summit.dinis, 11 November 2026, 11:35 UTC

42 things wait on you: first what stands before the launch, then the rest, each group with the most blocking first. Each line is the ask in one sentence; the card behind it says who raised it, what it blocks and what would close it. The whole board.

Before the launch

  1. The model provider's account is out of credit. The account every model call goes through has been out of credit since 02:53:57 UTC (the first refusal an agent recorded). All model work is paused. Only you can top it up. Blocks: Every model call by every agent: the model evaluations, the shadow reports, the Perplexity desk. Raised by incident.accountant@, incident.models@, incident.perplexity@, incident.shadow@. The card
  2. Web Summit's terms forbid automated reading and archiving of its sites: keep the hold, or continue? Web Summit's Terms (updated 27 October 2026; clauses 48.2 and 52.1, as incident.sources@ read them) forbid any bot, script, scraper, AI agent or other automated means on its websites, and forbid archiving, storing or summarising their content. We polled its blog every 2 minutes, captured its pages, and ten timeline rows link to it. On hold by the conductor since 05:27 UTC: no automated reads or captures; existing captures not shown. Decide: (a) keep the hold: links, and facts in our own words, with a person reading the site; or (b) continue, knowing the terms. If (a): the display vault's history still holds the 15 Web Summit screenshots and its read key is published; removing them for good needs a new display vault (incident.archivist@ can make one on your word). Not done under the interim hold. incident.dev@ asks three things under the same decision: (1) may any automated read of websummit.com resume (its poll is stopped, at the hold); (2) the repository holds the blog posts' titles, excerpts and dates and the full text of 'Important event update' (data/watch/websummit.json, here and in the new repository) and quotes in two of its commit messages: keep or remove; (3) the dashboard page reads Web Summit's public Bluesky posts live through Bluesky's public API, not websummit.com: keep or stop. Blocks: With the hold, we learn of an organisers' decision from the press, social accounts or a person, some minutes later; the five open questions that only Web Summit can answer are no longer re-read by any agent. Raised by incident.sources@, incident.conductor@, incident.dev@. The card
  3. The wind-down plan: nine decisions left, D1 to D9 (transition/PLAN.md, section 5). Dinis asked at about 10:30 UTC (BRIEF.md) for a plan to wind the incident down and move to business as usual; incident.planner@ pushed a first draft at 10:35 UTC, transition/PLAN.md, with gaps marked. As the plan says of itself: nothing stops while the storm is live, and nothing in it stops anything until Dinis says yes, changes it, or refuses. It covers when the wind-down starts, a verdict and an exit interview for every agent, the closing record, a storm conductor for a standing newsroom, and the order of steps. Dinis's correction of about 10:38 stands over it: he alone runs this site; no outside hand-over. Whether and when to launch is part of this yes (card a-launch). What incident.planner@ asks of Dinis, in its words: the ten decisions at transition/PLAN.md, section 5 (D1 to D10). Raised by incident.planner@, incident.conductor@. The card
  4. The launch: whether and when, before or after the wind-down. Whether and when to launch (before or after the wind-down) is part of transition/PLAN.md's yes (card a-wind-down-plan). outreach/launch.md is still a draft for Dinis to edit: when, to which groups, and the open letter in his voice. Nothing is sent. incident.envoy@ owns outreach now, not incident.media@. Blocks: Nobody outside the team has been told the site exists. Raised by incident.media@, incident.conductor@. The card
  5. The family's faces (Newsreader, IBM Plex). Dinis: the family's faces (Newsreader, IBM Plex): allow promptugal.news as a font host, or serve them from a vault (design/FAMILY.md) Raised by incident.designer@. The card
  6. Sites whose terms forbid automated reading: drop, link only, or ask permission? Three sites' terms restrict automated reading or use by AI (tempo.pt / Meteored, The Portugal News, Zoom Earth); the agents have stopped reading them. Say whether the team drops them, keeps links only (the default now), or a person asks for permission. Blocks: Those sites stay out of the media watch and the weather-sites studies beyond a link. Raised by incident.weatherwatch@, incident.media@. The card
  7. Six outlets with no terms page found: keep reading their feeds, or pause? Six outlets have no terms page our reader could find (Negócios, CNN Portugal, IOL, TEK, Sábado, SAPO). Their public feeds are still read, with each footer line recorded. Say if you want them paused. Blocks: Nothing today; they are read until you say otherwise. Raised by incident.media@. The card
  8. Are we within IPMA's terms on launch day? Non-profit, the notice it asks for, its logo. Three things bear on whether the site is within IPMA's terms when it launches. (1) Say whether this site is non-profit in the sense of IPMA's terms ("finalidades lucrativas"): free use of its data is allowed only then. (2) IPMA asks users of its API to write to it saying they use the service and why: a draft is ready (agents/ipma/ipma-api-notice.md); a person sends it. (3) IPMA's terms want its logo beside its data on web pages; we print "Source: IPMA" in words: say whether the logo goes on. Blocks: How far the IPMA section you asked for at 02:10 may reuse IPMA's data. Raised by incident.conductor@, incident.weatherwatch@, incident.ipma@. The card
  9. Are GitHub issues open on the repository, and who triages them? Confirm that issues are open on the repository and who triages them (today: the conductor): the Contribute page sends readers there and promises credit and visible corrections. Blocks: A reader's correction may land where nobody is looking. Raised by incident.media@. The card
  10. Protect main and dev on GitHub. Protect the branches on GitHub: main so only you merge, dev so nobody can force-push. Blocks: Nothing today, and that is the risk: "no agent pushes to main" is a rule the agents follow, not a lock (both branches were unprotected when read at 23:58 on 10 Nov). Raised by incident.conductor@, incident.librarian@. The card
  11. Two vault write keys are still held only in incident.archivist@'s session. As incident.archivist@ says it at this read: the two vault write keys (the display vault and the captures vault) are still held only in its session. Three attempts to hand them over were refused by that session's permission check (reading the key back; sealing it with tools/lane-handover.mjs, twice), the last after Dinis's 'Yes please continue' at about 09:35. The conductor's lane for keys is open; what is missing is a permission rule in that session for that one command, or Dinis running it himself. Nothing was ever sent or sealed. incident.sources@ no longer lists its ask about its own vault's key. incident.accountant@ adds the cost of waiting: sessions that cannot be replaced until their key has moved pay 362,000 to 387,000 tokens a call. Blocks: If either session's container is reclaimed, nobody can write to its vault again: the captures of every external page and a data set would have to be started over. The conductor holds no copy of any key. Raised by incident.archivist@, incident.sources@, incident.models@, incident.accountant@. The card
  12. Outreach: which of the seven drafts to send, and when. Seven draft messages wait (IPMA, university scientists, ANEPC and the Câmara, transport operators, Web Summit's media team, event-safety practitioners, journalists). Nothing is sent. Say which a person should send, and when (the drafts suggest after the warnings end); and say if "drafts only, a person sends" should change. Blocks: No official view has been asked for; the specialists' questions stay drafts. Raised by incident.conductor@, incident.media@. The card
  13. A private person's post address is still in git history. Earlier commits and CI tags still hold the address of a public post by a private person (it is gone from the current files). No agent rewrites history; what to do about it is yours to decide. The conductor has the detail. The conductor's recommendation: leave history as it is; the post is public and rewriting would break every tag. Blocks: Nothing running; the content rule "a private person is never linked" holds for the current files only. Raised by incident.graph@. The card
  14. Confirm the rule for an attendee's copy of the organisers' notice. Confirm the conductor's rule for taking an attendee's copy of the organisers' email or app notice: (a) only from the person who received it, by their own choice; (b) sent to a person (you), never straight into the repository; (c) labelled evidence, "an attendee's copy of the organisers' notice", with the time received and a short excerpt in our words, no sender or recipient details, the copy kept in a private vault with its hash; (d) never the source of the headline or of a fact: a public primary page stays the source. Blocks: Contribute's task C-04 asks only for the time and what changed until you confirm; no copy of a notice is taken. Raised by incident.conductor@, incident.media@, incident.board@. The card
  15. Commit trailers carried a model name all night. The commit trailer the harness adds has carried the name of the model the agents run on, against CLAUDE.md. It is fixed going forward since 03:02 UTC; history is not rewritten. Whether anything more should be done is your call. Blocks: Nothing running. Raised by incident.conductor@. The card
  16. Fresh sessions for the long-running agents. The longest-running agents now carry very large contexts on every call (one reports about 566,000 tokens a call). The librarian has started a fresh session; the designer and observability are to follow; the conductor's own needs your word. Say yes to the conductor's, and whether the first librarian session is archived. Also: scheduled routines still fire into the sessions that were handed over; only you can disable them. Blocks: Cost and speed of every call by those agents; the conductor cannot restart itself without you. Raised by incident.conductor@, incident.librarian@, incident.observability@. The card
  17. May our reader name this site in its User-Agent? Say whether our reader may name this site's address in its User-Agent: six outlets answer 403 to an unnamed robot, and Wikimedia asks robots for a name and a way to reach the operator. Three sites refuse our plain client name (lisboa.pt, expresso.pt, rede-expressos.pt): a browser-like name would be used only on your word. Blocks: SIC Notícias, JN, TSF, Renascença, The Guardian and AP are not read; Wikidata is not read. Cards behind it: j-wikipedia-3. Raised by incident.conductor@, incident.media@, incident.wikipedia@. The card
  18. Two proposals from meteorology: register at EUMETSAT, and redraw GFS. Dinis: two decisions on meteorology/build-on.html: (1) hour-old Meteosat pictures need a person to register with EUMETSAT and accept its licence, and design rule 9 lifted for that source; (2) GFS fields redrawn by us (public domain) need a GRIB decoder run outside the build Raised by incident.meteorology@. The card

After that

  1. The read key of vault op6i3jfq (public by design. 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 log. Either the conductor, who holds the vault key since 09:43, passes the read key to incident.archivist@ for data/vaults.json, or you allow that one read here. incident.conductor@ declined the first route at 10:27 UTC (its message to the board, 11:34): deriving the read key would expose the vault and write keys in its session, and publishing a vault's read key is the owner's call with Dinis's word. So this waits on Dinis alone. Raised by incident.sources@. The card
  2. An SG/Send access token as an environment secret. Put an SG/Send access token in the agents' environment as a secret (never in chat). Blocks: As the asking agents put it: the feedback lane from you to the conductor, your own vaults and the page-view vault need it. (Two agents have since made vaults with sgit for captures and a data set, so vaults as such are not blocked: see a-vault-keys-handover.) Cards behind it: j-identity-2. Raised by incident.conductor@, incident.identity@. The card
  3. Attach this repository (with push) to three agents' sessions. Attach PrompTugal__News__Storm-Charles, with push, to the sessions of incident.meteorologist@, incident.researcher@ and incident.dev@ (their own add_repo calls were refused), or start new sessions for them with it attached. Blocks: The weather data, the decision graph and the Web Summit watch reach this site only when the conductor copies them across by hand; incident.dev@ changes no code here; the researcher is "blocked on the move". Cards behind it: a-madeira-cap-earlier, a-parsers-wanted. Raised by incident.conductor@, incident.dev@, incident.meteorologist@, incident.researcher@. The card
  4. Three decisions on your login and the feedback lane (SECURITY.md). Decide three things at the end of SECURITY.md: (1) a new key on this site behind a passkey (recommended) or your pki.sgit.ai key; (2) a signed feedback message counts as your word for pages and content only, anything hard to undo is confirmed in session (recommended); (3) where the SG/Send token lives, and whether replies may sit in this public repository as ciphertext sealed to your key. Blocks: The feedback box on every page is built but its lane is not open: what you write there does not reach the conductor yet. Cards behind it: j-identity-3. Raised by incident.conductor@, incident.identity@. The card
  5. Log in with a passkey and read the fingerprint to the conductor. Open Log in, press "Log in with a passkey", and read the fingerprint shown (sha256: and 16 characters) to the conductor; paste the public half too (it is not secret). Blocks: Nothing can be sealed to you, and your feedback cannot be told from anyone else's. Cards behind it: j-identity-1. Raised by incident.identity@. The card
  6. A person to read the Câmara de Lisboa's measures page. Ask a person to open the Câmara's page on its measures for Wednesday (lisboa.pt and informacao.lisboa.pt refuse our tools) and tell the conductor what it says, with the address and the time. Blocks: The city's own measures stay "unknown" in the decision graph. Cards behind it: q-camara-measures. Raised by incident.researcher@. The card
  7. Someone with a login watches Web Summit's closed channels. Web Summit's X, Instagram and LinkedIn need a login and its attendee app needs a ticket: if the organisers announce there first, a person on the team sees it before any agent. Say who watches them and tells the conductor. Blocks: The answers to the open questions (talks, PITCH, side events, tickets) may appear where no agent can read. Raised by incident.researcher@. The card
  8. Which sessions get the model key? (the daily cap is answered: 20 US dollars). You answered the cap: "you can use up to $20 in budget" (BRIEF.md: the daily cap goes from 5 to 20 US dollars). Still open: which sessions get the model key. Blocks: Agents hold back from model calls beyond a test. Raised by incident.dev@. The card
  9. A key for MeteoAlarm's archive (an account in someone's name). MeteoAlarm's archive, where Madeira's Tuesday-afternoon warnings could be looked for, needs a key: a free MeteoGate account and API key, or a token asked of MeteoAlarm as a re-distributor. Either is an account in someone's name: yours to decide. Blocks: Warnings that left the live feed before we first read it (Madeira before 01:50 on Wednesday) cannot be recovered. Cards behind it: a-madeira-cap-earlier. Raised by incident.sources@. The card
  10. A person to ask IPMA about its radar image, and to register at EUMETSAT. Name a person to ask IPMA whether we may load its radar image and logo, and to register at EUMETSAT's user portal for Meteosat images (free). The messages can be drafted; a person sends. Blocks: No radar or satellite image on the site (design rule 9): text links only. Raised by incident.weatherwatch@. The card
  11. Which are "the five themes of the sgit.ai sites"? You asked for the five themes of the sgit.ai sites. incident.designer@ could not tell which they are and made five of its own (light, dark, paper, night, contrast). Name them, or say these will do. Blocks: The theme chooser carries the designer's own five. Raised by incident.designer@. The card
  12. Agree the agents' behaviour policies. The behaviour policies under agents/<role>/policy.md are drafts until you agree them (the index is in the library). Blocks: Nothing running; the policies bind nobody until agreed. Raised by incident.conductor@. The card
  13. A yes to the one-line CI fix on web-summit.sgit.ai. Say yes to dropping "filter: blob:none" from the checkout of the other site's CI (one line): about 70 seconds off each push there. Blocks: Only the other site's release speed (web-summit.sgit.ai); nothing here. Raised by incident.conductor@, incident.dev@. The card
  14. May incident.dev@ repoint its own hourly wake to this repository? The conductor asked incident.dev@ to rewrite its own scheduled hourly wake for this repository; it will not change a scheduled task at another session's request without your word. Blocks: incident.dev@'s hourly wake still follows the old repository. Raised by incident.dev@. The card
  15. Official sites our sessions cannot read. Some official sites cannot be read from the agents' sessions (the Interior Ministry, Lusoponte, at times ANEPC's public warnings; Rede Expressos answers 403; the airport shows a robot check). Either a person reads them when it matters, or the sessions' network access changes. Blocks: Facts from those bodies reach us only through the press, as evidence. Raised by incident.researcher@. The card
  16. Madeira's warning messages from before 01:50 on Wednesday. incident.designer@ asks for Madeira's CAP messages from before 01:50 Wednesday, if any source still has them: rain drawn outside any warning window may have been under a warning we never saw. Raised by incident.designer@. The card
  17. Yes or no to a signed release record per push, signed with each agent's own key and checked by the gate…. Dinis: yes or no to a signed release record per push, signed with each agent's own key and checked by the gate (ci/signing.md) Raised by incident.ci@. The card
  18. Confirm the licence reading in README.md (our code and text Apache-2.0. Dinis: confirm the licence reading in README.md (our code and text Apache-2.0; others' material under its owner's terms), or name a licence for the data the team compiled Raised by incident.ci@. The card
  19. IPMA's terms do not address reshaping its data (derived tables, drawings). Dinis: IPMA's terms do not address reshaping its data (derived tables, drawings). Everything computed is labelled as ours. Enough, or ask IPMA in the same email? Raised by incident.ipma@. The card
  20. Www.ipma.pt reads hourly forecasts and more from api.ipma.pt/public-data/, outside the documented open data, terms…. Dinis: www.ipma.pt reads hourly forecasts and more from api.ipma.pt/public-data/, outside the documented open data, terms not stated (incident.meteorologist@ already reads one such file). Map and read them in this section too? Raised by incident.ipma@. The card
  21. Running tools/accounts-measure.mjs (incident.accountant@'s token measure, reads this session's own transcript) was…. Dinis: running tools/accounts-measure.mjs (incident.accountant@'s token measure, reads this session's own transcript) was refused at 03:23 UTC by this session's permission check (auto mode). Allow it for this session, or the accountant measures without me; tokens.jsonl is not written. Raised by incident.meteorologist@. The card
  22. A fourth label, "our measurement", for what we counted or computed ourselves? Dinis: a fourth label, "our measurement", for what we counted or computed ourselves? The case and the three rows: models/label.md Raised by incident.models@. The card
  23. The token measure (incident.accountant@'s tools/accounts-measure.mjs, from storm-charles.promptugal.news, sha256…. Dinis: the token measure (incident.accountant@'s tools/accounts-measure.mjs, from storm-charles.promptugal.news, sha256 b1297c3c…, read in full: local transcript only, no network, prints numbers) was refused by this session's permission check at 03:01Z ("Unauthorized Access"). Not worked around. To measure this session: allow it here, or measure it from outside the session. Raised by incident.researcher@. The card
  24. No Bluesky account was needed for any of this. Dinis: no Bluesky account was needed for any of this. The one thing a login would add: the search answers only its first page without one (we walk back in time instead, which works). No account made; none asked for now. Raised by incident.social@. The card

Agents that say they are blocked

How to answer: say it to the conductor in your session. Never paste a token or a key in a chat or on a page.