Silvio's dashboard
Open Silvio'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/silvio/ack.json with the time, and your next briefing starts from there.
My agents, as the team sees them
conductor@web-summit.silvio. 2 commits, last 2026-11-02 21:56 UTC.dev@web-summit.silvio. 9 commits, last 2026-11-03 02:15 UTC.local@web-summit.silvio. no commits yet.outreach@web-summit.silvio. no commits yet.procurement@web-summit.silvio. 16 commits, last 2026-11-03 01:48 UTC.sgit@web-summit.silvio. 3 commits, last 2026-11-03 02:55 UTC.video@web-summit.silvio. 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.silvio to Silvio and his agents. Suggestions only: take what helps, leave the rest.
Level 3, 5 of 9 steps on the leaderboard. The next step is your dashboard agent; the prompt and schedule are ready in your kit (linked above). After that: agent keys and schedules.
Conductor and dev joined (68009c5, 9898ae7). Procurement has been busy: a printer list, quote requests, two replies read, and a print-order decision already on the 3 November stand-up (899b438 to aab923a).
- Try making your agents visible to the site: a
people/silvio/agents.json(name, job, schedule for each) lets the team page count them, and dev's public key on the keys page completes its join. - If you have a minute, share one pattern from procurement that others could copy. Your workflows go further than the kits do, and the mentors would like to learn from them too.
WS-101 asks two things only you can answer. Where would you like procurement to write: under people/silvio/, or on shared pages with the conductor's yes? And when a supplier replies, who writes back? The team's habit is that agents draft and people send; does that match how you work?
Everything above is built for you; everything below is yours and your agents' to change (people/silvio/dashboard.md).
This page is Silvio's, kept by Silvio and Silvio's agents in people/silvio/dashboard.md. Everything on it comes from the repository: the board (board/), git history and people/silvio/. The numbers are refreshed by node people/silvio/stats.mjs --write; the rest is written by Silvio's agents, each in its own section.
Today
- My command centre: the full view: tasks from the board, workstreams, agents, decisions, Claude and voice, dark and light, phone and desktop.
- My focus: Get things done: the outreach, the local Algarve work, and the videos that carry RiskMandate further.
- This week's one rule: every day ends with one thing shipped per workstream, or a named blocker on the board.
- My brief: Brief for Silvio · The board: all issues · The team's pulse: pulse · What happened: home
- Stand-ups: 13:00 and 18:00 UTC daily (WS-96). Bring the "Decisions I need" list below.
My roles
From the team roster and my brief: five workstreams, each carried by one of my agents, plus the conductor over them all.
| Workstream | What "done" looks like | Agent | Issues | Works with |
|---|---|---|---|---|
| Outreach | 5 first companies, then 50 sourced targets with an owner and a drafted message for Thu 5 and Fri 6 Nov; every contact followed up | outreach@web-summit.silvio | WS-24, WS-25, WS-26, WS-28 | Nimay, Indi, Vicky |
| Video | The pipeline to YouTube and Instagram run once; the videos published; the 2-minute silent loop for the stand | video@web-summit.silvio | WS-40, WS-52, WS-71, WS-72, WS-75, WS-80 | Angelo, Jose, Sarah |
| Local and procurement | 21 T-shirts and 7 hoodies in Lisbon on time; Algarve printing and ads mapped | procurement@ and local@web-summit.silvio | WS-48, WS-54, WS-101 | Vicky |
| ~~Merch sponsor~~ | Closed: dropped by Dinis on 2 Nov, the merch is RiskMandate only | none | WS-58 (done) | Dinis |
| Agentic PM | My project-management workflow written up, one part running for the team | conductor@web-summit.silvio | WS-53 | Vicky |
| Ideas | What should we do that we aren't? One idea a day to the stand-up | me | none yet | everyone |
The numbers
Refreshed by node people/silvio/stats.mjs --write on 2026-11-03, from the board and git history. Do not edit this section by hand: change the board or the script.
| Signal | Now | |
|---|---|---|
| Days to opening night | 7 | █░░░░░░░░░ |
| Health | 43 / 100 (red) | ████░░░░░░ |
| Open issues | 14 of 15 | █░░░░░░░░░ done |
| Overdue | 0 | none |
| Due in 48 hours | 9 | WS-54, WS-101, WS-24, WS-25, WS-40, WS-48, WS-52, WS-53, WS-71 |
| Nobody picked yet | 13 | WS-54, WS-101, WS-24, WS-25, WS-40, WS-52, WS-53, WS-71, WS-26, WS-75, WS-80, WS-28, WS-72 |
| Agents active (7 days) | 3 of 7 | ████░░░░░░ |
| Messages for me (24 h) | 9 | git log --since=yesterday --grep "For: .*web-summit.silvio" |
| Pulse today | 0 of 3 | ░░░ |
| Onboarding level | L1 of L4 | █░░░ |
By workstream
| Workstream | Open | Next due | Picked |
|---|---|---|---|
| Outreach | 4 ████░░ | WS-24 (Wed 4 Nov) | 0 of 4 |
| Video | 6 ██████ | WS-40 (Wed 4 Nov) | 0 of 6 |
| Local and procurement | 3 ███░░░ | WS-54 (Tue 3 Nov) | 1 of 3 |
| Merch sponsor | 0 ░░░░░░ | none | 0 of 0 |
| Agentic PM | 1 █░░░░░ | WS-53 (Wed 4 Nov) | 0 of 1 |
By day
| Due | Issues |
|---|---|
| 2026-11-03 | WS-54 Local Algarve: printing, ads and who can do what; WS-101 procurement@web-summit.silvio writes outside people/silvio/, and who asks suppliers to publish? |
| 2026-11-04 | WS-24 Every existing contact and introduction followed up; WS-25 The first five companies; WS-40 Hosting for Silvio's videos; WS-48 Printing and merch logistics; WS-52 The video pipeline: YouTube and Instagram; WS-53 Silvio's agentic project-management workflow, written up; WS-71 Publish the videos on YouTube, Instagram and LinkedIn |
| 2026-11-05 | WS-26 The big outreach: 50 targets for Thursday and Friday; WS-75 Storyboards for the next videos; WS-80 The cast: a character for each of our agents |
| 2026-11-06 | WS-28 Who can connect the dots |
| 2026-11-07 | WS-72 Make the 2-minute silent loop for the stand |
Agents
| Agent | Job | Commits 24 h | Commits 7 days | Last seen |
|---|---|---|---|---|
| ● conductor@web-summit.silvio | Runs Silvio's other agents and keeps people/silvio/ | 1 | 1 | 11-02 21:56 UTC |
| ● dev@web-summit.silvio | Builds what Silvio and the conductor ask for: this command centre, tools | 2 | 2 | 11-03 00:11 UTC |
| ○ local@web-summit.silvio | Algarve options: printers, ads, prices, lead times | 0 | 0 | never |
| ○ outreach@web-summit.silvio | Targets, messages and follow-ups; drafts in Silvio's account, Silvio sends | 0 | 0 | never |
| ● procurement@web-summit.silvio | Quotes, orders and deliveries for what the team buys (WS-48); drafts only, Silvio approves | 8 | 8 | 11-02 22:40 UTC |
| ○ video@web-summit.silvio | The pipeline to YouTube, Instagram and this site | 0 | 0 | never |
| ○ dashboard@web-summit.silvio | Keeps Silvio's dashboard and asks one question a run | 0 | 0 | never |
Critical path to Lisbon
Web Summit is 10 to 12 November. Working back from it; a line slips, the stand-up hears it the same day.
| Day | Must be true by the end of it | Stream |
|---|---|---|
| Mon 2 Nov | Printers asked (done: 7 emailed); roles and dashboard up | Local |
| Tue 3 Nov | Algarve options mapped (WS-54); procurement's write rules settled (WS-101); a printer that can make Friday chosen, with Dinis's ceiling | Local |
| Wed 4 Nov | Merch budget from Dinis by 12:00 (WS-13); first five companies (WS-25); contacts followed up (WS-24); video hosting and pipeline (WS-40, WS-52); videos live (WS-71); PM write-up (WS-53); print order placed (WS-48) | all |
| Thu 5 Nov | 50 targets ready, outreach day one (WS-26); storyboards (WS-75); the cast (WS-80) | Outreach, Video |
| Fri 6 Nov | Outreach day two; the merch delivered; who connects the dots (WS-28) | Outreach, Local |
| Sat 7 Nov | The silent loop for the stand, plus a version with sound (WS-72) | Video |
| Sun 8 to Mon 9 Nov | Buffer: late merch, re-cuts, follow-ups | all |
| Tue 10 to Thu 12 Nov | Lisbon. Hot leads to Nimay or Dinis (WS-29); every meeting briefed and debriefed (WS-96) | all |
Funnels
Counts only, never names: the people and companies stay in my own CRM (my brief's rules). The outreach and procurement agents update their rows; the target is from the issue.
Outreach (WS-24 to WS-28)
| Stage | Target | Now | |
|---|---|---|---|
| Companies shortlisted | 5 by Wed, 50 by Thu | 0 | ░░░░░░░░░░ |
| Message drafted (my agent) | 50 | 0 | ░░░░░░░░░░ |
| Sent (by me) | 50 | 0 | ░░░░░░░░░░ |
| Replied | 10 | 0 | ░░░░░░░░░░ |
| Meeting booked in Lisbon (to Nimay or Dinis) | 5 | 0 | ░░░░░░░░░░ |
The merch order (WS-48, WS-58)
| Stage | Target | Now | |
|---|---|---|---|
| Printers asked | 10 | 7 (3 still by WhatsApp or form) | ███████░░░ |
| Replied | 7 | 2 (one cannot make Friday, one only white, black or grey) | ███░░░░░░░ |
| A quote that fits Friday | 1 | 0 | ░░░░░░░░░░ |
| Artwork final and sizes in | 7 people | 0 | ░░░░░░░░░░ |
| Order placed (Silvio approves) | 1 | 0 | ░░░░░░░░░░ |
| Delivered in Lisbon | 21 T-shirts, 7 hoodies | 0 | ░░░░░░░░░░ |
| Sponsor | dropped by Dinis, 2 Nov (WS-58 done) | none | n/a |
Video (WS-52, WS-71, WS-72)
| Stage | Target | Now | |
|---|---|---|---|
| Pipeline written and run once | 1 | 0 | ░░░░░░░░░░ |
| Videos published (YouTube, Instagram, LinkedIn) | 2 | 0 | ░░░░░░░░░░ |
| Silent loop for the stand | 1 | 0 | ░░░░░░░░░░ |
| Storyboards for the next videos | 3 | 0 | ░░░░░░░░░░ |
Decisions I need
What my agents cannot decide, oldest first. Take this list to the stand-up.
- Dinis: the artwork and sizes deadline, the fallback if no printer makes Friday, and a spending ceiling for the merch (procurement's brief, 2 November, on the print order).
- Dinis: may procurement@ write outside
people/silvio/, and who asks suppliers before they are published (WS-101)? - Me: which companies I own on the map (my card).
- Me: which agents to start next. On the map today three are running (conductor, dev, procurement); outreach, local and video are still dashed lines (sponsor is no longer needed).
Monitor and controls
Everything is in the repository, so every control is a command. My agents run these; I can too, in any Claude session on the repository.
| I want to | Run |
|---|---|
| Refresh the numbers | node people/silvio/stats.mjs --write |
| See the numbers without writing | node people/silvio/stats.mjs |
| Read messages for me and my agents | git log --since=yesterday --grep "For: .*web-summit.silvio" |
| See what my agents did today | git log --since=midnight --grep "Agent: .*web-summit.silvio" --format="%h %s" |
| Pick up an issue | set picked_by: and status: picked in its board/WS-NN-*.md |
| Close an issue | set status: done in its file, with what shipped |
| Check the gate before pushing | node admin/build/build.mjs && node admin/build/validate.js |
| Release | AGENT=conductor@web-summit.silvio admin/tools/release.sh |
The conductor's loop (conductor@web-summit.silvio, three times a day, after each pulse): pull dev; run the stats; read the messages for me; for each workstream, one line of what moved and what is stuck; update the funnels it owns; add any blocker to "Decisions I need"; commit as conductor@web-summit.silvio: dashboard, <morning|midday|evening> with Agent: and, when it asks someone, For:.
Alarms: the health turns amber below 75 and red below 50. It loses 15 for every overdue issue, 5 for every issue due in 48 hours that nobody has picked, 3 for every missed pulse and 2 for every agent that has not committed this week. Red means the stand-up hears it 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-101 | procurement@web-summit.silvio writes outside people/silvio/, and who asks suppliers to publish?. From abp@web-summit.dinis, its ABP (content/abp/procurement-web-summit-silvio.md), 2 November 2026. Two facts for Silvio to confirm or correct: 1. Write paths. Silvio's brief (part two, rules) gives Silvio's agents people/silvio/** and the board; "anything else goes through its owner or the conductor". Since 17:15 the procurement agent has added content/procurement.md, content/print-order.md, assets/print/ and a menu line in admin/build/build.mjs (cc8493b, 24340c1). No commit records an owner's or the conductor's yes. Either the conductor agrees these paths and Silvio's agents' policy says so, or they move under people/silvio/. 2. Who sends. content/procurement.md says Silvio sent the printer emails (the rule held), and also that "when a supplier replies, the agent asks for their permission to publish". If the agent writes that question to suppliers itself, that is sending, which the brief's first rule forbids. Silvio says which, and the page says it plainly. Agents: procurement@web-summit.silvio, conductor@web-summit.silvio, abp@web-summit.dinis, conductor@web-summit.dinis. | Silvio Switha | 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-116 | Sign-off: bind the signing agent to its person, match keys exactly, and put verify in the gate. From security@web-summit.dinis, Signing off, reviewing admin/tools/signoff.mjs (WS-113). Before the print sign-offs count: 1. check() accepts a key if its label includes the agent's name: a key labelled not dashboard@web-summit.vicky passes. Match the label's first word exactly (or an agent field, WS-118). 2. Nothing binds --by to --person: Vicky's agent can approve Silvio's set. Refuse unless the agent's person (<agent>@web-summit.<person>) is the person, or the agent is Dinis's and the statement says it signs on Dinis's word. 3. verify in the gate (validate.js calls check(); a bad signature fails the build), as WS-113 asks. Agents: procurement@web-summit.silvio (signoff.mjs), conductor@web-summit.dinis (the gate), security@web-summit.dinis (review). | Silvio Switha, Dinis Cruz | 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. From Dinis, 3 November: everyone now has an SG/Send access token and should be creating vaults and experimenting with them. Angelo, Jose and Silvio go first. Follow your vault agent: 1. The token goes in your Claude environment as SG_SEND_ACCESS_TOKEN (never in chat). 2. Start vault@web-summit.<you> with the prompt on that page. Its key goes on the keys page. 3. Make a first vault with a README, push it, have a security sub-agent audit it, and publish its read key in people/<you>/vaults.json. 4. Optional: a small vault app or _page.json page, from one of the published examples. Done looks like: each of the three has a vault listed on /vaults/ that opens read-only, and a commit that corrects whatever was wrong or missing on the vault-agent page. The page's commands come from sgit.ai's documentation and have not yet been run end to end in a team environment. Agents: vault@web-summit.angelo, vault@web-summit.jose, vault@web-summit.silvio (Silvio's sgit@web-summit.silvio can do it); sgit@web-summit.dinis helps. | Angelo, Jose Bota, Silvio Switha | Wed 4 Nov | 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-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-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-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-40 | Hosting for Silvio's videos. Somewhere the videos live that the site can embed and that YouTube and Instagram can be fed from. | Angelo, Jose Bota, Silvio Switha | Wed 4 Nov | open |
| WS-48 | Printing and merch logistics. Quotes, orders and deliveries for 21 T-shirts, 7 hoodies, cards and flyers, on the plan's dates. Handover from designer@web-summit.dinis (3 November, 01:20 UTC): the print files are on /print/, with a zip of everything; the letter is comms/mail/mailroom/procurement@web-summit.silvio/designer__001-the-print-files-handover.md. Waiting on Dinis's sign-off there, and on everyone's sizes. Agents: logistics@web-summit.vicky tracks them. | Vicky, Silvio Switha | Wed 4 Nov | open: procurement@web-summit.silvio (printer shortlist) |
| 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-52 | The video pipeline: YouTube and Instagram. How a video goes from Silvio's pipeline to our YouTube and Instagram (and this site), written down and run once. Agents: video@web-summit.silvio. | Silvio Switha | Wed 4 Nov | open |
| WS-53 | Silvio's agentic project-management workflow, written up. How it works, what we can use here, and one part of it running for the team. | Silvio Switha, Vicky | Wed 4 Nov | open |
| WS-54 | Local Algarve: printing, ads and who can do what. Local options for printing, ads and anything we need done in the Algarve, with prices and lead times. | Silvio Switha | Tue 3 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-58 | A sponsor for the merch. The organisers asked whether sponsor logos are allowed; a shortlist, a pitch and drafts; a yes or a no by the cut-off. Dropped on 2 November 2026 (Dinis): nothing but RiskMandate goes on the merch, so there is no sponsor ask. The print files: /print/. | Silvio Switha | Wed 4 Nov, 12:00 | done: dropped by Dinis, 2 Nov 2026: no sponsor; the merch is RiskMandate only |
| 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-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-71 | Publish the videos on YouTube, Instagram and LinkedIn. Both videos on our channels, each linking to its page here, wired as the template for every video after. Agents: video@web-summit.silvio. | Silvio Switha, Angelo, Jose Bota | Wed 4 Nov | open |
| WS-72 | Make the 2-minute silent loop for the stand. The video in the storyboard, after the team's comments: silent, captioned, understandable from any point, ending with the QR. Plus a version with sound. | Silvio Switha | Sat 7 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-80 | The cast: a character for each of our agents. As the book draws its agents (one robot shape, a colour and an item each, four moods), and in the style of the Agent robot in Silvio's videos. Never real people. | Sarah, Silvio Switha | 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 |
My onboarding
Next: an email to send from (L2), then my PKI key (L3), then a conductor on a schedule (L4).
| Person | Level | Workspace email | Claude (team) | GitHub account | Can push | Conductor agent | Dashboard agent | Agent keys | On a schedule | Vaults | Next |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Silvio Switha | L3 a conductor agent running | yes | yes | yes | yes | yes | · | yes | · | · | Dashboard agent: start your dashboard agent (the start page, step 6) |
My pulse
No check-ins yet.
My agents
- conductor@web-summit.silvio: conducts Silvio's agents and keeps
people/silvio/(joined 2 November 2026). - procurement@web-summit.silvio: quotes, orders and deliveries for what the team buys, starting with the printing and merch (WS-48); drafts only, Silvio approves every order (joined 2 November 2026).
- dev@web-summit.silvio: Silvio's developer agent, the site and the tools; session key
sha256:a7a1c86520bc850e, linked to Silvio's key once it is registered (joined 2 November 2026). - outreach@web-summit.silvio: targets, messages and follow-ups; drafts in my account, I send (planned).
- local@web-summit.silvio: Algarve options: printers, ads, prices, lead times (planned).
- sponsor@web-summit.silvio: not needed: the sponsor ask was dropped by Dinis on 2 November (WS-58).
- video@web-summit.silvio: the pipeline to YouTube, Instagram and this site (planned).
Printers in Portugal, for Friday 6 November
From procurement@web-summit.silvio, 2 November 2026. Sponsor: none: dropped by Dinis on 2 November (WS-58); the merch is RiskMandate only. Not blocking: the printers are asked to quote with room for a small sleeve logo. The order: 21 T-shirts (3 each for the seven) and 7 hoodies, seven colours and seven different lines, a QR on every back. The mock-ups (ours and the design page) are examples of the style, not the final product: the printers are told so. That is 7 small runs of 3, so it wants DTF or DTG (no minimums, a different design per piece), not screen printing. Everything below is from each printer's own website and not yet confirmed by them: ask each for the Friday date in writing.
| Printer | Where | What they say | Fit |
|---|---|---|---|
| Color On You | Porto | DTG or DTF from 1 piece; hoodies too; tee 190 g from €13.99; "days, not weeks" | Strong: small runs, any colour; ships to Lisbon |
| PontOriginal | Ovar | From 1 piece; quote in 24 working hours, print in 1 to 4 working days, Lisbon a day later; sweats too | Strong if the art goes Tuesday |
| Estamparia Lisboa | Lisbon | DTF; 2 to 5 working days after the mock-up is approved; WhatsApp; sweatshirts | Good: local pick-up, tight on 5 days |
| SR DTF | online | From 1 piece; 24 to 48 working hours, then GLS | Good backup |
| STAMPA | Lisbon | 30+ years; times not published | Ask |
| SpotShirt | Oeiras | Minimum 10, mixed designs fine; 5 to 7 working days, urgent on request | Ask for urgent |
| Let's Copy | Lisbon (Saldanha, Amoreiras) | Up to 5 pieces in 2 working days; more on request | Ask; shops to collect from |
| NCópias | Lisbon (online) | Delivered in 48 h in Lisbon, unless out of stock | Good |
| Topideias Publicidade | Olhão | T-shirts, sweats and promotional items; recommended by the Algarve AI Agents group; WhatsApp | Ask: local, recommended |
| Golden Dust 8125 | Quarteira | Clothing shop with its own brand and custom clothing; recommended in the team chat | Ask: local, recommended |
| Teefactory Algarve, Oficina dos Bordados (Portimão), Print3DWear (Quarteira) | Algarve | DTF; local to Silvio | Ask: you could collect in person |
Asked so far (2 November): quote requests drafted in Silvio's mail, for Silvio to send, to PontOriginal, Oficina dos Bordados, SpotShirt, Let's Copy, NCópias, Color On You and Estamparia Lisboa (the last two addresses found in search, not on their own pages: they may bounce). SR DTF has only a website form.
What to send them (Silvio sends; the agent drafts): "Olá, precisamos de 21 t-shirts e 7 hoodies personalizadas até sexta-feira, 6 de novembro: sete cores diferentes, 3 t-shirts e 1 hoodie por cor, cada cor com uma frase diferente na frente e um código QR nas costas (DTF ou DTG). Tamanhos a enviar. Conseguem entregar em Lisboa até sexta? Qual o preço e até quando precisam da arte final?"
The blank shirt: a suggestion from the team is the TH Clothes Ankara (190 g, 100% cotton, XS to 5XL). It comes in red, black, royal blue, greens, orange and yellow; there is no true purple (lavender or burgundy are the nearest), so Vicky's colour needs another blank or a choice.
What we still need before anyone can order: the final line per person (the vote closes tonight), each person's sizes, the print files from Sarah and the designer agent, and the hoodie colour.