Jose's briefing: stand-up 2026-11-03 13:00
Your briefing for the 2026-11-03 13:00 stand-up, Jose. Read it before; the stand-up is for deciding, not for reporting.
On the agenda for you
Decisions
- Who records the decisions during each stand-up (carried over from 2026-11-02-1800). For: everyone. Added by team-collaboration@web-summit.angelo. No decision was recorded at the 13:00 stand-up on 2 November. A debrief within the hour (WS-96) needs one person to say the decision out loud and one agent to record it. Options: (1) the chair records it; (2) team-collaboration@web-summit.angelo drafts it from the chair's words and the chair confirms; (3) each decider records their own. Recommended: team-collaboration@web-summit.angelo drafts it; the chair confirms in one line WS-96
- Nimay, Jose and Indi are all at the push step: the invitations (WS-09). For: dinis, nimay, jose, indi. Added by mentor@web-summit.dinis. Three of the six stop at the same step, Can push (L1, 3 of 9 on /team/setup/). That is a hand-off to fix once, not three notes. A suggestion: each person could say whether the GitHub invitation has arrived (and share their username if the team still needs it), and Dinis could send any missing invitations. Options: (1) settle it at the stand-up, two minutes each; (2) Dinis sends the invitations before the stand-up and the three accept them. Recommended: Dinis sends the invitations before the stand-up and the three accept them WS-09
- Jose's GitHub account on the roster, so his agents' keys can be sealed to (L6). For: jose, dinis. Added by conductor@web-summit.jose. Jose asked (3 November, about 01:00 UTC) for riskmandate-jose to be added to data/team.json for jose. His two agent keys (conductor-jose, dashboard-jose) were pushed by riskmandate-jose, but the roster lists no GitHub account for him, so seal.mjs refuses them and he cannot reach L6. WS-106 leaves the roster change to conductor@web-summit.dinis once Dinis confirms the account is Jose's; Jose's conductor has not written it itself, since an account adding itself to the roster is the very check WS-106 exists for. Options: (1) Dinis confirms, and conductor@web-summit.dinis adds riskmandate-jose to the roster; (2) Jose reads his agents' fingerprints to the sealer out of band (--fingerprint) instead. Recommended: Dinis confirms riskmandate-jose before the stand-up and his conductor adds it; Vicky's account (riskmandate-vicky) is in the same position and could go in the same change WS-106
Quick syncs
- Where is everyone on connecting (levels L0 to L4)? (carried over from 2026-11-02-1300). For: everyone. Added by conductor@web-summit.dinis. One person of nine past L0 at 04:31. Say what blocks you; Angelo and Jose help (WS-35). WS-01
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-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-08 Fill in your card (due 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-108 Jose's two apps (Hack the Agent, ReachCheck) as the stand demos, if Jose agrees (due Wed 4 Nov, 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-120 Vaults, first through: Angelo, Jose and Silvio start a vault agent, make a vault and publish it (due Wed 4 Nov, open)
- WS-18 The demos we run at the summit (due Wed 4 Nov, open)
- WS-30 Owners for the 20 priority-1 companies (due Tue 3 Nov, open)
- WS-33 Make the repository safe for everyone to commit to all the time (due Tue 3 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, open)
- WS-39 A WhatsApp number in the team group, and the RiskMandate Slack (due Wed 4 Nov, picked)
- WS-40 Hosting for Silvio's videos (due Wed 4 Nov, open)
- WS-41 The pulse app (due Wed 4 Nov, open)
- WS-45 Keys page from everyone's key files (due Wed 4 Nov, open)
- WS-55 Everyone's shirt and hoodie: size, colour, message (due Mon 2 Nov, open)
- WS-62 Vote on the design (due Mon 2 Nov, 16:00, open)
- 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-71 Publish the videos on YouTube, Instagram and LinkedIn (due Wed 4 Nov, open)
- 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, open)
- 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, 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-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
| Releases | Agent and people commits | |
|---|---|---|
| Today (since 00:00 UTC) | 43 | 61 |
| The last 24 hours | 97 | 127 |
| Since you last acknowledged (never: showing the last 24 hours) | 97 | 127 |
Newest releases since then:
- 04:52 UTC v0.2.46 vaults outside the repository clone, .sg_vault/ ignored, one name for the access token
- 04:14 UTC v0.2.45 ABPs for six more agents (Jose's four, sgit@silvio, dashboard@dinis); dev's feedback lane
- 03:43 UTC v0.2.44 the gate checks me.json: its shape, its links, and no contact detail (WS-123, item 3)
- 02:59 UTC v0.2.43 the 02:57 report, and 'What happened' updated
- 02:56 UTC v0.2.42 the access token is server access only; the vault key is the encryption
- 02:52 UTC v0.2.41 decisions blocking Dinis first, the agents second, one click between them
- 02:39 UTC v0.2.40 your vault agent: the guide for everyone to create, publish and share vaults; WS-106 settled; Vicky's and Jose's accounts on the roster
- 02:37 UTC v0.2.39 how every one of Silvio's agents creates and uses a vault (people/silvio/kit/vaults.md)
Seen it? Tell your agent "acknowledge": it writes people/jose/ack.json with the time, and your next briefing starts from there.