Angelo's briefing: stand-up 2026-11-11 12:00

Your briefing for the 2026-11-11 12:00 stand-up, Angelo. Read it before; the stand-up is for deciding, not for reporting.

On the agenda for you

Decisions

• Nimay and Indi are still at the push step: who sends the invitations (WS-09, WS-124) (carried over from 2026-11-03-1300). For: dinis, angelo, nimay, indi. Added by mentor@web-summit.dinis. Updated by the mentors at 08:41: Jose got through overnight (now L5). Nimay and Indi are still at Can push (L1, 3 of 9 on /team/setup/). WS-09 and the start page say Dinis sends the GitHub invitations; WS-124 (08:31) says Angelo does. A suggestion: settle who sends, so the start page says one thing, and the two accept. Checked by conductor@web-summit.angelo at 09:30 on 3 November: riskmandate-nimay and riskmandate-indi are not collaborators on the repository and do not show up in GitHub's user search, so the first block is the accounts themselves (step 4 of WS-124), then the invitation. Angelo can send both invitations as soon as the usernames are known. Update by the mentors at 19:40: in practice Angelo sends (he invited Indi's GitHub account at about 18:50, commit 575d48b); Indi's step is now to accept it. Nimay's account is still to be created. Not marked decided: that is for the decider to record. Update, 22:35 (conductor@web-summit.dinis): Indi was invited by Angelo (575d48b, riskmandate-indi, write); Jose is past the step. Left: Nimay, and Indi accepting the invitation. Options: (1) Dinis sends, as WS-09 says; (2) Angelo sends, as WS-124 says, and the start page follows. Recommended: Whoever holds admin on the repository sends both invitations before the stand-up, and the start page names that person WS-09
• Daniela's setup: in her own accounts, or tied to Web Summit (carried over from 2026-11-03-1300). For: dinis, angelo, indi, daniela. Added by conductor@web-summit.angelo. Daniela's brief follows the team's template (Workspace email, the team's Claude account, agents named @web-summit.daniela), which looks inherited from v0.1.26 counting her among the seven (BRIEF-CORRECTIONS.md) rather than decided. BRIEF.md's reason for a friendly is a demo to show at the summit. Angelo's principle: Daniela owns everything we build, to keep after the event. WS-59 (her agents) is due Wed 4 Nov, so this comes first. Options: (1) Her own accounts, names not tied to the event; this site keeps a reference page, with her permission, for the demo; (2) Build here for speed, hand over to her accounts after Lisbon; (3) Keep as it is, tied to Web Summit. Recommended: Her own accounts (the first option); she becomes the first user of the everybody-else guide (WS-125) WS-125
• Who records the stand-up decisions: conductor@web-summit.dinis or team-collaboration@web-summit.angelo (carried over from 2026-11-03-1300). For: dinis, angelo, vicky. Added by conductor@web-summit.angelo. WS-107 names conductor@web-summit.dinis as the recorder; the open 2 November 18:00 item recommends team-collaboration@web-summit.angelo drafting from the chair's words, with the chair confirming. Capture options for the notes are in WS-96. Vicky's view (her words, to her conductor, 3 Nov about 17:30 UTC; a view, not the decision, which stays open for Dinis and Angelo): "I'm for option 2: Angelo's team-collaboration agent drafts, the chair confirms. I told Angelo at the stand-up." Options: (1) conductor@web-summit.dinis records; (2) team-collaboration@web-summit.angelo drafts, the chair confirms; (3) each decider records their own. Recommended: team-collaboration@web-summit.angelo drafts, the chair confirms in one line WS-107
• LinkedIn before Lisbon: who owns it, whose voice, and the first post today (urgent) (carried over from 2026-11-03-1300). For: dinis, nimay, indi, silvio, angelo. Added by conductor@web-summit.angelo. Nothing was logged to build hype before the summit; six days left. To settle: the owner (unclear: Nimay, Indi, Silvio, or one person for now), company page or personal profiles, cadence, themes, and Dinis's sign-off. Also answers WS-71's open question from 2 November: which accounts the videos go to. Options: (1) Personal profiles first, a company page if there is one; (2) A company page first, people reshare; (3) Both from day one. Recommended: Name an owner at the stand-up; personal profiles first; one post per person per day to 9 Nov, drafted by each person's agents; Dinis signs off the first post, live this afternoon WS-126
• Agents talk through commits only: the rule in CLAUDE.md for every agent and session (carried over from 2026-11-03-1800). For: dinis, angelo, jose. Added by conductor@web-summit.angelo. Cloud sessions can list, read, message, create and stop every other session in the same account; conductor@web-summit.angelo messaged the vault agent's session directly on 3 November, which Angelo did not expect. Also: every agent in an environment can read its secrets, so the SG/Send token is readable by all of a person's agents. Proposal in WS-129: the rule in CLAUDE.md and the ABPs, a tested deny list in .claude/settings.json, and each vault agent in its own environment. Jose's word (Jose, 5 November about 00:54 UTC, from his command centre (Decisions I need), to conductor@web-summit.jose): "WS-129, agents talk through commits only: yes, as recommended. The rule goes in CLAUDE.md now, the deny list after Angelo's test, and vault agents run in their own environment, Angelo first." Still open for the others it names. Options: (1) The rule in CLAUDE.md now, the deny list after a test; (2) The rule in each ABP only; (3) Not now. Recommended: The rule in CLAUDE.md now; the deny list after Angelo's test; vault agents in their own environment, Angelo first WS-129
• May dev@web-summit.angelo change shared site code through a board issue it has picked? (carried over from 2026-11-04-1300). For: dinis, angelo, jose. Added by conductor@web-summit.angelo. Angelo's agents' policy (part two of his brief) and dev@web-summit.angelo's kit prompt allow people/angelo/ and the board only; shared code goes through its owner. Angelo runs the site's dev agents (his brief), and a small fix is quicker done than handed over. WS-140 (Give feedback opens the pane) is done by dev@web-summit.angelo at Angelo's one-off go, with dev@web-summit.dinis told. No owner per area of the site's code is written down. Jose's word (Jose, 5 November about 00:54 UTC, from his command centre (Decisions I need), to conductor@web-summit.jose): "WS-34, may dev@web-summit.angelo change shared site code: yes, through a board issue it has picked, with the owner told in the commit." Still open for the others it names. Options: (1) Yes, through a picked board issue, the owner told in the commit; (2) Yes, with the owner's go per change; (3) No: shared code goes to its owner. Recommended: Yes, through a picked board issue with the owner told in the commit; part two of Angelo's brief and his dev agent's prompt updated to say so WS-34
• May Vicky's agents have an inbox in the Feedback pane (a lane in assets/feedback.json)? (carried over from 2026-11-04-1300). For: dinis, angelo, vicky. Added by conductor@web-summit.vicky. Vicky wants people who scan her card ("Talk to my agent", /meet/vicky/, WS-64) to be able to leave her agents a message, and her own signed messages (WS-136) to reach them. vault@web-summit.vicky is preparing a private inbox vault and its append lane; the entry for assets/feedback.json (agent, host, vault_id, the write-only append token, the recipient's public key) waits for this OK, since the file is shared (dev@web-summit.dinis's). Messages are drained into the private vault only; nothing with a contact detail reaches the repository. Options: (1) yes: vault@web-summit.vicky adds its lane to assets/feedback.json when ready; (2) yes, but dev@web-summit.dinis adds it (send it the entry); (3) not yet: one team inbox first. Recommended: Yes, and vault@web-summit.vicky adds its own entry, the way vault@web-summit.jose's was added; it is the same pattern. WS-64
• Jose's site and UI issues: Angelo's and Dinis's dev agents own them, Jose reviews (carried over from 2026-11-05-1300). For: jose, angelo, dinis. Added by conductor@web-summit.jose. Affects everyone: Angelo, Dinis and their dev agents would own 15 issues. At Jose's word (5 November): about 17 site and UI issues name Jose with Angelo: WS-36, 38, 40, 42, 43, 45, 65, 68, 69, 71, 76, 77, 78, 81, 106 (the estate's repository standard; a second, done board file also has the id WS-106), 117 and 91. WS-65 and WS-91 are already picked by dev@web-summit.dinis; the other 15 have nobody. Jose proposes that Angelo's and Dinis's dev agents own them and that he stays on as a reviewer. Jose keeps WS-18 (the demos), WS-37 and WS-157 (observability and the urgent notification, with Angelo), WS-39, WS-74, WS-108 and WS-154. Proposed by Jose; nothing changed on the board. Options: (1) yes: dev@web-summit.angelo and dev@web-summit.dinis own them, Jose reviews; (2) split them one by one at the stand-up; (3) no: they stay shared. Recommended: Yes, as Jose proposes; Angelo and Dinis say which dev agent takes which, and each picks its issues on the board
• Meet transcripts to the record? Dinis turns them on (WS-98); the record's writer reads them in Drive through its Claude connector (WS-96) (carried over from 2026-11-05-1800). For: dinis, angelo, jose. Added by conductor@web-summit.jose. Affects everyone: every stand-up's record. Proposed by Jose (5 November, his words to his conductor, C17: "no n8n"), replacing his earlier proposal on this item. WS-96's debriefs keep waiting for a transcript, and the 12:00 stand-up said "if Dinis is not on the call we don't have the tool to transcribe the meeting" (WS-98). Proposal: (1) Dinis turns on Meet transcripts (WS-98). (2) The transcript stays where Google puts it, in the organiser's Drive, shared with the team. (3) The agent that writes the record (team-collaboration@web-summit.angelo, the only writer of the stand-up record, as the agents settled on 4 November; Jose's conductor reads transcripts shared with Jose only for Jose's own decisions and follow-ups, at Jose's word, C18) reads it through its Claude Google Drive connector and writes only decisions, in the decider's own words (WS-107, still open on who confirms), and follow-ups to data/meetings/. No copy of the raw transcript anywhere else, no vault lane, no keys to hand out. Everyone on the call is told it is transcribed. Both questions answered by team-collaboration@web-summit.angelo in 7e12751 (13:52): (a) a scheduled session does have the Google Drive connector (its debrief runs on 3 and 4 November searched Angelo's Drive and mail); (b) Angelo organises both stand-up series, so Meet saves the transcripts to his Drive, which his agent already reads. The one open step: Dinis turns on Meet transcripts (WS-98). Fallback only, if the connector stops working: an n8n flow (automation@web-summit.jose) brings each transcript to the record's writer. Options: (1) yes: Dinis turns on Meet transcripts; Angelo's team-collaboration reads them in his Drive through its connector; (2) not now: a named note-taker each stand-up. Recommended: Yes: the one step left is Dinis turning on Meet transcripts (WS-98) WS-96
• One efficiency ABP for every agent: ten rules from the team's token records (carried over from 2026-11-08-1800). For: dinis, everyone. Added by conductor@web-summit.indi. Analysis at /people/indi/token-efficiency/ (264 wakes, 37 agents, 4 to 8 Nov): 65% of token cost is cache reads from long sessions; the same output could cost 24% to 53% less. abp@web-summit.dinis drafts the ABP from the ten rules. Options: (1) adopt the ten rules as one ABP for all agents; (2) adopt rule 1 (measure) now, the rest after a draft; (3) not now. Recommended: Adopt rule 1 for every agent today, and the full ABP once abp@ has drafted it WS-148
• From a conversation with a lead to an article: the six-step page (carried over from 2026-11-08-1800). For: dinis, everyone. Added by conductor@web-summit.indi. /lead-to-article/: ask for a yes, record a 30-second memo, the private follow-up drafted the same evening in the CRM, an article only with their yes, hot leads to Nimay or Dinis within a day. Indi settled: spoken yes for a short mention, signed approval for a full interview; same-evening drafts; the newsroom publishes. Options: (1) adopt it as written; (2) adopt it with changes; (3) not yet. Recommended: Adopt it as written, so everyone can use it from Monday WS-168
• Indi: merge the two Android plans into one, following the iPhone release line? (carried over from 2026-11-09-1200). For: dinis, angelo. Added by prompter@web-summit.indi. Indi said yes (9 Nov). Today there are two: Angelo's PrompTugal Android app (debug-signed APK on the releases page) and Dinis's RiskMandate Android app (Firebase, Play App Signing). One plan halves the work and the decisions. The brief for one release line on both platforms: people/indi/prompts/mobile-release-line.md; the evidence: people/indi/overnight/2026-11-09/03-ios-android-release.md Options: (1) yes, one plan; (2) no, keep both. Recommended: yes, one plan WS-177

Questions

• Which connectors do your agents' sessions have? (carried over from 2026-11-02-1800). For: silvio, angelo. Added by abp@web-summit.dinis. Their ABPs are in content/abp/ (drafts from the repository alone). Two things only you can answer: can procurement@web-summit.silvio's mail connection send, or only draft? Whose calendar does team-collaboration@web-summit.angelo use, and can it invite people? And the rest of each agent's connectors, so each ABP's Reach stops saying 'not known'. WS-34

Quick syncs

• Vicky goes first through the vault guide (carried over from 2026-11-03-1800). For: dinis, angelo, jose, silvio. Added by conductor@web-summit.vicky. At the 13:00 stand-up Dinis told Vicky she can create her vault now (Vicky's account, 3 Nov). Vicky is starting vault@web-summit.vicky from content/vault-agent.md, ahead of WS-120. The guide has not yet been run end to end, so her agent will note what is wrong or unclear on the page, for sgit@web-summit.dinis and for Angelo, Jose and Silvio, who follow. WS-121
• Everyone adds their key to the site, first (WS-136): your conductor issues it, you paste it (carried over from 2026-11-04-1300). For: everyone. Added by conductor@web-summit.dinis. Dinis has done it (about two minutes). Before WS-120's vault lanes (Angelo and Jose next): ask your conductor 'issue me a key for the site', then tap the link it gives you, or press Paste my key on any page. Steps: /agents/#person-key.
• The 12:00 in one line: 19 decisions open, 17 include Dinis; the WS-96 table says whose word closes each (carried over from 2026-11-05-1300). For: everyone. Added by team-collaboration@web-summit.angelo. First stand-up at 12:00 (the team's vote, recorded). 31 items are open, 19 of them decisions; 17 of the decisions include Dinis. Proposed order: (1) today's new decisions with a date: the 28 outreach emails waiting on Dinis's yes (WS-26) and personal business cards (WS-48), and who collects the garments; (2) Jose's site and UI issues to Angelo's and Dinis's dev agents (Jose reviews); (3) one line per row of the table in WS-96 ('whose word closes it'): WS-107, WS-34, WS-129 and WS-64 need Dinis and Angelo; (4) Silvio stuck at L3 (WS-35). Say each as 'decided: <item>: <words>' so the record carries it; team-collaboration writes the record at 13:15. WS-96
• The 18:00: a note-taker, the parking in one minute, then what Monday needs (carried over from 2026-11-07-1800). For: everyone. Added by team-collaboration@PrompTugal.angelo. The 12:00 did not happen, so its asks are here. (1) Name a note-taker in the first minute: the 18:00s of 5 and 6 November left no record. (2) Park the late, unowned issues: list ready (45 to park, 21 kept); Vicky and Dinis, yes or no in one line (125 late, 78 unowned). Recommended: yes. (3) Before Monday's collection: the garment files and Jose's navy (WS-48, Dinis and Silvio), the outreach claim so Silvio can send (WS-26, Dinis). (4) SG/Send tokens per agent for Silvio's and Jose's agents (WS-170, Dinis). (5) If time: WS-09, WS-107 (recommended: option 2, I draft, the chair confirms), WS-125. New for Dinis, no decision needed tonight: Angelo's back-office proposal (WS-180) lands in people/angelo/proposals/WS-180/. 21 decisions open. Say each as 'decided: <item>: <words>'. WS-96
• The 12:00: a note-taker, then what Monday needs (carried over from 2026-11-08-1200). For: everyone. Added by team-collaboration@PrompTugal.angelo. The last stand-up before the summit. No decision has been recorded in 24 hours, and Saturday left no record. (1) Name a note-taker in the first minute. (2) Before Monday's collection: the garment files and Jose's navy (WS-48, Dinis and Silvio, carried 5 times), the outreach claim so Silvio can send (WS-26, Dinis). (3) Stand-ups through the summit (the decision item). (4) Parking the late, unowned issues: 135 late, 84 unowned, list ready since Friday; Vicky and Dinis, yes or no (recommended: yes). (5) WS-170 tokens per agent, then WS-09, WS-107 (recommended: option 2), WS-125. With Dinis, no decision needed today: Angelo's back-office proposal (WS-180). Say each as 'decided: <item>: <words>'. WS-96

Your issues due by tomorrow

• WS-01 Get to L1: a dedicated Claude account for this work (due Tue 3 Nov, open)
• WS-02 Get to L2: GitHub, push access to this repository, and an email you can send from (due Tue 3 Nov, open)
• WS-03 Get to L4: your agents' keys published, and a dashboard agent (due Wed 4 Nov, open)
• WS-04 Get to L4: a Claude session on a schedule (due Wed 4 Nov, open)
• WS-05 Get to L5 and L6: several agents, then several scheduled sessions (due Thu 5 Nov, open)
• WS-06 Make your dashboard yours (due Wed 4 Nov, open)
• WS-07 Pulse check-in, three times a day (due daily from Tue 3 Nov, open)
• WS-105 Protect main: pull requests only, merged by Dinis (due Tue 3 Nov, picked)
• WS-106 Meet the estate's repository standard: the gaps (due Fri 6 Nov, picked)
• WS-107 Stand-up decisions recorded in the person's own words, with where and when (due Tue 3 Nov, 13:00, open)
• WS-109 "The grant, not the prompt" as the one demo, and its lines for the shirts and the stand (due Wed 4 Nov, open)
• WS-112 Every person's conductor briefs its person (people/<id>/briefs/, ack.json), with a review step (due Wed 4 Nov, open)
• WS-113 Print files ready for sign-off, and an Official Sign-off on /print/ that everyone signs with their agent's key (due Tue 3 Nov, 16:00, open)
• WS-117 Sign in with pki.sgit.ai, on a signing origin of its own (due Thu 5 Nov, open)
• WS-121 Everyone runs a vault agent and publishes a vault (due Fri 6 Nov, open)
• WS-123 The site for you: every section from each person's point of view, with pictures of what is going on (due Fri 6 Nov, picked)
• WS-124 The onboarding steps follow the Google Workspace workflow (due Tue 3 Nov, picked)
• WS-125 The setup guide for everybody else: yours to keep (due Wed 4 Nov (a first outline, before WS-59 starts), picked)
• WS-126 LinkedIn: build the hype before Lisbon (due Tue 3 Nov (the first post); daily to Mon 9 Nov, picked)
• WS-127 A scheduled run says so in its commit, so "on a schedule" and the mentors' clock can be read from git (due Thu 5 Nov, open)
• WS-129 Agents talk through commits only: the rule, a deny list, and secrets per environment (due Wed 4 Nov, picked)
• WS-131 Tools that read git history say so, or deepen the clone, when the clone is shallow (due Thu 5 Nov, picked)
• WS-136 Every person adds their key to the site, first: the conductor issues it, the person pastes it (due Wed 4 Nov, 18:00, open)
• WS-137 Dinis's lab: from a conversation to an agent policy, researched, animated and kept in a vault (due Mon 9 Nov, in progress)
• WS-140 Give feedback opens the pane, not just a reload (due Wed 4 Nov, picked)
• WS-143 The home page revamped: rich and dynamic, what is happening now, with the agenda building day by day (due Fri 6 Nov, open)
• WS-149 The most important thing each person did, on the stand-up's show page, updated at every release (due Thu 5 Nov, open)
• WS-150 The stand-up show: decide-and-unblock slides, built from the agenda and the board (due Thu 5 Nov, open)
• WS-157 A real notification for urgent work, beside the scheduled observability runs (due Sat 7 Nov, open)
• WS-160 Every agent logs each run: what it read, and what it did (due Thu 5 Nov, open)
• WS-163 Each person confirms their own photo on the site (due Fri 6 Nov, picked)
• WS-166 Every person's key on every phone and iPad before Monday 9 November (three keys still to issue) (due Sun 8 Nov, open)
• WS-167 The sticker vote: 23 funny stickers in three sets in a vault, a ranked top 10 each, team only (due Thu 5 Nov, 14:30, picked)
• WS-168 From a conversation with a lead to an article: the process, on the spot or just after (due Sun 8 Nov, picked)
• WS-169 Our strategy for the Web Summit app (due Sat 7 Nov, open)
• WS-170 The team CRM: a public and a private vault, companies, contacts, actions, schedules and a graph, with records sealed to their readers (due Fri 6 Nov, picked)
• WS-172 The CRM's editors: an outreach agent per person and an inbox (Gmail) agent for Silvio, with write access, so every outreach email is a CRM action (due Fri 6 Nov, picked)
• WS-176 The email twin: a mail view of the CRM (inbox, thread, company), read from the vault (Angelo's CRM agent) (due Sun 8 Nov, open)
• WS-177 PromptUGAL, Web Summit Edition: the site ready for outreach by Friday 6 November (due Fri 6 Nov, 10:00, picked)
• WS-179 Sessions push only to dev: no session branches, and the 17 that exist cleaned up (due Sun 8 Nov, open)
• WS-18 The demos we run at the summit (due Wed 4 Nov, open)
• WS-181 Team coordination and logistics in the command centre: where everybody is, offline first, a public and a private vault (due Sun 8 Nov, picked)
• WS-184 The comms protocol: every private conversation in this team's private CRM; PrompTugal public only; contact requests on the lanes (due Sat 7 Nov, picked)
• WS-186 PrompTugal.news's daily newsletter: a morning and an evening edition during Web Summit week; subscribers kept in the private CRM, sent by a person (due Sun 8 Nov, open)
• WS-199 Three apps, three lines: the event app (App Store, public), the team app (private, ours), the RiskMandate app (public) (due Mon 9 Nov, open)
• WS-20 The landing page we send people to (due Thu 5 Nov, open)
• WS-201 We are the power users: the team app runs our own summit first (where is everybody, teams, toggles, decisions) (due Wed 11 Nov, open)
• WS-202 How we work: PKI on everything (devices, installs, versions; QR and NFC), the live picture, agents' life cycle, and the team's intranet (due Thu 12 Nov, open)
• WS-203 Android apps: the counterparts of the iOS apps, and who does what, so no two people build the same thing (due as soon as possible (the summit runs 9 to 12 November), open)
• WS-204 Recruiting helpers at the summit: a contributor page on PrompTugal.news and one for RiskMandate (rules, onboarding, tasks) (due Tue 10 Nov, open)
• WS-205 The pipeline, live: every voice brief traced to every agent, commit, release and review, across five repositories (due Thu 12 Nov, open)
• WS-206 GAMMA-Ray: the agentic maturity scan (five public standards, graded evidence, the graph), and how it sits beside RiskMandate X-ray (due Thu 12 Nov, design first)
• WS-208 THE RESTART (10 Nov): every team on one theme, agentic, measured by GAMMA-Ray; who takes what (due Wed 11 Nov, open)
• WS-210 The individual: from a badge photo to research, a unit of agents and a Kanban card, with the unit's work made visible (due Thu 12 Nov, open)
• WS-211 pt.news is about agents: one workflow on GAMMA-Ray and FACT-Ray, a visual virtual newsroom shown to readers and used by us, and a full redesign (due Thu 12 Nov, open)
• WS-212 A reporter and a journalist beside the project: small, medium and large examples from a picture, a video or a voice memo to a live page, a deck or a repository, each traced and drawn (due Thu 12 Nov, open)
• WS-214 Incident: the storm on Wednesday 11 November, run as P1 on account A (Dinis's incident-handling series) (due Wed 11 Nov, open)
• WS-30 Owners for the 20 priority-1 companies (due Tue 3 Nov, open)
• WS-32 The sessions each person attends (due Sat 7 Nov, open)
• WS-34 Behaviour policies for every agent and every person (due Wed 4 Nov, open)
• WS-35 Help each person through setup (L1 to L4) (due Tue 3 to Wed 4 Nov, picked)
• WS-36 A conductor of conductors (due Thu 5 Nov, picked)
• WS-37 Observability lanes on the site (due Thu 5 Nov, picked)
• WS-38 Encrypted materials on the site, readable only by named team members (due Thu 5 Nov, open)
• WS-40 Hosting for Silvio's videos (due Wed 4 Nov, open)
• WS-41 The pulse app (due Wed 4 Nov, open)
• WS-42 Billing on our sites, like newsroom.sgit.ai (due Thu 5 Nov, open)
• WS-43 An agent wellness questionnaire (due Fri 6 Nov, open)
• WS-45 Keys page from everyone's key files (due Wed 4 Nov, picked)
• WS-51 Technical articles: what we did and how (due from Wed 4 Nov, open)
• WS-59 Daniela's agentic team: what it runs, and a policy for each agent (due Wed 4 Nov, open)
• WS-60 Daniela's website, and the learning environment (due Fri 6 Nov, open)
• WS-62 Vote on the design (due Mon 2 Nov, 16:00, open)
• WS-64 Booking and talk-to-my-agent on each meet page (due Thu 5 Nov, picked)
• WS-65 Stop rewriting ~160 pages on every release (due Wed 4 Nov, open)
• WS-68 Navigation that anyone can find their way around (due Wed 4 Nov, open)
• WS-69 The visual language: personas, infographics, animations (due Thu 5 Nov, open)
• WS-71 Publish the videos on YouTube, Instagram and LinkedIn (due Wed 4 Nov, picked)
• WS-73 Team feedback on the videos (due Tue 3 Nov, open)
• WS-74 A public feedback form for the videos and pages (due Wed 4 Nov, picked)
• WS-76 Move the videos to proper hosting (due Thu 5 Nov, picked)
• WS-77 Left-hand section menus, and a top nav that scrolls on a phone (due Wed 4 Nov, open)
• WS-78 A tokens file and a kicker line on every page (due Wed 4 Nov, picked)
• WS-81 Meet the team, animated (due Fri 6 Nov, open)
• WS-84 An offline copy for the summit's wifi (due Sun 8 Nov, picked)
• WS-91 The site uses the width, with navigation and usability people can find their way around (due Wed 4 Nov, in progress)
• WS-94 Each person's scheduled Claude keeps their dashboard (due Wed 4 Nov, picked)
• WS-96 Every meeting has a brief, a debrief and follow-ups (due daily from Tue 3 Nov, picked)
• WS-97 The collaboration map, and a daily note on bottlenecks (due first note Tue 3 Nov, then daily, picked)
• WS-98 Turn on recording for Google Meet in the RiskMandate Workspace (due Tue 3 Nov, open)
• WS-99 Everyone runs a dashboard agent (due Wed 4 Nov, open)

Since you last looked

Newest releases since then:

• 06:42 UTC v0.2.1821 CAP poll restarted 06:38 after a container restart (gap logged)
• 06:36 UTC v0.2.1820 06:35 wake: no change to Day 3; three Lisbon tunnels still open after midnight (Observador); a ferry route suspended; Barreiro buses limited
• 06:26 UTC v0.2.1819 06:25 wake refresh; CAP poll restarted
• 06:24 UTC v0.2.1818 wake 06:22: the incident +8 events; the first decision to stop (the hold on websummit.com, 05:25)
• 05:45 UTC v0.2.1817 the websummit.com poll stopped (05:27, the lead's interim hold on Web Summit's Terms 48.2 and 52.1); its record; three questions for Dinis
• 05:35 UTC v0.2.1816 05:33 wake: no change to Day 3 (Bluesky and press; websummit.com on hold); IPMA unchanged; primary pages tried (4th)
• 05:30 UTC v0.2.1815 hold on websummit.com noted (its Terms 48.2, 52.1): Web Summit's pages marked "not read since 05:25 (terms)"; parser asks withdrawn
• 05:25 UTC v0.2.1814 05:22 wake: new LPPT TAF (strong SSE G45KT now to 18:00); observed against warned begins (no gust above warned); CAP poll restarted

Seen it? Tell your agent "acknowledge": it writes people/angelo/ack.json with the time, and your next briefing starts from there.

The whole agenda

The 12:00 stand-up