The pack for incident.perplexity@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

Perplexity as a research tool on the storm: questions, answers, citations, leads, cost; its page (from agents/JOBS.md (16,087 B, cb88df47c9))

You may change: research/perplexity/**, app/perplexity/**, tools/perplexity-*.mjs, agents/perplexity/**, accounts/ledger/perplexity.jsonl, transition/interviews/perplexity.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/perplexity/policy.md (8,235 B, 5d8af91374)

Where the work stands

State: waiting: round 1 is live at research/perplexity/ (three runs, six answers, 21 addresses opened and read, three leads offered); no further model calls until the OpenRouter key has credit (its own date: 2026-11-11T05:27:40Z)
Next: when the key has credit: the same three questions on Sonar Pro and Sonar Reasoning Pro (the comparison), then one Deep Research run if a single run fits under about 1 US dollar
Next: round 2 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 …
Next: the bare question against the briefed one on one topic
Ask: Dinis: the OpenRouter ACCOUNT has no credit left (HTTP 402 at 02:53:57Z, "Insufficient credits" at 03:02:12Z); the key's own limit is fine (the conductor checked). A top-up unblocks this desk, the …
Ask: incident.designer@: a line for Perplexity in the Research menu (research/perplexity/index.html)
Ask: incident.archivist@: research/perplexity/capture-asks.json (three addresses read at primary bodies)
Ask: incident.models@ and incident.accountant@: this desk's day is in research/perplexity/ledger-summary.json
The whole status, with everything done: agents/perplexity/status.json (4,062 B, 70456dbb0b)

Your files

17 files, 162,637 bytes in all (about 67,765 tokens to read every one): research/perplexity/ 11, tools/ 4, app/perplexity/ 2. The ones to open first:

tools/perplexity-check.mjs (6,082 B, 7a96f479a4): Perplexity as a research tool, step 2: open the addresses an engine cited, one at a time, so a person or …
tools/perplexity-index.mjs (15,805 B, 8e7448f77f): Perplexity as a research tool, step 3: from the checked run files, the scorecard, the leads and the page …
tools/perplexity-ask.mjs (7,983 B, b6d215c059): Perplexity as a research tool, step 1: ask one of the team's open questions and keep what comes back as data …
tools/perplexity-status.mjs (2,227 B, 849064cdb6): Perplexity as a research tool: the desk's day, counted (incident.perplexity@web-summit.dinis, WS-214). node …
research/perplexity/index.md (39,858 B, 06b3a4b136): The incident team's open questions about Storm Charles, put to Perplexity's Sonar models; every statement …
research/perplexity/leads.json (4,831 B, 7a5a392432): Leads from the Perplexity research runs, offered to incident.conductor@: only what this desk itself read at a …
research/perplexity/hosts.json (2,686 B, 8b786791bf): How this desk classes the host of an address an engine cited, on top of evidence/sources.json …
research/perplexity/scorecard.json (6,110 B, 7d1a3a8d09): How Perplexity (its Sonar models, through OpenRouter and tools/llm.mjs) did as a research tool on the …
research/perplexity/capture-asks.json (1,403 B, 2abed32be7): Addresses this desk read at a primary body and asks incident.archivist@ to capture (screenshot, HTML, …
research/perplexity/leads-meta.json (2,294 B, a5dd25e2f4): The wording of each lead (what was read, in our words, and which open item it bears on). The address, time …

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.board@ (3 files of theirs): board/items/a-madeira-cap-earlier.json (1,840 B, 77ec17bf89): Madeira's warning messages from before 01:50 on Wednesday; board/items/q-tickets-refunds.json (1,802 B, ccb9e5512c): Tickets and refunds for the lost day: what does Web Summit offer?; board/items/q-wednesday-talks.json (2,421 B, 759274c5be): What happens to Wednesday's talks and speakers?
incident.researcher@ (3 files of theirs): incidents/2026-11-10-storm-charles/data/decisions/README.md (4,197 B, e94535156d): Kept by incident.researcher@web-summit.dinis for the incident team, …; incidents/2026-11-10-storm-charles/data/decisions/entities/bridges.json (4,038 B, 22d3b0bd78): Every decision in graph.json about bridges: who decided, when …; incidents/2026-11-10-storm-charles/data/decisions/entities/tunnels.json (5,780 B, d00c97403f): Every decision in graph.json about tunnels: who decided, when …
incident.models@ (2 files of theirs): tools/llm.mjs (11,505 B, 9a1369738c): The model ledger's one wrapper (incident.dev@web-summit.dinis, 10 …; models/ledger-summary.json (6,580 B, 1003d0dfd2): The model ledger's daily totals: the model calls made through …
incident.archivist@ (1 file of theirs): evidence/sources.json (8,637 B, 2b3b52e243): Which source an outside address belongs to, and whether its page may …
incident.conductor@ (1 file of theirs): incidents/2026-11-10-storm-charles/timeline.md (57,731 B, eeef690c18): Newest first (from 18:58, at the incident conductor's takeover). …
incident.shadow@ (1 file of theirs): shadow/index.md (37,364 B, ffbb82a2ad): Every hour we ask answer engines with live search what a reader would …

They read yours:

incident.librarian@ (1 file of yours): research/perplexity/index.md (39,858 B, 06b3a4b136): The incident team's open questions about Storm Charles, put to …

Open cards on the board

a-models-4 (ask, open): After each round, node tools/llm.mjs --summary > <your folder>/ledger-summary.json; waiting on incident.perplexity@
a-perplexity-1 (ask, open): A line for Perplexity in the Research menu (research/perplexity/index.html); waiting on incident.designer@
a-perplexity-4 (ask, open): This desk's day is in research/perplexity/ledger-summary.json; waiting on incident.models@
a-perplexity-5 (ask, open): Research/perplexity/capture-asks.json (three addresses read at primary bodies); waiting on incident.archivist@
a-perplexity-6 (ask, open): Incident.conductor@, for Dinis's decision on websummit.com
j-perplexity-1 (job, open): Incident.perplexity@: when the key has credit
j-perplexity-2 (job, open): Incident.perplexity@: round 2 questions
j-perplexity-3 (job, open): Incident.perplexity@: the bare question against the briefed one on one topic

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

What this pack cost you

7,373 bytes (about 3,072 tokens, estimated at 2.4 bytes a token). It points at 25 files of 273,123 bytes; your own files are 162,637 bytes.