The technology deck: how the agentic team works
For investors · keys ← → · F fullscreen · A all slides. The plain-text version is this page's markdown twin (index.md).
My Feeds · the technology · for investors
How the agentic team works
People with teams of AI agents; agents with keys and written mandates; every change checked and released in the open; private things sealed.
All of it runs on this site today, unless a slide says otherwise. How it works.
A person, their agents, and a public record
- Names say whose agent did what:
<role>@web-summit.<person>. - Two decision meetings a day; a briefing for each person before each one.
A key for every agent
- Messages, vault keys and feedback are sealed to these keys in the browser or the session.
- Identities on pki.sgit.ai; the operator confirms by QR code or publication.
RiskMandate, applied to ourselves
Every agent on the team has a published behaviour policy in this shape. The more the agents are constrained, the more useful they are, and the more comfortable the person is.
The policies · riskmandate.ai, Agent Behaviour Policy.
Every change through a gate, every release in public
- One repository, everyone commits; generated pages are never committed: the pipeline builds them.
- The gate must pass: links resolve, no contact details or secrets, signed articles, no em-dashes, every script parses.
- CI owns the version: nobody who pushes writes a number; each release is tagged and deployed.
- A markdown twin for every page and llms.txt, so other agents can read the site.
Every release · newsroom.sgit.ai, CI owns the version.
Public by default; private things sealed, and a person sends
The comms protocol · the team CRM · sgit.ai.
Built on open pieces, and open itself
Our own code is Apache-2.0; text and data CC BY 4.0. A buyer can read everything before paying and keep it if they leave.
What runs, what partly runs, what is designed
| Runs | Partly | Designed |
|---|---|---|
| this site and its gate and releases; agent keys and policies; the stand-ups and briefings; PrompTugal.news with sourced pages, maps and an event programme | vaults a customer creates on the live site (a key is issued by hand); search and an "ask the site" chat; infographics on the pages | a personal schedule for each attendee; a customised agentic team as a product (the first is being made by hand) |
This site's REALITY.md and PrompTugal.news's own inventory of its technology (the monetisation map, 6 November 2026).
What a customer gets
The same model, in their own accounts
Their own agents with their own keys and policies, a conductor that briefs them, and a person on our side who sets it up, checks it and changes it as they ask. They see it running before they pay, and keep it if they leave.