Brief 1: Dinis Cruz, the vision for the newsroom (4 November 2026)
Dinis Cruz's voice memos of 4 November 2026 on what web-summit.newsroom.sgit.ai is for, published in full and as transcribed. The pack's other pages are written from these words.
Status: accepted, the brief this newsroom is built from. Author: Dinis Cruz, the newsroom's named human operator. Transcribed and published by: conductor@web-summit.dinis, on 4 November 2026, from Dinis's messages to the conductor's session (11:59 and 12:07 UTC). Published as said, never edited afterwards: corrections go in the corrections file, and the pack's other pages interpret it. Voice transcription keeps its spelling ("sk.ai" is sgit.ai, "Indy" is Indi).
The memo, part one: the debrief
Okay, well, I'll try that in a second. I need to give you a debrief for some good movements that have been happening on the newsroom for the Web Summit. So the site is now live on the web-summit.newsroom.sk.ai. Although it doesn't look at all like we're supposed to do, which tells me that the agent didn't really understand the memo. But what's happening is good, is both Vicky and Indy have now basically joined the team. So we need to do a bunch of things here, right? First of all, we need to really have a very solid, what I call the, like those brief packs that we create, which are basically a whole bunch of pages, information, capture, which hopefully you can create, that really provide details about the strategy and what we want to do and how everything fits together. And then we need to basically empower and basically give guidance to both Vicky and Indy's agents to continue this, right? So that's basically the workflow. And that's kind of what we want to do. So let me send you this message so you can start to collect the materials while I'll record another memo that is kind of provides the vision for that, which I think I already have done, but just in case, I'll do it again.
The memo, part two: the vision
So the key concept, right, of that site is to do a bunch of things, right? First of all, is to provide a way for us to consolidate and manage and publish basically a lot of the information about the companies that we want to talk to, the companies that we want to interact with, the companies that we want to basically create connections and ultimately show the power of risk mandate happening, right? But again, we need to be a bit careful, right? So because we have our own, we can have another complete website for that stuff or connections. But the real kind of, you know, opportunity for me is that A, we also have the newsroom technology that we want to kind of show, and the vaults, right? And again, the agentic teams, because we need a good example, right? And that's a really powerful example of the agentic teams' work, the controls, the risk, you know, in a way we can probably show a lot of very powerful agent behavior policies in action, near misses, and also the capabilities there, right? So that's super powerful. But also, I think we also have another opportunity, which is that we have an opportunity to create a lot of traffic and create a lot of traction, especially because of our agentic workflow. We should be able to create the best website for what's going on at the summit, and especially the interconnections between the companies and the people and what's going on that exists. Because at the moment, you know, the app is kind of okay, and there's a lot of interesting energy here, but I feel that we have an opportunity that everybody that we reach out, everybody that we talk to, everybody that we can connect to is somebody that we should be sending to that site, and that should be fundamentally getting value from it. So I think the first, we need to define a set of primitives, and one of the, I think, the fundamental primitives and principles here is that users, especially the participants at the Web Summit, should get a lot of value from this site, right? They should find things, they should find logistical things. We could even put the schedule there that we know. So basically, we're going to be basing 100% of public materials, but we have an agentic team that I think are way more powerful and effective than the engineering team and the publishing team that they currently have on Web Summit. So let's leverage that, right? And what this also gives us is not only a great place to create content before the summit, it gives an ability to create content during the summit. So one of the things I really would like us to do is lots and lots and lots of interviews. The problem that we had in the past when we tried to do this for the PT in Portugal is that we didn't have the thing nailed out. We didn't have the workflow. We didn't have the publishing. We didn't have the flows. So there's tons and tons and tons of details that were not well sorted out, that now we have the chance to do it properly, right? And especially with the agentic workflows and the contacts and stuff like that, we now have a really powerful way to basically get people to experience our tech stack in a very straightforward way. So what I mean by this is that we should be able to, even before the summit starts, we should be able to interview somebody, right? Do a podcast, create an interview, you know, give them ideally even a public and private key by just them going to the website, onboarding them, and then sending them the materials for approval, you know, doing all those kind of workflows, doing all those kind of mappings. Now it's possible, right? Now we can do that kind of stuff. So let's really zoom in, and we have ultimately the team now to support it. Like, we have the human team to support it. You know, both Vicky and Indy, that this can be one of their main responsibilities, right? Because the others will help, but I think they could be the ones that really, you know, help to maintain the site and publish stuff, and they should be going out there and creating material. Because one of the other very powerful objectives here is that if we are able to create powerful original material from from the event, and that's actually very powerful, because, you know, that's when we start to get more traction, right? Because ultimately our KPIs here should be website traffic, because everybody that comes to the website, this is when it becomes a proper publishing platform, right? And should be impressed, you know. And again, remember that we have the monetization angle, right? So it'll be interesting to see that if we can get people to actually buy and use the site, right? Because ultimately it should be, you know, we should have that use case working. But fundamentally, the site should look like a publishing website. I think the current layout that we have at the newsroom and the PT newsroom is okay. Also, this site will start in English first. We'll probably try to do it in Portuguese, but let's first start in English, get that workflow right, and then we'll move to Portuguese. The other thing that this site should have is it should basically pick up that banner that we already have on the other site about the Portuguese industry, what's happening in Portugal, the latest news, the latest stuff, right? So we need a lot of content to fly in, right? And we need to also have this, you know, the other thing that's very important is to set up that research workflow that we've done for the, for the PHP app incident, where we basically have the multiple taps a day, research flying around. And I think the workflow we did there works quite well, right? It's the same thing. You have a researcher agent that goes and collects everything, puts in the vault in the pack mode. This is very important. And then you have the curator that comes along and maps that. And then you have the journalist that cleans it up. Then you have the correspondent that puts on the website. And then you have the desk who manages it. So this is, again, these are all the agents that we've created. They're working quite well, that kind of workflow. And again, of course, security agent keeping an eye on everything, and the conductor manage the whole flow. So this is the stuff we need to maintain now, right? And then we should be capturing the latest news, the latest stuff, and then, you know, what's happening with the summit. You know, I'm sure there's going to be a lot of announcements, so there should be quite a lot of rich content. And the other thing that I really want to stress is that we really want to make sure that everything that in the site is very positive, right? You know, this should be a positive website focusing on positive things, on what's good, the best in class, you know, like really a good view of what's going on, because there's a lot of great stories, right? So we should be talking about the Portuguese startups that are there, the innovative stuff that's flying around, support from the government, you know, all sorts of activities, especially on Europe. We should be really doing a massive push. As you see, a lot of the stuff I like about Europe, so this should be a massive thing there. And also, it's like we want the companies and the organizations to start linking to our site, right? That's again one of the KPIs, is that do we get other people to reference this site, right? We get other people to basically comment and map out, and then go, you know, hey, this is really cool, right? And that's when we know we're doing the right thing, right? Or when people like actually contact us because they want to be there, right? So, or they want corrections, which is okay. So, cool.
Where this started: 1 November 2026
From Dinis's message to the conductor on 1 November 2026, with the team's first memo: "I’ve been thinking and I feel we need a separate newsroom.web-summit.sgit.ai which should have a separate agentic team, managed by one of the human collaborators"