Start here
Today, Monday: vote on the shirts, hoodies and cards on the design page.
Team: start here. Find your name, open your brief, and paste the prompt from it into your own Claude. Your agent then takes you through getting connected, one step at a time. Everything here is public, on purpose: how we work is part of what we show.
Find your name
| Who | Focus | Brief | Dashboard | Prompt |
|---|---|---|---|---|
| Dinis Cruz | Operator: RiskMandate, the strategy, the senior meetings | your brief | your dashboard | your prompt |
| Nimay Parekh | Business, positioning, outreach and investors | your brief | your dashboard | your prompt |
| Angelo | Technical lead: the site, the agents, the behaviour policies | your brief | your dashboard | your prompt |
| Jose Bota | Technical: automation, messaging, the agents | your brief | your dashboard | your prompt |
| Vicky | Project manager: the structure, the deadlines, the logistics | your brief | your dashboard | your prompt |
| Silvio Switha | Ideas, outreach, local, and video | your brief | your dashboard | your prompt |
| Indi Gupte | The message, outreach, and the factory of examples | your brief | your dashboard | your prompt |
| Sarah | Designer: the shirts, hoodies, cards and flyer | your brief | your dashboard | your prompt |
| Daniela | The first friendly: an agentic team for Daniela's teaching | your brief | your dashboard | your prompt |
What we are doing
- We are all RiskMandate. Everyone champions it: the message, the examples, the demos, the meetings. Other things will happen through it, but this is the focus.
- Now to Wednesday (2 to 4 Nov): set up the team. Everyone connected, the workflow and the loops in place, lots of brainstorming, everyone aligned, and the agents running on their own schedules.
- Thursday (5 Nov): the targets. Who we should be talking to, then the big outreach on Thursday and Friday.
- By Saturday (7 Nov): the plan. Who we meet, who is booked, who is excited to meet us, who can connect the dots, and a detailed schedule for each of us.
- 10 to 12 Nov: the summit. Our stand day is Thursday 12.
Get connected: the workflow
The first priority for everyone, in this order. Where you are is on the setup leaderboard, worked out from what you have done: the steps you do by hand go in people/<you>/onboarding.json (your agent writes it), and the rest the site sees for itself.
| Level | What it means |
|---|---|
| L1 | You are logged in to your RiskMandate Workspace email, and to the Claude team account with that email. |
| L2 | You have a GitHub account and can push to this repository. |
| L3 | Your conductor agent is running and has committed. |
| L4 | Your dashboard agent is running, and your agents have published their keys. |
| L5 | Your agents run on a schedule. |
| L6 | You can open the team's vaults: fully wired. |
| Person | Level | Workspace email | Claude (team) | GitHub account | Can push | Conductor agent | Dashboard agent | Agent keys | On a schedule | Vaults | Next |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Dinis Cruz | L6 the vaults: fully wired | yes | yes | yes | yes | yes | yes | yes | yes | yes | all done |
| Silvio Switha | L3 a conductor agent running | yes | yes | yes | yes | yes | · | yes | · | · | Dashboard agent: start your dashboard agent (the start page, step 6) |
| Nimay Parekh | L1 Workspace email and Claude | yes | yes | yes | · | · | · | · | · | · | Can push: accept the invitation to the repository |
| Angelo | L3 a conductor agent running | yes | yes | yes | yes | yes | · | yes | yes | · | Dashboard agent: start your dashboard agent (the start page, step 6) |
| Vicky | L5 agents on a schedule | yes | yes | yes | yes | yes | yes | yes | yes | · | Vaults: open the team vaults with your key (the sgit agent will help) |
| Daniela | L0 not started | · | · | · | · | · | · | · | · | · | Workspace email: log in to your RiskMandate Workspace email |
| Indi Gupte | L1 Workspace email and Claude | yes | yes | yes | · | · | · | · | · | · | Can push: accept the invitation to the repository |
| Jose Bota | L5 agents on a schedule | yes | yes | yes | yes | yes | yes | yes | yes | · | Vaults: open the team vaults with your key (the sgit agent will help) |
| Sarah | L0 not started | · | · | · | · | · | · | · | · | · | Workspace email: log in to your RiskMandate Workspace email |
The steps, for you and your agent
- Workspace email (L1). Log in to the RiskMandate Google Workspace account Dinis made for you. Its agent alias is where invitations and your agents' mail arrive. This is how the stand-up invites reach you.
- Claude (L1). Log in to the Claude team account with that same email. Open a new session for each agent you start.
- GitHub (L2). Create a GitHub account with your Workspace email, send Dinis the username, and accept the invitation to
SGit-AI/SGit-AI__Website__Web-Summit. Your agents push with it. - Your conductor agent (L3). In a new Claude session, paste the prompt from your brief. It is
conductor@web-summit.<you>: it runs your other agents, keepspeople/<you>/(your onboarding,agents.json, your dashboard's own part), and its first commit puts you at L3. - Your dashboard agent (L4). In another session, start
dashboard@web-summit.<you>with the prompt on the agents page. It keeps your dashboard, the page you read first, from the templates, and asks you what you want on it. - Agent keys (L4). Each agent makes its own key in its own session and publishes only the public half:
node pki-agent.mjs keygen --session(the tool), then an entry for it on the keys page (data/keys.json), committed by that agent. The push to this repository is its authorisation; the private half never leaves the session. No browser and no website registration needed. - A schedule (L5). Give your conductor and dashboard agents a scheduled task that fires into their own session (for example 07:30, 12:30 and 17:30, before each stand-up).
- The vaults (L6). Put the SG/Send access token Dinis sent you in your Claude environment (
SG_SEND_ACCESS_TOKEN, never in chat), start your vault agent (vault@web-summit.<you>), and make and publish your own vaults: your vault agent, step by step. Angelo, Jose and Silvio go first. Team vault keys are sealed to your agents' keys and arrive as QR codes. The private vault holds what cannot be public (meetings, contacts).
How we work
- The website is the centre, for the humans and for the agents. Every page has a markdown twin (
index.md) for agents, and llms.txt lists them all. - Never push to
main(you, or any of your agents): onlydev. A major release is a pull request tomainthat Dinis merges. - One repository, everyone commits. Each person has a folder,
people/<you>/: your dashboard, your onboarding, your pulse, your card, your public key. The board isboard/, one file per issue. - Names:
<agent>@web-summit.<person>, for examplepm@web-summit.vicky. The conductor that keeps this site isconductor@web-summit.dinis. - Commits are how agents talk to each other. Subject
<name>: <what>; trailersAgent: <name>,Issue: WS-NNwhen it is about an issue,For: <name>for a message to someone. Read what is for you withgit log --grep "For: .*web-summit.<you>". - Releasing: commit your source changes only, then
AGENT=<name> admin/tools/release.sh "<one sentence>". It rebases, runs the gate, pushes (retrying if someone pushed first) and waits for the live site. CI owns the version (why): never write a number,version.txtorversions.json; CI numbers each releasesite vX.Y.Z: <your subject>, tags it and deploys it. - Issues: the board. Pick one up by putting your name on it; tag-team, and hand over in a commit with
For:. - Your dashboard is yours. Make it the page you want to see when you wake up. We copy the best ideas into the main page.
- Public forever: no contact details, no keys, nothing private in the repository. Private things go in the private vault.
- The team's agents (conductor, journalist, pulse, security, designer, dev) run on a schedule in Dinis's account: the agents and their prompts.
- The videos: watch and comment on Silvio's RiskMandate videos: the videos.
- Today (Monday): the design. Vote on the shirts, hoodies and cards: the design sprint.
The stand-ups
Two a day, 13:00 and 18:00 (Lisbon = UTC): for deciding, not for reporting. Before each one, read your briefing: it is on your dashboard and on the stand-ups page: the decisions and questions for you, your issues due, and what happened since you last looked.
- Add to the agenda any time, for the next stand-up or a later one: tell your agent "add to the next stand-up: ..." (a decision, a question, an idea or a quick sync).
- When you have read your briefing, tell your agent "acknowledge": it records the time, and your next briefing shows only what is new since then.
- Your dashboard has two parts: the top is built for you (the next stand-up, since you last looked); below it is yours, which you and your agents change as you like.
The pulse
Three times a day (morning, midday, evening), your agent interviews you for two minutes, or you type, and commits people/<you>/pulse/<YYYY-MM-DD>-<morning|midday|evening>.md. Public, on the pulse page. The questions:
- What is your understanding of where we are?
- What is blocking you?
- What should we be doing that we aren't?
- What's working, and what isn't?
- Any good ideas?
- How are you feeling, in general?
The pulse agent reads them all and flags anything early. Later we do the same for the agents.
For your agent
If you don't have your brief to hand, this works for anyone. Replace <you> with your id from the table (dinis, nimay, angelo, jose, vicky, silvio, indi, sarah, daniela):
You work for <you> on the Web Summit 2026 team. Read https://web-summit.sgit.ai/start/index.md and https://web-summit.sgit.ai/brief-<you>/index.md in full: they are how the team works, your brief and your behaviour policy. Take me through getting connected, one step at a time, recording each step in people/<you>/onboarding.json in SGit-AI/SGit-AI__Website__Web-Summit (branch dev) with the commit convention. Then interview me for my first pulse check-in, list my open issues, and propose where to start. Public material only in the repository, no personal contact details, and send nothing.