> Kept by incident.perplexity@web-summit.dinis, 11 November 2026, 03:05 UTC

## What it is good for here, and what it is not

Our analysis of the first three runs (six answers, one model); labelled as analysis, to be tested by the next rounds.

**Good for**

- **Finding a deep address on a body's own site that our tools had not reached.** Asked about the PITCH semi-final, it returned Web Summit's own session page, which gives the slot as Wednesday 11 November, 17:00 to 18:00, Centre Stage. That settled a conflict the board had held open (the conductor made it timeline row s-1111T0255) since Tuesday night (Wednesday 17:00, unsourced, against Thursday in a press preview): the full agenda sits behind a login, but single session pages are public and the engine's index had this one. Only the Portuguese question found it; the English one returned the group rounds instead.
- **Finding a regional body's own page.** Asked about Madeira, it returned the regional civil protection service's own notice on Charles, in both languages; we read it there. (incident.researcher@ had already read the same page: the engine confirmed our record here, it did not extend it.)
- **Saying "I found no such page".** With the brief asking for the deciding body's own page, it said plainly, 10 times in six answers, that it had found none (Lusoponte, the Câmara, Infraestruturas de Portugal, the regional government, Web Summit on refunds). Each time that matched what our own reads had found. A tool that admits an empty hand saves the time of chasing a made-up address: it made none up here.
- **Price and speed.** About half a US cent and five seconds a question. Checking its work costs far more than asking: 21 pages opened and read for six answers.

**Not good for**

- **Being the source.** Of 90 addresses returned, 28 were a primary body's own page, and 24 of those were Web Summit's own sites on the one question about Web Summit (the other four: Madeira's civil protection three times, an embassy once). On the bridges and tunnels it returned no primary page at all: press, and sites that rewrite the press.
- **Knowing what happened next.** Both bridge answers reported the 60 km/h limit and neither said it had been lifted on Tuesday night (our record: 22:29). The lifting was in a headline on the very page one answer cited, and in the title of an address the other returned and did not use. It answers the question asked, from the paragraph that matches, not from the latest state of the thing.
- **Times.** It gave a second notice by Madeira's civil protection "at 15:43" on its home page; that time is not on the page. It spoke of an "Important event update" *email* by Web Summit with no address, while not returning the organiser's public page of that title, which is this site's headline.
- **The organiser's newest page.** On Web Summit it returned 24 schedule, session and competition pages and not the one blog post that matters. Its index of a site is broad and old; a watch on the page itself (incident.dev@'s) is the tool for news from a known address.
- **Consistency across languages.** The same question in Portuguese and English returned different addresses and different findings; each language found a lead the other missed on Web Summit. Ask both.

**So, for this team:** use it to find *where* something might be published, then read it there. Three answers of six gave us an address worth opening that we did not hold; none gave us a fact we could use without opening it.

## Cost per useful lead

Three leads read at primary addresses for 0.033 US dollars of model spend: about one cent a lead. The real cost is the checking: the agent's time to open 21 addresses and read them against 29 statements. A lead from the engine is cheap to get and dear to trust.

## A hold on Web Summit's site (05:27 UTC)

Since 05:27 UTC this desk does not request websummit.com: an interim hold from incident.conductor@ until Dinis decides, because the site's terms (updated 27 October 2026, read by incident.sources@) forbid automated access and archiving. The seven pages in run 3 were read at 02:55 to 02:56, before the hold. From now on, what an engine says about Web Summit is recorded as the engine's answer and marked **not checked: on hold**, not followed to the site.

## What is next

- The same questions on Sonar Pro, Sonar Reasoning Pro and (once, if a single run fits the budget) Sonar Deep Research, to compare the variants. Paused since 02:54 UTC: the OpenRouter account's credit balance ran out (HTTP 402, then "Insufficient credits" at 03:02); the key's own limit is fine (incident.conductor@, 02:54). Only Dinis can top it up.
- More of the team's open questions: the airport (ANA's own statement), the government's advice to Web Summit as a published text, the Câmara's measures, who else archived IPMA's earlier warnings, Thursday's transport, comparable storms and event cancellations.
- The bare question against the briefed one, on the same topic: does asking for the primary page change what comes back?