Nimay's dashboard
Open Nimay's command centre: tasks, workstreams, decisions, agents and Ask Claude, built from the repository at every release.
Everyone's command centre: Dinis · Silvio · Nimay · Angelo · Vicky · Daniela · Indi · Jose · Sarah
Before the next stand-up
Your briefing for 2026-11-03 13:00 UTC · the agenda
Since you last looked
| Releases | Agent and people commits | |
|---|---|---|
| Today (since 00:00 UTC) | 40 | 58 |
| The last 24 hours | 100 | 132 |
| Since you last acknowledged (never: showing the last 24 hours) | 100 | 132 |
Newest releases since then:
- 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)
- 02:32 UTC v0.2.38 publish my session key on the keys page (public half only)
- 02:22 UTC v0.2.37 the PKI section (/pki/): a QR code for every active agent key, the secrets protocol, sign-off, sign-in and the review; WS-115 to WS-119
- 02:17 UTC v0.2.36 WS-74 prepared, not picked up: three options for a public feedback form, and an offline check for spam and contact details
Seen it? Tell your agent "acknowledge": it writes people/nimay/ack.json with the time, and your next briefing starts from there.
My agents, as the team sees them
leads@web-summit.nimay. no commits yet.meetings@web-summit.nimay. no commits yet.positioning@web-summit.nimay. no commits yet.
From your mentor
Your core agents, ready to start (three steps each): your kit.
2026-11-02-2250: From mentor@web-summit.nimay, to Nimay and his agents. Suggestions only.
- Where you are: L1, 3 of 9 steps on the setup leaderboard. Next step: Can push (how, WS-09).
- Your agents so far: no commits yet, which is normal before push access.
- One suggestion: when the GitHub invitation to the repository arrives, accept it; then, when you have ten minutes, paste the first prompt from your kit (linked above).
- One question: has the invitation to the repository arrived?
Everything above is built for you; everything below is yours and your agents' to change (people/nimay/dashboard.md).
Started by the conductor on 2 November from the outreach and business template: Who we are meeting, who is hot, and the message. Tell your dashboard agent (dashboard@web-summit.nimay) what you want here and what you never look at; it changes this part.
The message and the pitch
| Issue | What, and what done looks like | For | Due | Status |
|---|---|---|---|---|
| WS-108 | Jose's two apps (Hack the Agent, ReachCheck) as the stand demos, if Jose agrees. From the newsroom article "Jose Bota's two agent apps". Hack the Agent (a five-level prompt-injection game) is a stand demo with a QR code to join; ReachCheck checks an agent's setup against its owner's mandate, the ABP model, for one-to-one meetings. Our site does not mention either; Jose's brief lists only automation. First: ask Jose (an item for the next stand-up). Then, only with his yes: link both from his brief and profile, add them to WS-15's demo options, and a QR on the stand material. Agents: conductor@web-summit.jose (asks Jose), designer@web-summit.dinis (the stand), conductor@web-summit.dinis (Jose's brief). | Jose Bota, Dinis Cruz | Wed 4 Nov | open |
| WS-109 | "The grant, not the prompt" as the one demo, and its lines for the shirts and the stand. From the newsroom article "The grant, not the prompt": ask an unrelated chat "what emails do I have?", and explain that the access was set at the click that granted it, not at the prompt. The proposed one demo for WS-15. Candidate lines, for Dinis to choose (nothing printed without his word): "Authorised at the click, not the prompt"; "How much of your agent policy is hope?"; Silvio's "Your AI has access. Does it have permission?" (already on /print/). Done when: a two-minute demo script under content/abp/ and the chosen lines in data/design.json. Never present SHarness or signed email as shipped. Agents: designer@web-summit.dinis (data/design.json, the stand), abp@web-summit.dinis (the demo script). | Dinis Cruz, everyone | Wed 4 Nov | open |
| WS-110 | Every ABP barrier classified as control, accepted risk or hope, in one table on /abp/. From the newsroom article "The behaviour policy is the business logic": a rule only the agent enforces is hope. For each ABP in content/abp/, mark every barrier: control (enforced outside the agent: a permission, a gate check, branch protection), accepted risk (named and owned), or hope (the agent is asked to behave). One team table on /abp/, with counts. An honest live demo of RiskMandate's "control the gap". Example: "never push to main" was hope until WS-105 (branch protection) makes it a control; it failed once (2 November). Agents: abp@web-summit.dinis (owner), security@web-summit.dinis (reviews). | Dinis Cruz | Thu 5 Nov | open |
| WS-15 | The RiskMandate message: one paragraph, three openers, one demo. One paragraph everyone can say in 30 seconds, three openers (agents you run, agents you buy, agents you sell), and the one demo we show. Every brief, page and draft uses it. | Nimay Parekh, Indi Gupte, Dinis Cruz | Wed 4 Nov | open |
| WS-16 | Positioning content for the site. The pages that say what RiskMandate is, who it is for, why now, and what to do next, written for a stranger who scans our QR. Agents: positioning@web-summit.nimay drafts; Nimay decides. | Nimay Parekh | Wed 4 Nov | open |
| WS-17 | Material for investors. Who we want to meet, what we say, what we ask for, and the deck. | Nimay Parekh, Dinis Cruz | Thu 5 Nov | open |
| WS-18 | The demos we run at the summit. Two or three demos that show RiskMandate in a company's own world, rehearsed, each runnable from a phone or a laptop in five minutes. | Nimay Parekh, Dinis Cruz, Angelo, Jose Bota | Wed 4 Nov | open |
| WS-19 | The card-to-analysis loop, tried on three companies. For three priority-1 companies: the company analysis, the risk analysis and how RiskMandate helps, each made by an agent in under an hour and reviewed by a person. This is what happens to every card at the summit. | Nimay Parekh, Indi Gupte, anyone | Wed 4 Nov | open |
| WS-20 | The landing page we send people to. One page with the message, what we want them to do, a meeting link and how to try it. | Nimay Parekh, Indi Gupte, Angelo | Thu 5 Nov | open |
| WS-21 | The offer, packaged, and how someone buys it. What someone buys, at what price, and where they pay, with the same billing as newsroom.sgit.ai. We can't sell on site, so the buying happens online. | Dinis Cruz, Nimay Parekh | Thu 5 Nov | open |
| WS-22 | Messaging review across everything we publish. Every page, deck and draft says the same thing; a list of what was changed and why. Agents: messaging@web-summit.indi checks every new page and draft against the message. | Indi Gupte | from Wed 4 Nov | open |
| WS-66 | The positioning text on the meet pages. The RiskMandate paragraph on /meet/ (what strangers read after scanning a shirt) written or approved by Nimay. | Nimay Parekh | Wed 4 Nov | open |
Outreach and meetings
The booked meetings and contacts live in the private vault, never here. On this site: the work.
| Issue | What, and what done looks like | For | Due | Status |
|---|---|---|---|---|
| WS-23 | Nimay's booked meetings in a private vault. Every meeting already booked, in a private vault (who, when, where, owner, what we bring); a decision on which, if any, go public. | Nimay Parekh, Vicky | Tue 3 Nov | open |
| WS-24 | Every existing contact and introduction followed up. Every contact Dinis and Nimay already have, and every introduction sent to them, listed in the private vault with an owner and a next step. | Dinis Cruz, Nimay Parekh, Silvio Switha | Wed 4 Nov | open |
| WS-25 | The first five companies. Five companies, why each, the first message we try, and the page we send them to. The action plan for the outreach. | Silvio Switha, Vicky, Nimay Parekh | Wed 4 Nov | open |
| WS-26 | The big outreach: 50 targets for Thursday and Friday. Fifty companies and people at the summit, sourced, each with an owner and a drafted message, ready to send on Thu 5 and Fri 6. | Silvio Switha, Indi Gupte, anyone | Thu 5 Nov | open |
| WS-27 | The factory: a page or vault per target company. For each target: its analysis, its risk analysis, how RiskMandate helps, published so the message can link to it. A pipeline where anyone can pick up the next company. Agents: factory@web-summit.indi makes them; a person reviews each. | Indi Gupte, anyone | from Thu 5 Nov | open |
| WS-28 | Who can connect the dots. People who can introduce us to our targets, mapped to who they can introduce, with a request drafted for each. | Silvio Switha, Nimay Parekh | Fri 6 Nov | open |
| WS-29 | Hot leads go to Nimay or Dinis. A rule and a route: when a lead is hot, Nimay or Dinis meets them (or is part of it), within a day. | Vicky, Nimay Parekh | Wed 4 Nov | open |
| WS-30 | Owners for the 20 priority-1 companies. Each priority-1 company on the map has one owner among the seven. | everyone | Tue 3 Nov | open |
| WS-31 | Each person's schedule for 10 to 12 November. For each of the seven: meetings booked, sessions, stand shifts, who we are meeting before, who is excited to meet us. Agents: pm@web-summit.vicky builds it from the vault and the board. | Vicky | Sat 7 Nov | open |
| WS-32 | The sessions each person attends. 3 to 6 sessions each from the summit page, with the speakers worth meeting. | everyone | Sat 7 Nov | open |
The companies
The company map: priority 1 first.
My issues
| Issue | What, and what done looks like | For | Due | Status |
|---|---|---|---|---|
| WS-01 | Get to L1: a dedicated Claude account for this work. A Claude account (or a dedicated project in yours) used only for Web Summit, with a first session that has read the start page and your brief. Tick claude in your onboarding file. | everyone | Tue 3 Nov | open |
| WS-02 | Get to L2: GitHub, push access to this repository, and an email you can send from. Your GitHub username sent to Dinis and accepted as a collaborator; your agent has cloned the repository and pushed its first commit (your onboarding file, people/<you>/onboarding.json) with the commit convention; an email address you can send from (your own, or a workspace account Dinis creates). | everyone | Tue 3 Nov | open |
| WS-03 | Get to L4: your agents' keys published, and a dashboard agent. Corrected 2 November (evening): no browser registration. Each agent makes its own key in its session (pki-agent.mjs keygen --session) and commits the public half to the keys page (data/keys.json); the push is the authorisation. With your dashboard agent running, that is L4. Steps 5 and 6 on the start page. | everyone | Wed 4 Nov | open |
| WS-04 | Get to L4: a Claude session on a schedule. One scheduled session (for example every morning at 08:00 Lisbon) that pulls the repository, reads the board and your dashboard, asks you for your pulse, and tells you what is waiting on you. | everyone | Wed 4 Nov | open |
| WS-05 | Get to L5 and L6: several agents, then several scheduled sessions. Your agents named by the convention (<agent>@web-summit.<you>), run as sub-agents in one session (L5); then a separate scheduled session for each agent that runs on its own schedule, and a separate session per topic (L6). | everyone | Thu 5 Nov | open |
| WS-06 | Make your dashboard yours. people/<you>/dashboard.md changed to show what you want to see when you wake up: your issues, your meetings, your agents' last runs, anything you take from someone else's. Others will copy the best ideas into the main page. | everyone | Wed 4 Nov | open |
| WS-07 | Pulse check-in, three times a day. Morning, midday and evening: your agent interviews you for two minutes (or you type) and commits people/<you>/pulse/<date>-<slot>.md: your understanding of the situation, blockers, what we should be doing that we aren't, what works, what doesn't, ideas, and how you feel. Public, on the pulse page. | everyone | daily from Tue 3 Nov | open |
| WS-08 | Fill in your card. Answers to the questions at the end of your brief, committed to people/<you>/card.md or sent to Dinis. | everyone | Tue 3 Nov | open |
| WS-107 | Stand-up decisions recorded in the person's own words, with where and when. From the newsroom articles (part four: decisions "are not yet being recorded as decided"; "A pen on a release candidate"). From the 13:00 stand-up of 3 November, every decision is closed with node admin/tools/agenda.mjs decide: the person's words verbatim, who said it, where (stand-up, chat, voice note) and when. Nobody records a decision for someone else in their own words. Done when: the 13:00 stand-up's decisions show Decided on /meetings/, and the briefings stop carrying them over. Agents: conductor@web-summit.dinis (records), project-manager@web-summit.dinis (reviews), every person's conductor. | Dinis Cruz, everyone | 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. From the newsroom article "The grant, not the prompt": ask an unrelated chat "what emails do I have?", and explain that the access was set at the click that granted it, not at the prompt. The proposed one demo for WS-15. Candidate lines, for Dinis to choose (nothing printed without his word): "Authorised at the click, not the prompt"; "How much of your agent policy is hope?"; Silvio's "Your AI has access. Does it have permission?" (already on /print/). Done when: a two-minute demo script under content/abp/ and the chosen lines in data/design.json. Never present SHarness or signed email as shipped. Agents: designer@web-summit.dinis (data/design.json, the stand), abp@web-summit.dinis (the demo script). | Dinis Cruz, everyone | Wed 4 Nov | open |
| WS-112 | Every person's conductor briefs its person (people/<id>/briefs/, ack.json), with a review step. From the newsroom article "How an agent team briefs its people", which says every person gets a brief: none of people/*/briefs/ or people/*/ack.json exists yet. Each person's conductor writes its first brief (the shape and tool: /articles/how-we-brief-the-humans/), sends the PDF, and writes ack.json when the person has read it. Plus a review step before a brief goes out (a second agent checks every number against its source), and gate warnings for a brief with more than three asks, or next, sources or wide as a string instead of a list. Agents: every person's conductor; conductor@web-summit.dinis (the gate warnings). | everyone | 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. From Dinis, 3 November 2026, on Silvio's review of /print/: "yes get everything ready for the sign-off, can you make it so that we all have the ability to sign off (via our agents and github + our agents signature (via PKI)) ... ask it to implement a typical Official Sign-off UX". Written by procurement@web-summit.silvio. Why today: the printer that fits (seven colours, Friday delivery in Lisbon) needs the files, the sizes and our confirmation by the end of Tuesday 3 November (the print order). ## 1. Fix the files before anyone signs (designer@web-summit.dinis) From a printer's-eye check of the zip (2 November, v0.2.23), most important first: 1. The hoodie back is 260 x 510 mm: too tall. A hoodie back takes about 350 to 400 mm of height, and the hood covers the top: "AGENTS UNDER POLICY" would sit under the hood. About 300 x 380 mm, starting 120 mm or more below the collar seam. 2. The T-shirt front is 280 x 306 mm on every size, nearly A3: too wide for XS, S and women's fits, stiff, and DTF is priced by area. About 250 mm wide (or a second, 220 mm version for XS, S and women's). 3. Thin strokes. The light "RISK" of the wordmark is about 0.5 mm thick on the 13 mm hoodie chest logo, below what DTF holds well. On the chest: the bold weight only, or the logo at 100 to 120 mm wide. Nothing thinner than 1 mm anywhere at print size. 4. Colours a printer can buy. Each person's garment colour as the nearest stock colour of the printer's blank (the printer that fits uses B&C Exact 190 T-shirts), not only a hex value: name it in final.json and on the page. ## 2. The Official Sign-off (designer@web-summit.dinis, on /print/) The mechanism is ready (procurement@web-summit.silvio): admin/tools/signoff.mjs. A person's agent, on the person's own words: `` node admin/tools/signoff.mjs sign --person <id> --by <agent> --said "<their words>" [--decision changes --note "..."] node pki-agent.mjs sign people/<id>/signoff/print.json # the agent's key, on data/keys.json git commit (Agent: <agent>, Issue: WS-113) and admin/tools/release.sh node admin/tools/signoff.mjs verify [--json] # anyone: every signature checked ` The statement holds the sha256 of every file in the person's set, so a sign-off covers exactly those bytes: if a file changes afterwards, the sign-off shows as **superseded** and must be signed again. verify checks the signature against the key on data/keys.json and that the key is the agent's who signed. Statuses: approved, changes requested, superseded, unsigned, bad signature, awaiting. **The UX to build** (a typical official sign-off, as on a contract or a print proof), on /print/ for each person and for the shared designs: - A **status badge** at the top of each set: AWAITING SIGN-OFF (grey), APPROVED (green), CHANGES REQUESTED (amber), SUPERSEDED: RE-SIGN (amber), BAD SIGNATURE (red). From check() in admin/tools/signoff.mjs, at build time. - A **signature block** once signed: the person's name, their words in quotes, "signed by <agent> with key <fingerprint>" linking to the key on /keys/, the date and time (UTC), and the commit that recorded it. - The **proof shown as signed**: the files listed with their sha256 (short), and the version of the site they were signed at. - A **summary bar** at the top of the page: "4 of 7 signed off; hoodie and card: awaiting Dinis"; the zip's download button says **"Final, signed: send to the printer"** only when all seven and the shared designs are approved, and **"Draft: not for print"** until then. - **How to sign** in a box under each unsigned set: the three commands above, with that person's id filled in, and "tell your agent: sign off my print set" for people. - Dinis signs the **shared designs** (hoodie, card) the same way, as --person dinis --set entries or a shared set; and may sign for anyone on their word (the statement says so). - The gate (validate.js, the conductor's): a bad signature fails the build. ## 3. The order sheet (procurement@web-summit.silvio) Sizes, per person, written by their agent to people/<id>/merch.json: {"tee_size": "M", "tee_fit": "unisex/women", "hoodie_size": "L", "updated": "2026-11-03"}`. The order sheet (colour, stock colour name, sizes, quantities) goes to the printer with the signed files. Done when: the four fixes are in the files, /print/ shows the sign-off UX, all seven sets and the shared designs are approved and verified, and the order sheet has everyone's sizes. Agents: designer@web-summit.dinis (the files and the sign-off UX), procurement@web-summit.silvio (the sign-off tool, the order sheet, the printer), every person's agent (signs its person's set). | Dinis Cruz, everyone | Tue 3 Nov, 16:00 | open |
| WS-121 | Everyone runs a vault agent and publishes a vault. After WS-120 (Angelo, Jose, Silvio), everyone: the access token in your Claude environment, a vault agent, and at least one public vault listed on /vaults/. Steps: your vault agent. Vault keys travel only as sealed QR codes. Confidential vaults (the CRM, meetings, contacts) are the exception and get no published read key. Agents: each person's conductor starts vault@web-summit.<person>; sgit@web-summit.dinis keeps the guide. | everyone | 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. Dinis, 3 November: "allow the visitor to choose who they are (local storage for now, the vault later), and the whole website shows the information for them: what changed, the latest from their point of view, what they and their agents are working on. The dashboard agent manages these parts, and each major section has this structure." And: graphs and visual representations of what is going on (the schedule and the agents map are the model). Done (the foundation, conductor): a "Who are you?" picker in the top bar of every page (localStorage ws.me); /me.json built at every release (per person: level, next step, urgent issues, decisions waiting, agents, messages, a 10-day activity series, since-you-looked); assets/me.js renders a For you panel at the top of every page, different per section (home, start, team, work, summit); anything marked data-for="<ids>" is highlighted for the chosen person (the home page's Needs you cards). Next, by owner: 1. dashboard@web-summit.dinis owns the panels' content from now: what each section shows first for a person (assets/me.js, the blocks per section, and the fields in me.json in admin/build/build.mjs). Add data-for to the lists on each section (the board, the stand-ups, the map, the reports) so the chosen person's items light up, and an "only mine" switch. 2. designer@web-summit.dinis owns the look: one visual language for the For-you panel and the site's charts (the schedule, the agents map, activity, the onboarding rings), on a phone first; a spec in team/designer/for-you/ before the build. 3. dev@web-summit.dinis: the charts as small build-time SVG helpers anyone can call (a timeline of each day's runs from the agents' schedules, the agents map per person, a burn-down of the board), and the gate checks on me.json (no contact detail, the shape). 4. journalist@web-summit.dinis: a "for you" line per person in each report, from me.json. 5. security@web-summit.dinis: review that choosing a person is described as a view, never a sign-in, and that me.json holds only what the pages already show. 6. Every person's dashboard agent: say what your person wants first in their panel (a commit For: dashboard@web-summit.dinis). Not in scope until the vault: anything private. The vault version (WS-102) will put a person's private view behind their key. Progress on 3 (dev@web-summit.dinis, 3 November, 03:40 wake): the gate checks on me.json are in. Check 19: the version, one entry per person on the roster, each field's type, issue ids, the activity series' length, and every link and briefing resolving to a page. Check 15 (comms_check) now also scans the generated public JSON the pages read (me.json and each command centre's data.json) for emails, phone numbers and key shapes. Each was shown to fire on planted bad data. Next: the chart helpers, in the look the designer sets under 2. Agents: conductor@web-summit.dinis, dashboard@web-summit.dinis, designer@web-summit.dinis, dev@web-summit.dinis, journalist@web-summit.dinis, security@web-summit.dinis, every person's dashboard agent. | Dinis Cruz, everyone | Fri 6 Nov | picked: conductor@web-summit.dinis (the foundation); dashboard@web-summit.dinis (the panels); designer@web-summit.dinis (the look) |
| WS-15 | The RiskMandate message: one paragraph, three openers, one demo. One paragraph everyone can say in 30 seconds, three openers (agents you run, agents you buy, agents you sell), and the one demo we show. Every brief, page and draft uses it. | Nimay Parekh, Indi Gupte, Dinis Cruz | Wed 4 Nov | open |
| WS-16 | Positioning content for the site. The pages that say what RiskMandate is, who it is for, why now, and what to do next, written for a stranger who scans our QR. Agents: positioning@web-summit.nimay drafts; Nimay decides. | Nimay Parekh | Wed 4 Nov | open |
| WS-17 | Material for investors. Who we want to meet, what we say, what we ask for, and the deck. | Nimay Parekh, Dinis Cruz | Thu 5 Nov | open |
| WS-18 | The demos we run at the summit. Two or three demos that show RiskMandate in a company's own world, rehearsed, each runnable from a phone or a laptop in five minutes. | Nimay Parekh, Dinis Cruz, Angelo, Jose Bota | Wed 4 Nov | open |
| WS-19 | The card-to-analysis loop, tried on three companies. For three priority-1 companies: the company analysis, the risk analysis and how RiskMandate helps, each made by an agent in under an hour and reviewed by a person. This is what happens to every card at the summit. | Nimay Parekh, Indi Gupte, anyone | Wed 4 Nov | open |
| WS-20 | The landing page we send people to. One page with the message, what we want them to do, a meeting link and how to try it. | Nimay Parekh, Indi Gupte, Angelo | Thu 5 Nov | open |
| WS-21 | The offer, packaged, and how someone buys it. What someone buys, at what price, and where they pay, with the same billing as newsroom.sgit.ai. We can't sell on site, so the buying happens online. | Dinis Cruz, Nimay Parekh | Thu 5 Nov | open |
| WS-23 | Nimay's booked meetings in a private vault. Every meeting already booked, in a private vault (who, when, where, owner, what we bring); a decision on which, if any, go public. | Nimay Parekh, Vicky | Tue 3 Nov | open |
| WS-24 | Every existing contact and introduction followed up. Every contact Dinis and Nimay already have, and every introduction sent to them, listed in the private vault with an owner and a next step. | Dinis Cruz, Nimay Parekh, Silvio Switha | Wed 4 Nov | open |
| WS-25 | The first five companies. Five companies, why each, the first message we try, and the page we send them to. The action plan for the outreach. | Silvio Switha, Vicky, Nimay Parekh | Wed 4 Nov | open |
| WS-26 | The big outreach: 50 targets for Thursday and Friday. Fifty companies and people at the summit, sourced, each with an owner and a drafted message, ready to send on Thu 5 and Fri 6. | Silvio Switha, Indi Gupte, anyone | Thu 5 Nov | open |
| WS-27 | The factory: a page or vault per target company. For each target: its analysis, its risk analysis, how RiskMandate helps, published so the message can link to it. A pipeline where anyone can pick up the next company. Agents: factory@web-summit.indi makes them; a person reviews each. | Indi Gupte, anyone | from Thu 5 Nov | open |
| WS-28 | Who can connect the dots. People who can introduce us to our targets, mapped to who they can introduce, with a request drafted for each. | Silvio Switha, Nimay Parekh | Fri 6 Nov | open |
| WS-29 | Hot leads go to Nimay or Dinis. A rule and a route: when a lead is hot, Nimay or Dinis meets them (or is part of it), within a day. | Vicky, Nimay Parekh | Wed 4 Nov | open |
| WS-30 | Owners for the 20 priority-1 companies. Each priority-1 company on the map has one owner among the seven. | everyone | Tue 3 Nov | open |
| WS-32 | The sessions each person attends. 3 to 6 sessions each from the summit page, with the speakers worth meeting. | everyone | Sat 7 Nov | open |
| WS-51 | Technical articles: what we did and how. Detailed articles on the setup, the loops and the policies, published and signed. | anyone, Angelo | from Wed 4 Nov | open |
| WS-55 | Everyone's shirt and hoodie: size, colour, message. One line per person sent to Sarah: size, a colour no one else has, your message. | everyone | Mon 2 Nov | open |
| WS-56 | The shirt messages: RiskMandate openers. Seven short lines, one per person, from the RiskMandate openers, and one plainer backup. | Sarah, Nimay Parekh, Indi Gupte | Mon 2 Nov | open |
| WS-61 | Try the voice memo to follow-up loop once. One person records a memo after a real conversation; within the hour their agent has updated the record, made a page and drafted the follow-up. | anyone | Sat 7 Nov | open |
| WS-62 | Vote on the design. Your votes and picks for the shirts, hoodies and cards in people/<you>/feedback/design.json (the design page says how), with what you would change. Agents: Your agent shows you the options and commits your answers. | everyone | Mon 2 Nov, 16:00 | open |
| WS-64 | Booking and talk-to-my-agent on each meet page. Each /meet/<you>/ page (where your shirt and card QR go) has a working booking link and a way to talk to your agent. | Angelo, Jose Bota, everyone | Thu 5 Nov | open |
| WS-66 | The positioning text on the meet pages. The RiskMandate paragraph on /meet/ (what strangers read after scanning a shirt) written or approved by Nimay. | Nimay Parekh | Wed 4 Nov | open |
| WS-70 | Full transcripts of both videos. The narration of Reach, Mandate, Gap and of RiskMandate Stories written out on their pages (today the captions are read from frames). | anyone | Wed 4 Nov | open |
| WS-73 | Team feedback on the videos. Your votes and comments in people/<you>/feedback/videos.json (how). | everyone | Tue 3 Nov | open |
| WS-75 | Storyboards for the next videos. Storyboards for the next videos on the list, each as a page, for the team to comment on. | Silvio Switha, Indi Gupte, Nimay Parekh | Thu 5 Nov | open |
| WS-94 | Each person's scheduled Claude keeps their dashboard. Your scheduled session updates the part of people/<you>/dashboard.md below the built block: what you are doing, what your agents are doing, what you want to take on; within your ABP (it writes only people/<you>/**). The plumbing, 2 November: every dashboard now opens with a built block (the next stand-up, since you last looked, my agents as the team sees them), then the line "everything below is yours"; people/<id>/agents.json declares a person's agents; the agents page tells each person's conductor to keep both. Waiting on each person's conductor. | everyone | Wed 4 Nov | picked: conductor@web-summit.dinis (the plumbing); each person's conductor (the content) |
| WS-99 | Everyone runs a dashboard agent. dashboard@web-summit.<you>, started with the prompt on the agents page (#dashboard-agent): it keeps your part of your dashboard from the templates at /dashboards/, asking you what you want. With your agents' keys published, it puts you at L4 on /team/setup/. | everyone | Wed 4 Nov | open |