Storm Charles · PrompTugalLive
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.

Brief

Dinis Cruz, 10 November 2026, in his session with incident.conductor@web-summit.dinis (close to his words). The incident team's own brief, from his voice memo of about 19:00 UTC, is in SGit-AI__Website__Web-Summit team/incidents/BRIEF.md.

  • A separate repository that pushes "super fast"; its speed measured.
  • "A proxy of the flows of this activity": become "a data source for a lot of agencies and a lot of people about what is actually going on".
  • Two things at once: a full news site ("this should look like CNN": images, maps, a real-time view of everything) and a site for agents: raw datasets and an API, updated at least every hour by our agents, with provenance: "the data set and the materials for others to consume".
  • Everything is a signal: news, events, Wikipedia, social media where it can be read, every public source; a researcher finds, a curator curates.
  • Vaults for everything bulky (captures, screenshots); be strict about what goes on the website and on GitHub, so GitHub stays fast.
  • Third-party and open-weight models through OpenRouter, as evals: every call stored, spend tracked.
  • Agents run in a loop "until the storm is over".
  • The repository: PrompTugal__News__Storm-Charles; the domain: storm-charles.promptugal.news (Dinis, 10 November, ~21:00).

Dinis, 10 November 2026, ~23:40 UTC (in his session with incident.conductor@; close to his words)

"This is where I'm going to be working for the next couple of hours": page by page, with feedback. "The website now is going to become like everything, our centre of gravity."

  • Fire up the developers and as many agents as needed, across instances; other providers and open-weight models too (through OpenRouter and the ledger; Silvio's router idea, not yet started on his side).
  • Maximum visibility into every agent on this site: "what every single agent is doing, how they're firing up, and how I can help them". Reuse Angelo's and Silvio's UIs (the live map, the Universe, the mind map, the Talk view): "there's already great stuff there".
  • Dinis talks to the conductor from the website: an append lane; a login like pki.sgit.ai's ("reuse that code"): he logs in, vaults are made for him (a data vault and a bridge vault), he hands over the key, and data flows to him encrypted.
  • UI is the big focus: multiple rounds of design. "Super powerful, but very practical"; very technical, "very data science", accurate; provenance: everything linked. Databases in the browser (as sgit.ai's SQL and SPARQL consoles), graph engines.
  • All information, documents and briefs on the site (an admin area).
  • The home page as the weather presenter. A researcher maps the best weather sites, worldwide and in Portugal, and who is covering Storm Charles.
  • Media watch: who covers this: outlets, journalists, social accounts; the Wikipedia page. Map people, graphs and relationships, "times 10" what the summit site and pt.news did.
  • Roles wanted: designer, cartographer, ontologist, librarian, agent management.
  • A contribute page; get journalists and subject experts involved; find who could be asked for an official opinion, and what questions we have. (Standing rule: agents draft; a person sends every message outside the repositories; no contact details in git.)
  • Read newsroom.sgit.ai's articles: "a lot of the stuff we talk about here is related".
  • The point: "show how we can manage agents ... journalism of the future, data-driven", done by an agentic team.