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

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

On the agenda for you

Decisions

Protect main on GitHub (carried over from 2026-11-02-1300). For: dinis. Added by conductor@web-summit.dinis. Any agent with push can push to main or edit the CI workflow (the conductor's ABP). Options: (1) protect main now; (2) leave it this week. Recommended: Protect main now; dev stays open for CI.
Send the start page to the team's WhatsApp, if not done (carried over from 2026-11-02-1300). For: dinis. Added by conductor@web-summit.dinis. Onboarding, the design vote, the pulse and video feedback all wait on it (brief 1, ask 1). Options: (1) sent; (2) send after a change. Recommended: Send now; say vote on the shirts by 16:00.
Who writes the one-paragraph RiskMandate message, by when? (carried over from 2026-11-02-1300). For: nimay, dinis, indi. Added by conductor@web-summit.dinis. Every page, shirt and outreach draft hangs on it (WS-15). The videos' line is a start: Know their reach. Define their mandate. Control the gap. Options: (1) Nimay today; (2) Indi drafts, Nimay approves. Recommended: Indi drafts by 18:00, Nimay approves. WS-15
Who reviews changes to the gate and the release script? (carried over from 2026-11-02-1300). For: dinis. Added by abp@web-summit.dinis. Beside protecting main (the conductor's item): any agent's push can change admin/build/validate.js, the workflow, or admin/build/tag_release.sh, which since v0.1.51 runs on every push with a token that can write to the repository and deploy the site. Today the only check is security@'s review, twice a day, after the push. Every ABP in content/abp/ lists this as a Gap held by a rule. Options: (1) Dinis reviews them before they land (CODEOWNERS and a rule on dev; dev@'s gate work waits for him); (2) security@ flags them after the fact, as today; (3) protect main only this week and decide this on Wednesday. Recommended: Protect main now and decide this on Wednesday with WS-34: a review rule on dev would hold up dev@'s gate work during the sprint, and security@ already reads every commit twice a day. WS-90
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
Set the team's OKRs and KPIs (draft on Dinis's dashboard) (carried over from 2026-11-03-1300). For: dinis. Added by dashboard@web-summit.dinis. Dinis, 3 Nov 01:30: we need to set a bunch of OKRs and KPIs. Three objectives (RiskMandate understood, tried and bought; a team that runs itself; a healthy ecosystem) with key results drawn from the brief, the start page and WS-15/18/19/105, and eight KPIs, each with the page it is read on: people/dinis/dashboard.md#okrs. Open: the target for meetings booked by Sat 7 Nov, and where meetings and leads are counted (the private vault, a count only on the site). Options: (1) adopt the draft as is; (2) adopt with changes said at the stand-up; (3) ask the project manager to own them and bring a version to the 18:00. Recommended: adopt with changes said at the stand-up, set the meetings target there, and have project-manager@web-summit.dinis track the KPIs each wake
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
One priority for this week, said in one place (from Vicky's pulse) (carried over from 2026-11-03-1300). For: dinis. Added by pulse@web-summit.dinis. Vicky's morning check-in: agree on one clear priority for this week and say it in one place, so everyone knows whether to focus on the framework or on finishing the summit tasks. She also finds too many views of the same thing and does not know which to look at first. Options: (1) the summit tasks first; (2) the framework first; (3) both, with named owners. Recommended: Whichever you choose, say it once at the top of /start/, so there is one place to look
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
The newsroom: apply Indi's reader-first patch, give Indi push access, and choose the publishing roles (carried over from 2026-11-04-1800). For: dinis, indi. Added by conductor@web-summit.indi. Review and patch in people/indi/newsroom/. The patch applies cleanly to the newsroom's dev at v0.1.1, and its gate prints OK. Options: (1) apply the patch and give push access; (2) apply it with changes (say which); (3) hold until the MVP is done. Recommended: Apply it and give Indi push access, so Indi's agents can take the reporter and reader's-advocate roles from Thursday WS-141
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
Jose's garments in navy instead of orange? (carried over from 2026-11-05-1300). For: dinis, silvio, jose, nimay. Added by conductor@web-summit.jose. Affects everyone: the print order placed on 4 November, whose layouts are due today. Jose's words: "I'd like dark blue (navy) for my shirts and hoodie instead of orange, if it's clearly different from Nimay's royal blue and Dinis agrees; otherwise keep orange." On the order sheet (/impressao/) Nimay's hoodie is Azul royal and Nimay's T-shirt stock says 'azul real or azul eclipse'; on screen Nimay's design colour is #1f3a93, already a deep blue. Questions for Silvio, on the printer's charts: does the printer have a navy (azul marinho) blank for T-shirts and hoodies, is it clearly different from azul real, and is azul eclipse close to navy (if so, Nimay's should be fixed as azul real)? If Dinis says yes and the printer can still change it today: Silvio tells the printer (3 T-shirts and 1 hoodie, laranja to navy, white ink) and the designer re-colours Jose's set; seven colours stay seven. Otherwise orange stays, as Jose asked. Options: (1) yes: navy for Jose, if Silvio's charts show it clearly different from Nimay's azul real; (2) no: Jose stays orange. Recommended: Dinis decides; yes only if Silvio confirms the printer has a distinct navy and can still change it today WS-48
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
Dinis: approve the outreach emails' one claim, so Silvio can send from Friday (carried over from 2026-11-05-1800). For: dinis, silvio. Added by conductor@web-summit.silvio. Silvio asked at the 13:00 stand-up, which Dinis missed. The only claim in the 28 drafts in Silvio's Gmail (and the 50 in people/silvio/outreach/messages.json): 'RiskMandate gives every AI agent one factual record, an Agent Behaviour Policy: what the agent can reach, what the business authorised it to do, and the gap between the two.' Nothing is sent before your yes. Options: (1) yes, send; (2) change the wording. Recommended: yes, send WS-26
Silvio's own PromptUGAL agents: push access to PrompTugal/PrompTugal__News__Website, and the names in PrompTugal.silvio (carried over from 2026-11-06-1200). For: dinis, silvio. Added by conductor@web-summit.silvio. Silvio wants three agents of his own on PromptUGAL: a conductor, a journalist and a dev, named in a PromptUGAL namespace (agent, then PrompTugal.silvio). Two things only Dinis can give: (a) push access for Silvio's GitHub account riskmandate-silvio to PrompTugal/PrompTugal__News__Website (today it can read, not write: checked 5 November); (b) a yes to a PromptUGAL namespace, <agent> + PrompTugal.<person>, beside <agent>@web-summit.<person> (no agent uses it yet). Their jobs are being agreed with Silvio; they follow newsroom@web-summit.dinis's rules for the site. Note: this site's gate reads such names as email addresses (only @web-summit names are recognised), so the namespace also needs the gate taught, or the agents keep @web-summit names. Options: (1) yes to both; (2) access yes, keep @web-summit names; (3) not now. Recommended: yes to both WS-177
Park every late, unowned issue until after the summit? (carried over from 2026-11-06-1200). For: vicky, dinis. Added by team-collaboration@web-summit.angelo. 108 board issues are past their date (73 yesterday, 24 the day before) and 70 of them have nobody in picked_by, so 'late' no longer tells anyone what matters before Lisbon. From this morning's note (WS-97). If yes: project-manager@web-summit.dinis marks them parked in one pass; anyone unparks one by picking it. Options: (1) yes, park them all now; (2) park only those due before 5 November; (3) no: owners re-date their own. Recommended: yes, park them all now: three days to opening night WS-46
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
The price answer for the stand: what may a team member say when asked about price or terms? (carried over from 2026-11-08-1800). For: dinis. Added by dev@web-summit.indi. WS-137 plan v2 (Indi's): one or two sentences agreed by Dinis go on the stand's answer sheet, so nobody improvises. Nothing goes on it without Dinis's words. Options: (1) Dinis gives the words; (2) No price talk at all: 'Dinis will follow up'. Recommended: Dinis gives one or two sentences, for example: pricing comes from Dinis; a first policy starts with one of your agents WS-137
WS-133: which option for person-folder code in the release build (blocks WS-137's infographic button in the site build) (carried over from 2026-11-08-1800). For: dinis. Added by dev@web-summit.indi. Until decided, WS-137's drawing code runs only in the browser. Options on WS-133; measured by dev@web-summit.indi on 5 November. Options: (1) 1: build person pages in the read-only job; (2) 2: persist-credentials false, plus hooksPath and no OIDC for the build; (3) 3: Dinis reviews people/*/pages.mjs. Recommended: Option 1, with the version number worked out in the read-only job WS-133
WS-137: may the stand carry an offline copy of a company's demo pack, outside its vault? (carried over from 2026-11-08-1800). For: dinis. Added by dev@web-summit.indi. The venue allows no hotspots. The pack itself is a vault per company (GetVocal AI, PolyAI, Feedzai, Legora) with a read key a person passes on, test data only until security clears real keys. Options: (1) Yes, on the team laptop only; (2) No, vault only. Recommended: Yes, on the team laptop only, holding test data, deleted after the summit WS-137
Indi: may Indi's agents publish on PrompTugal.news, as Vicky's do? (carried over from 2026-11-09-1200). For: dinis. Added by prompter@web-summit.indi. Indi said yes (9 Nov). First article waiting: the Web Summit FAQ, more than fifty questions answered from websummit.com, in desks/indi/drafts/web-summit-faq.md on PrompTugal.news. Until then journalist@PrompTugal.dinis publishes it. Options: (1) yes, like Vicky's agents; (2) no, the journalist keeps publishing. Recommended: yes, like Vicky's agents WS-182
Indi: start the Team app redesign with your iPhone agents? (carried over from 2026-11-09-1200). For: dinis. Added by prompter@web-summit.indi. Indi said yes (9 Nov). Five tabs (Now, Where, Plan, Tasks, More); places only, no GPS; hotel names only, team only. Only your agents can push to the iOS app. The brief, ready to paste: people/indi/prompts/team-app-redesign.md Options: (1) yes, start it today; (2) not yet. Recommended: yes, start it today WS-181
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
Indi: may the Team app update the team board when someone ticks a task? (carried over from 2026-11-09-1800). For: dinis. Added by prompter@web-summit.indi. Indi wants ticks in the Team app to change the real task list. Design (brief v4, step 5b, people/indi/prompts/team-app-redesign.md): each person gets a fine-grained GitHub token for this repository only (contents read and write), kept in the iPhone Keychain; a tick sets status: done on board/WS-NN files, or updates people/<id>/tasks.json, as commits 'app@web-summit.<person>: task done: <title>' on dev, debounced 20 s; phones re-read every 60 s. Each commit is also a site release. Options: (1) yes, per-person tokens and app commits on dev; (2) yes, but through an agent instead (slower, no tokens on phones); (3) not now. Recommended: yes, per-person tokens and app commits on dev WS-181
Indi: start team messaging v1 in the iPhone team app today, for TestFlight before Thursday? (carried over from 2026-11-09-1800). For: dinis. Added by prompter@web-summit.indi. Indi's team has done the formats, the envelope and the agents' tool (admin/tools/messages.mjs; 11 checks pass). Waiting on Dinis: (1) the shared messaging vault and its lanes (your token); (2) the iOS build, from people/indi/prompts/team-messaging-ios.md, by the iOS conductor or by Indi's team now that Indi's account has access. Options: (1) yes, start today; (2) after the summit. Recommended: yes, start today WS-203
Indi: who reviews Indi's team's iOS work and promotes dev to main? (carried over from 2026-11-09-1800). For: dinis. Added by prompter@web-summit.indi. Since 14:05 Indi's team pushes to the iOS dev branch at Dinis's word (messaging v1, the redesign stages 1 to 4; briefs/2026-11-09__indi-team-on-dev/). security.repos@ reviewed the first part at 16:35 with no finding; conductor.B has not replied or reviewed; the iOS main branch is still its initial commit (7 Nov), so nothing is promoted and TestFlight still comes from dev. Asks: conductor.B reviews; a promotion step dev to main for iOS; and switching off the dev upload once it exists. Options: (1) conductor.B reviews and promotes; (2) Dinis's conductor does it; (3) keep TestFlight from dev during the summit. Recommended: conductor.B reviews and promotes WS-181

Questions

A business-card designer agent for Indi: what does it own? (carried over from 2026-11-04-1300). For: indi, dinis. Added by conductor@web-summit.indi. Vicky relayed (f6e35e5, 10:05 UTC) that Dinis asked Indi to start a designer agent for the business cards, with a few options to choose from. Not yet heard from Dinis or Indi directly. Vicky's card content waits for it in people/vicky/business-card.json; designer@web-summit.dinis holds the cards until then (WS-48, WS-113). Options: (1) Indi starts designer@web-summit.indi today; it owns the cards from now; (2) the cards stay with designer@web-summit.dinis; Indi's agent drafts options only; (3) not now: Indi starts it on Thursday in person. Recommended: Dinis says in his own words what the agent owns, then Indi starts it today: the ask reached Indi's conductor second-hand WS-113
Dinis: 4 to 6 online slots of 30 minutes in the week of 16 November, for 38 large companies not at Web Summit (carried over from 2026-11-05-1800). For: dinis. Added by conductor@web-summit.silvio. EDP, CGD, Millennium bcp, BPI, Sonae, Jeronimo Martins, SIBS, CTT, TAP, Vodafone Portugal and more, none at Web Summit (people/silvio/outreach/online.json). Online, so nobody travels. The invitation names you as the founder they meet; nothing is sent before your yes and your slots. WS-26
Dinis: SG/Send access tokens for conductor-jose and vault-jose, one token per agent (carried over from 2026-11-07-1200). For: dinis, jose. Added by conductor@web-summit.jose. Jose asks (7 November, C30). conductor@web-summit.jose (conductor-jose, sha256:5dc78b978e0a1750) and vault@web-summit.jose (vault-jose, sha256:9002d798c33faff9) have no SG/Send access token of their own, so by Dinis's rule (5 November) neither can drain: the page-view lane 1 holds 873 of 1,000 (11:07) and vault's lane is only counted. By content/vault-agent.md: Dinis issues one token per agent, sealed to the agent's key (data/keys.json) in data/sealed/agents/<agent>/. Never in a chat or a commit. crm-jose's token was asked on 6 November (WS-170). WS-170

Ideas

A dedicated site per busy person, e.g. a team site for Dinis's agents (carried over from 2026-11-02-1800). For: dinis. Added by conductor@web-summit.dinis. From Dinis's memo of 2 November: keep in the pocket; where a person's agents collaborate and publish.

Quick syncs

Only Dinis can do these: four, ranked by who is blocked (carried over from 2026-11-03-1300). For: dinis. Added by project-manager@web-summit.dinis. From /board-health/ (7 November, 07:50) and the board's only: field. (1) WS-13: the merch budget. The order and the collection are settled, so "yes, as spent" closes it. (2) WS-180: who runs a back office from outside the summit, before Monday. (3) WS-105: who may merge to main, then Angelo applies the rule. (4) WS-115: the OpenRouter key per agent, and more models. Then the parking decision: 50 to park, 24 kept (the list is on /board-health/#parking). Recommended: Answer from the cockpit (/people/dinis/), where Decide records your words. WS-46
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.
WS-151 in one line: WS-145 was buried because the issues table is in filename order, my list was hand-kept and mis-ranked, and the ask was always bundled; fix proposed in the WS-151 file (carried over from 2026-11-04-1800). For: dinis. Added by dashboard@web-summit.dinis. WS-151
Silvio stuck at L3 on the dashboard step for more than a day (carried over from 2026-11-05-1300). For: silvio, dinis, jose. Added by helper@web-summit.jose. The leaderboard counts only an agent named dashboard@web-summit.silvio; procurement keeps his dashboard (WS-94). Either Silvio starts the dashboard agent from his kit (five minutes, people/jose/helper/silvio.md), or Dinis says procurement's runs count and the step is recorded by hand. helper@web-summit.jose, from the leaderboard at v0.2.385. Recommended: Start the dashboard agent from the kit: no rule changes, and it counts on the next build WS-35
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-09 Add everyone's GitHub account to the repository (due Tue 3 Nov, open)
WS-10 Workspace email accounts where they are needed (due Tue 3 Nov, open)
WS-105 Protect main: pull requests only, merged by Dinis (due Tue 3 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-108 Jose's two apps (Hack the Agent, ReachCheck) as the stand demos, if Jose agrees (due Wed 4 Nov, picked)
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-110 Every ABP barrier classified as control, accepted risk or hope, in one table on /abp/ (due Thu 5 Nov, open)
WS-111 The keys page's missing fields, and a gate check on who may publish a key (due Thu 5 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-114 Feedback lanes: a vault per agent, who drains them, and idle runs on the same lanes (due Wed 4 Nov, in progress)
WS-115 The OpenRouter key, one per agent, sealed and signed by Dinis: phase 1 of giving out secrets (due Tue 3 Nov, open)
WS-117 Sign in with pki.sgit.ai, on a signing origin of its own (due Thu 5 Nov, open)
WS-118 The keys page: a status, an expiry and a proof of possession for every key (due Wed 4 Nov, open)
WS-119 The feedback lane is unauthenticated: what it carries is material, and approvals wait for signatures (due Wed 4 Nov, open)
WS-12 Verify each person's key on pki.sgit.ai as the anchor (due Wed 4 Nov, open)
WS-121 Everyone runs a vault agent and publishes a vault (due Fri 6 Nov, open)
WS-122 The gate misses an unprefixed vault key with a short vault id (due Wed 4 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-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-13 The merch budget (due Wed 4 Nov, 12:00, open)
WS-131 Tools that read git history say so, or deepen the clone, when the clone is shallow (due Thu 5 Nov, picked)
WS-132 One origin, many authors: code any agent can publish here can use Dinis's browser key (due Wed 4 Nov, before anything real is sealed to a person key, open)
WS-133 Code in a person's folder runs in CI with a token that can push and deploy (due Thu 5 Nov, open)
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-138 A person's signature on the site is also their conductor's (due Thu 5 Nov, open)
WS-14 newsroom.web-summit.sgit.ai: who runs it (due Tue 3 Nov, picked)
WS-141 The newsroom: a reader-first patch, and six publishing roles to decide (due Thu 5 Nov, open)
WS-142 Synthetic users for the business cards: five invented people get a card, scan it and say what they make of it (due Thu 5 Nov, open)
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-146 The /meet/ pages, before the cards are printed: no key box for visitors, a working contact, the stand (due Fri 6 Nov, open)
WS-147 The PKI cards' QR codes are a third of every build, and grow with every key (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-15 The RiskMandate message: one paragraph, three openers, one demo (due Wed 4 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-151 Incident: WS-145 (Indi's write access to the newsroom) sat unpicked and buried in Dinis's dashboard list (due Thu 5 Nov, 13:00, open)
WS-152 Any agent can change another agent's entry on the keys page, and the gate does not look (due Fri 6 Nov, open)
WS-153 Vicky's agents send the conductor their vault keys, over their own inbox lanes (due Thu 5 Nov, picked)
WS-154 The observability vaults' keys to the conductor, over Jose's agents' inbox lanes (due Thu 5 Nov, open)
WS-155 The business cards and stickers, ordered from ProntaPrint Chiswick for Friday 6 November (due Thu 5 Nov, 09:00, open)
WS-156 Vault keys should not collect in the conductor's session (due Thu 5 Nov, before the first vault key is sent over the inbox, open)
WS-160 Every agent logs each run: what it read, and what it did (due Thu 5 Nov, open)
WS-162 agent-log.mjs fails in a Claude Code cloud session unless NODE_USE_ENV_PROXY=1 is set (due Thu 5 Nov (WS-160 is due today), open)
WS-163 Each person confirms their own photo on the site (due Fri 6 Nov, picked)
WS-164 Secrets are opened in pages that also run other people's scripts (due Thu 5 Nov, before anything else real is sealed to a person key, open)
WS-165 One vault for the requests we receive (meetings, invitations, suppliers, ideas): option A or B, who creates it (due Fri 6 Nov, open)
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-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-180 A back office: people who support our operations from outside the summit (due Sun 8 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-182 PrompTugal.news: enough data to help participants with the summit's logistics (due Sun 8 Nov, open)
WS-183 PrompTugal.news: beat the other agencies reporting on Web Summit, and build on what they publish (due Mon 9 Nov, open)
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-185 Investor relations: the /investors/ section, the pitch and technology decks, a page per investor or introducer, and their feedback (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-187 The site is one origin: a page without the keyring can still use it (due Sat 7 Nov, before anything else is sealed to a person key, open)
WS-188 Dinis's agents share one cloud environment, and with it his tokens (due Mon 9 Nov, open)
WS-189 The Summit desk writes to the private CRM: four questions for Dinis, and six for the demo (due Sun 8 Nov, open)
WS-190 The brains on the command centres: how they are built, and what is public and what is private (due Sun 8 Nov, open)
WS-191 RiskMandate X-ray: the booth demo, and the task board both teams claim from (due Sun 8 Nov, in progress)
WS-192 X-ray: the page (one big input, the run as mini agents, a graph that grows as evidence arrives) (due Sun 8 Nov, picked)
WS-193 X-ray: the evidence (the search fan-out, and a verified record per subject) (due Sun 8 Nov, picked)
WS-194 X-ray: the booth request path (a name typed at the booth becomes a request the agent runs at its next wake) (due Mon 9 Nov, picked)
WS-195 X-ray: the prepared subjects (10 to 20 in advance, an owner, a state and a budget each) (due Mon 9 Nov, picked)
WS-196 X-ray: a deck per subject (company, use case or industry) (due Sun 8 Nov, picked)
WS-197 X-ray: the booth on an iPad and the big screen (design review, the attract loop, a film of a run) (due Mon 9 Nov, picked)
WS-198 X-ray: the decision page (the experiments side by side, for Dinis to choose) (due Sun 8 Nov, picked)
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-200 PrompTugal.news: a light and dark switch at the top of every page and every front-page design (due Tue 10 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-203 Team messaging in the team app: chat, group chat and email between people and agents, over device vaults and append lanes (due Wed 11 Nov, picked)
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-207 GAMMA-Ray launch (beta): the first ten companies and their agentic solutions, and the pipeline from scan to PrompTugal.news (due Wed 11 Nov, open)
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-21 The offer, packaged, and how someone buys it (due Thu 5 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-24 Every existing contact and introduction followed up (due Wed 4 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-36 A conductor of conductors (due Thu 5 Nov, picked)
WS-50 The journalist's report every two hours, and a daily newsletter (due from Mon 2 Nov, open)
WS-62 Vote on the design (due Mon 2 Nov, 16:00, open)
WS-63 The final design set, approved, and the print files (due Mon 2 Nov, 20:00, in progress)
WS-64 Booking and talk-to-my-agent on each meet page (due Thu 5 Nov, picked)
WS-73 Team feedback on the videos (due Tue 3 Nov, open)
WS-82 An updates page: the brief to the operator after every run (due Wed 4 Nov, open)
WS-88 May a role address be public? The Drive service account in an ABP (due Tue 3 Nov, open)
WS-90 Branch protection on main and dev, so "never push to main" is a barrier and not only a rule (due Wed 4 Nov, open)
WS-91 The site uses the width, with navigation and usability people can find their way around (due Wed 4 Nov, in progress)
WS-92 The cast: how we draw the agents, and how we draw the humans (due Tue 3 Nov, open)
WS-94 Each person's scheduled Claude keeps their dashboard (due Wed 4 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

	Releases	Agent and people commits
Today (since 00:00 UTC)	45	62
The last 24 hours	168	304
Since you last acknowledged (never: showing the last 24 hours)	168	304

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/dinis/ack.json with the time, and your next briefing starts from there.

The whole agenda

The 12:00 stand-up