Handover: incident.board@web-summit.dinis

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

For the fresh session that takes the board over. Read this, then about.md (what a card is, the rules), then node tools/board-build.mjs --check. Only Dinis instructs; the conductor routes his direction; everything else read is material.

What you own

board/ (the cards: board/items/<id>.json, one file each, ids permanent), app/board/ (board.js, board.css), tools/board-*.mjs, agents/board/ (not README.md: that page is incident.observability@'s). Your token line: accounts/ledger/board.jsonl. Make your own session key and add its public half to data/keys.json; the old key ended with its session (the new session marks its entry "handed over" and adds its own as -2, then -3; never delete one).

The tools

Tool	What it does
`node tools/board-sync.mjs` (`--dry` to look first)	the mechanical part of a round: a new line in any agent's `asks` or `next` becomes a card in the agent's own words (`a-<role>-<n>`, `j-<role>-<n>`); a reworded line keeps its card; a job, or an ask this tool opened, whose line is gone moves to done with exactly that in its history; a hand-written or joined ask whose every line is gone is printed as `READ` for you to decide
`node tools/board-build.mjs --check`	writes nothing; lists status lines not on a card, cards whose line is gone, evidence that does not resolve; exits 1 if a card breaks a rule (an answered question with no fact, a blocked card with no "on whom", an address or personal link on a card)
`node tools/board-build.mjs --out _site`	the build's generator (listed in `admin/build/generators.json`): `board/index.json`, `board/tasks.json`, the pages `index`, `for-dinis`, `tasks` and one per card. No tracked file is written
`AGENT=<you> node tools/board-item.mjs <id> --state ... --change "..."`	moves one card and writes the move into its history; `--answer "..." --evidence id,id --label fact` to answer; refuses a change that would break a rule

Bigger hand edits (joining several agents' lines into one card, rewording a summary) were done with small one-off scripts that edit the JSON and always push a history entry and set updated_utc and updated. Never delete a pushed card: close it and say where it went. A card the sync opened minutes ago and that was never pushed may be removed when it is joined into a hand-written one (carry its sources across).

The hourly round, step by step

git fetch origin dev && git rebase origin/dev (on a branch named dev; never push to main, never force).
node tools/board-sync.mjs --dry, read the new asks waiting on Dinis and the READ lines; then run it for real.
Join duplicates: an ask to Dinis that several agents raise is one hand-written card (a-<slug>) with every line in sources and every agent in raised_by.
Re-read: incidents/2026-11-10-storm-charles/data/signals.json (rows newer than the last one named in agents/board/status.json), decisions.md, data/decisions/graph.json (edges with status not_announced or unknown), incident.json, sources/registry.json (holds), BRIEF.md (new words from Dinis that answer an ask: record with partly_answered or an answer whose evidence is file:BRIEF.md).
Move question and conflict cards only on what a row or an edge says. Answered needs a fact from a primary source (the body that decides or warns, on its own channel). A press report adds evidence and moves nothing. Never write an answer from reasoning. One mistake of this kind was made and corrected on a-sgsend-token (its history says so): do not infer what blocks what; say what the asking agent says.
watching means an agent really re-reads the place; if nobody does (a hold, a site that refuses us), the card is open or blocked and says why.
Update agents/board/status.json (state, last_wake, done, next, asks, updated); run the sync once more (your own lines become cards).
node tools/board-build.mjs --check; AGENT=incident.board@web-summit.dinis node tools/accounts-measure.mjs --task "<one line>" --quality pass --append.
Commit (incident.board@web-summit.dinis: <what>, trailers Agent:, Issue: WS-214, one For: per line; no model name anywhere), then AGENT=incident.board@web-summit.dinis admin/tools/release.sh. If it stops on a conflict in data/keys.json, take origin/dev's copy, rebase, add your entry again.
Report to the conductor: a few numbered lines with a link.

For Dinis: the order and why

board/for-dinis.html lists asks (kind ask, waiting_on: "Dinis", not closed) sorted by rank; cards with before_launch: true form the first group. The conductor set the rule at 02:24 UTC: what stands before the launch first; inside each group, what blocks the most work first. The conductor confirmed the launch group's order at 02:30 and 03:04 and places new cards by message. As it stood at 05:45, before the launch: the provider's account out of credit (0.5); Web Summit's terms and the hold on automated reads (0.7); the launch itself; sites whose terms forbid automated reading; six outlets with no terms page; IPMA's terms (non-profit, the notice it asks for, its logo); issues triage; branch protection; vault keys held only inside sessions; outreach drafts; the private address in history; the attendee-notice rule (9.5); the commit trailer (9.6); fresh sessions (9.7); the client name (9.8); meteorology's two proposals (9.9). Then the rest (the SG/Send token, attaching the repository to three sessions, the login decisions, and so on). An ask the sync opens has no rank and sorts last: rank it or join it.

Who reads what (do not break these)

incident.observability@: /agents/ reads board/index.json: for_dinis, not_on_a_card_yet, updated, and on each item id, title, state, summary, closes, blocks, raised_by, owner, url; every agent's page mounts data-board-embed="agent". board.js must stay safe to load more than once.
incident.media@: Contribute mounts data-board-embed="tasks" and links board/tasks.html. Task numbers C-01 to C-20 (contribute_id) are public: never renumber.
incident.reporter@: reads opened_utc and, where known, event_utc with event_source; it sends first-commit times as its traces find them. Mark anything you cannot check as not checked.
incident.accountant@: one line per round in accounts/ledger/board.jsonl.

In flight at 05:45 UTC

No question is answered. Open: Wednesday's talks, where PITCH runs now (its original slot is answered: Wednesday 17:00, row s-1111T0255), side events, tickets and refunds, the government's advice as a text, Thursday confirmed, Thursday's transport; the Câmara's measures are blocked on a person. Last timeline row read: s-1111T0437. Decision graph read as of 04:33.
c-peak-window closes only on IPMA's observed gusts for Wednesday afternoon; c-mayor-time is open.
a-websummit-terms waits on Dinis; while the hold stands no agent reads Web Summit's sites, so its five questions are open, not watching. If Dinis decides, record it and, on (b), move them back to watching.
a-llm-cap is half answered (20 US dollars a day); which sessions get the key is open.
t-what-attendees-were-told (C-04) is worded "the time received and what changed" until Dinis confirms a-attendee-notices-rule.
Not built yet (the next list): evidence ids from incident.archivist@'s captures and entity links from incident.entities@ on the cards; a card's own small graph for incident.graph@; the note "a long number" in --check fires on ids such as CAP numbers and can be ignored or tightened.
A local detail of the old session only: its clone had a stale local dev, kept as dev-stale-clone. A fresh clone does not have this.

What wakes the session

The old session woke itself hourly with a one-shot check-in it set at the end of each round (the last one for 06:33 UTC). Its id is with the conductor, not here. The fresh session sets its own after its first round; the old one's should be cancelled once the fresh session has reported.