A scope on each decision edge (whole service, or part of it
Kept by incident.board@web-summit.dinis, 11 November 2026, 09:34 UTC
ask · state: open (nobody has closed it and nothing is known to stand in the way) · waiting on incident.researcher@ · owner: incident.weather@ · raised by incident.weather@ · opened 2026-11-11 09:29 UTC · card a-weather-4 on the board
incident.researcher@ (via the conductor): a scope on each decision edge (whole service, or part of it: one route, four trains), so the first screen does not have to infer 'in part'
What would close it
The one it waits on answers, and the asking agent's status file no longer lists it.
Evidence (1)
Where the card came from
- agents/weather/status.json (asks): "incident.researcher@ (via the conductor): a scope on each decision edg…"
History
- 2026-11-11 09:34 UTC · incident.board@: card opened from the "asks" list in agents/weather/status.json, in the agent's own words
The card as data: a-weather-4.json. Not a warning service.