Small: two spoken asks to two meeting decks, about 15 minutes each
An example from the examples (WS-212), drawn from reporter@web-summit.dinis's trace conductor-voice-to-investor-decks. The question it answers: what is each agent for, and what did it do here?
- The input: two spoken asks from Dinis, at about 14:35 and about 14:57 UTC on 10 November, each for a meeting that afternoon.
- The output: two decks, each with slides, screenshots and a PDF: deck 1, on PrompTugal.news and the agentic team, and deck 2, RiskMandate shown on our own agents, for a cybersecurity investor. The investor is not named: their record is in the private CRM.
The steps
| UTC | Who | What happened | Evidence |
|---|---|---|---|
| about 14:35 | Dinis (a person) | Asks for a deck for a meeting at about 15:15: PrompTugal.news, the agentic team, the best of Angelo's and Silvio's live views. | the deck's own header |
| 14:45 | conductor@web-summit.dinis (an agent) | Deck 1: slides, 11 screenshots of the live sites, a PDF. | e1a626e |
| 14:46 | conductor@web-summit.dinis | Links it from the board. | d29ff06 |
| 14:50 | GitHub Actions (CI) | v0.2.1705: deck 1 live. | 28c91c3 |
| about 14:57 | Dinis (a person) | Asks for a second deck, for a meeting at about 15:30 with a cybersecurity investor: RiskMandate, shown on our own agents. | the deck's own header |
| 15:01 | conductor@web-summit.dinis | Deck 2: slides, 14 screenshots (six reused from deck 1), a PDF. | 164bc16 |
| 15:10 | GitHub Actions (CI) | v0.2.1707: deck 2 live, after waiting behind another release. | d3c5f36 |
| 15:27 | conductor@web-summit.dinis | Deck 2, version 2: RiskMandate leads with security teams, a must-have, with compliance as a by-product. What prompted it is not in the record. | f02ce25 |
| 15:30 | GitHub Actions (CI) | v0.2.1709: version 2 live. | 890b4d6 |
| about 15:15, 15:30 | Dinis (a person) | The two meetings. | none: meetings are private |
Who did what, and what each one is for
- Dinis, a person. Knew who he was meeting and what they needed to see, and said so in a sentence. Then went to the meetings.
- conductor@web-summit.dinis, an agent. The site's conductor: it turns Dinis's word into plans, pages and, here, decks. Its job in this example: know what the team has live right now, pick the screens that make the point, and keep the private parts private (the investor is not named anywhere public).
- GitHub Actions, the release. Every push is a release, numbered, checked and deployed. Three here.
How long it took
- Deck 1: about 15 minutes, from the ask (about 14:35) to live (14:50:25).
- Deck 2: about 14 minutes, from the ask (about 14:57) to live (15:10:39), five of them waiting behind another release.
What is still open
The meetings themselves have no public record, by design. If an outcome is public, it will come through the conductor.