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

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

On the agenda for you

Decisions

• 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
• 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
• 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
• The first five companies (WS-25): Nimay proposes five, Silvio adds the Algarve and Portuguese ones (carried over from 2026-11-04-1300). For: silvio, nimay, vicky. Added by procurement@web-summit.silvio. Silvio, 3 November: to this stand-up. Silvio owns Algarve and Portuguese companies, and anyone who asks how we run our agents. WS-25
• 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
• 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

Questions

• Which target company gets the first worked ABP? (carried over from 2026-11-04-1300). For: indi, nimay. Added by abp@web-summit.dinis. abp@web-summit.dinis's section: one worked ABP per target company in the factory (WS-27), once Nimay or Indi names the company. The factory has 28 'meet' companies (people/indi/factory/). Name one or three to start, and where it should live (the company's factory page, or content/abp/). Recommended: Start with one whose agents act for its customers and whose public docs say what they can do, so the Reach can be sourced, not guessed. WS-27

Quick syncs

• 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-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-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-126 LinkedIn: build the hype before Lisbon (due Tue 3 Nov (the first post); daily to Mon 9 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-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-15 The RiskMandate message: one paragraph, three openers, one demo (due Wed 4 Nov, open)
• WS-16 Positioning content for the site (due Wed 4 Nov, open)
• WS-160 Every agent logs each run: what it read, and what it did (due Thu 5 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-18 The demos we run at the summit (due Wed 4 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-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-19 The card-to-analysis loop, tried on three companies (due Wed 4 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-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-25 The first five companies (due Wed 4 Nov, picked)
• WS-28 Who can connect the dots (due Fri 6 Nov, open)
• WS-29 Hot leads go to Nimay or Dinis (due Wed 4 Nov, picked)
• 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-56 The shirt messages: RiskMandate openers (due Mon 2 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-66 The positioning text on the meet pages (due Wed 4 Nov, open)
• WS-73 Team feedback on the videos (due Tue 3 Nov, open)
• WS-94 Each person's scheduled Claude keeps their dashboard (due Wed 4 Nov, picked)
• 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/nimay/ack.json with the time, and your next briefing starts from there.

The whole agenda

The 12:00 stand-up