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

Your briefing for the 2026-11-11 12:00 stand-up, Indi. 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
• 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
• 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 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
• 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
• 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

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-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-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-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-144 designer@web-summit.indi writes in team/designer/ and content/, and is not in Indi's agents.json (due Thu 5 Nov, open)
• WS-148 An accountant agent for Indi's agents: every agent measures its tokens, and the accountant finds the savings (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-155 The business cards and stickers, ordered from ProntaPrint Chiswick for Friday 6 November (due Thu 5 Nov, 09:00, 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-171 Two landscape infographics: how RiskMandate works, in plain terms (due Fri 6 Nov, open)
• 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-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-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-208 THE RESTART (10 Nov): every team on one theme, agentic, measured by GAMMA-Ray; who takes what (due Wed 11 Nov, open)
• WS-209 RiskMandate for education and children: talk with Dinis, find the people at Web Summit, publish the idea (due Thu 12 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-22 Messaging review across everything we publish (due from Wed 4 Nov, open)
• WS-26 The big outreach: 50 targets for Thursday and Friday (due Thu 5 Nov, picked)
• WS-27 The factory: a page or vault per target company (due from Thu 5 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-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-69 The visual language: personas, infographics, animations (due Thu 5 Nov, open)
• WS-73 Team feedback on the videos (due Tue 3 Nov, open)
• WS-79 The home page as a hero and bands (due Thu 5 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:

• 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
• 04:36 UTC v0.2.1813 04:33 wake: no change to Day 3; IPMA unchanged; primary pages tried (3rd), none published
• 04:26 UTC v0.2.1812 04:23 wake refresh; CAP poll restarted
• 04:15 UTC v0.2.1811 area on every decision edge (lisbon, mainland, madeira, porto-santo, national)
• 03:52 UTC v0.2.1810 Madeira's 71 occurrences to 02:00 (SRPC's press platform via DN Madeira: evidence); Porto Santo's measures not found at source; entities/madeira.json
• 03:44 UTC v0.2.1809 Jose's example (a one-word yes to a GAMMA-Ray scan of 13 agents), and the pictures' version numbers restored
• 03:33 UTC v0.2.1808 03:33 wake: no change to Day 3; primary pages tried again (none published)
• 03:26 UTC v0.2.1807 03:23 wake refresh; token measure refused by the session's permission check (Dinis: ask in status)

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

The whole agenda

The 12:00 stand-up