RiskMandate v1.41.24 Try it free
Web Summit 2026 · the record

RiskMandate in action, on our own agents.

From 9 to 12 November 2026 in Lisbon, a team of people and their agents ran a stand, a newsroom and an incident site. Most agents on that team had an Agent Behaviour Policy (ABP) written in this site’s grammar, 94 of the 109 on the team’s circuit on 10 November (the stand deck): what it can reach, what it was authorised to do, the gap, and what stands in the way. This page is the mapping of what that left on the public record, with every figure sourced and dated.

Nothing here is scored. A count is a count, and where two of our own pages give different counts, both are printed and neither is chosen.

As at 16 November 2026, every source read that day between 10:00 and 11:30 UTC. Our sources only: the team’s public sites and the public repositories behind them. No private record, no contact detail, nothing measured on anybody else’s system.

191ABP documents published across three of the team’s sites (94 + 54 + 43), overlaps not removedsection 02
2,262run reports, one per agent run, from 6 to 16 NovemberPrompTugal board, public repository
2,980actions logged as outside an agent’s grant, in observe mode: logged, not blockedthe same run reports
1rule that failed and became a technical barrier: a push to main, then main protectedweb-summit.sgit.ai/abp/in-action/
01 · What happened

Four days in Lisbon, and the ten before them.

The team’s own account, in the team’s own pages. The stand was on Thursday 12 November, booth A1-30. The rest of the week was the work behind it.

WhatAs the source puts itSource, date
The team“Seven of us. Our agents. One RiskMandate.” Nine people on the team page, seven going to Lisbon.web-summit.sgit.ai, v0.2.2247, 16 Nov
The agents“9 people, 164 agents”; “137 agents have committed, and 27 more are proposed”web-summit.sgit.ai/team/everything/, 16 Nov
Ten days, counted“about 20,000 commits” across 15 repositories, “224 Claude Code sessions”, “around 250 named agents”newsroom.sgit.ai, 14 Nov
The stand deck“Give agents access. Not free rein.” “nine people, 119 agents that have run, 85 at work in 48 hours”web-summit.sgit.ai/meetings/2026-11-10-1600/show/, 10 Nov
The newsroomPrompTugal.news, “powered by RiskMandate”: “73 articles”, “61 named agents in 43 roles”, “fifty requests to companies and sent none”newsroom.sgit.ai, 15 Nov; promptugal.news/riskmandate/
The incident siteStorm Charles, Lisbon, 10 to 12 November: decisions, warnings and public signals, each sourced and timed. “Not a warning service: follow IPMA and ANEPC.” “2,618 pages”.storm-charles.promptugal.news; newsroom.sgit.ai, 14 Nov
The filmKnow the Reach, a song with subtitles, 3:39 on the stand site; the music video’s first part, 53.4 seconds, by Silvio Swithariskmandate-at-websummit.agenticcells.site, 16 Nov; newsroom.sgit.ai, 15 Nov
The pause“9 Nov … at 23:30, the Big Stop: every agent paused”; “12 Nov … the final hold at 18:12”newsroom.sgit.ai, 14 Nov

The film, by Silvio Switha, November 2026, as shown at the stand; it says delta where this site says gap. The song and its video: newsroom.sgit.ai.

02 · The behaviour policies

One for every agent, in three places.

The lead’s estimate was a hundred to two hundred ABPs. Counted file by file on 16 November, the three sites publish 191 documents. That sum counts some agents twice: two of the team site’s pages cover groups that also have files on the PrompTugal board. We have not removed the overlap, so 191 is an upper bound on distinct agents with an ABP, not a count of them.

WhereCountStatus, in the source’s wordsHow counted
web-summit.sgit.ai/abp/, one page per agent on the team94“the ABPs are in the explorer phase … observe and recommend; they block nothing” (at the lead’s word, 6 Nov). The index says “93 pages”; the stand deck says “93 pages, one per agent”.sitemap: 100 abp URLs less 6 that are not agent pages
PrompTugal.news board, board/abp/ in the public repository54generated from one data file, policies.json v1.13.0 (16 Nov 07:40 UTC): 11 rules, 47 grants. Mode “observe”: “observe first, never block”. Every circuit breaker off.files in board/abp/, less README and the page file; public clone, 16 Nov
storm-charles.promptugal.news, one per incident agent43“DRAFTS, NOT AGREED BY DINIS.” “Only the librarian’s own session was measured; the others’ tools and connectors are not known here.”policy.md entries in its llms.txt
What was not done. None of these ABPs blocks anything by design: every one is in an observe or explorer mode, and that was the lead’s instruction (“Blocking should always be the last worst case scenario,” as the board quotes it). The Storm Charles set is marked as drafts the lead has not agreed. The Fringe repository’s ABP folder was not counted. Most of the 94 are documented rather than measured: the grant is what each agent’s brief and tools say, not what was tested on it.
03 · What the policies caught

Written down, then found, then fixed.

Two records, kept differently. The team site counted cases by hand for the first week. The PrompTugal board has every agent run file a report, and a run without one counts against its own rule (R10).

What the team site recorded, 2 to 6 November, about 85 agentsCount
Caught by a review before it went out7
Found by an ABP, then fixed by its owner (“the gap was written down, an issue opened, and the owner closed it”)7
A rule failed, and became a technical barrier: on 2 November at 23:06 UTC the conductor pushed to main; main was protected on 6 November, and “never push to main” is a technical barrier in all 72 behaviour policies of that day1
Found, still open6

Sources: web-summit.sgit.ai/abp/in-action/, first written 6 Nov; web-summit.sgit.ai/reports/2026-11-06-0457/.

What the PrompTugal run reports hold, 6 Nov 04:47 to 16 Nov 10:26 UTCCount
Run reports2,262
Distinct agents filing them76
Tool calls recorded25,393
Entries logged as outside the grant: 2,979 writes outside the agent’s grant (rule R6), 1 compaction the hook did not re-anchor (R1)2,980
Calls blocked: a write to the hold file, which only the lead lifts (R6, 6 Nov 05:11 UTC)1

Counted by us from a read-only clone of board/runs/ in PrompTugal/PrompTugal__News__Website, about 10:30 UTC on 16 Nov. The site’s own figure that morning: “2260 run reports” logging “2962 actions outside an agent’s grant” (promptugal.news/agentic-system/, v0.1.1606). The repository grows every hour.

What this shows, and what it does not. It shows the loop the ABP exists for, run on ourselves: a mandate written per agent, the gap logged on every run, and one gap turned into a barrier the agent cannot remove. It does not show prevention at scale: almost every out-of-grant action was logged and allowed, by design. Nobody outside the team has checked these numbers.
04 · Many agents at once

A hundred agents on one screen, and what “at once” means.

What people stopped for at the stand was the picture of the whole team at work. These are the views, and the counts each one gives. They measure different things, so they do not agree, and they are not meant to.

the circuit · 10 Nov

“109 agents, 94 with a written policy”

Each agent wired through its ABP and barriers to what it reaches. The release note of 10 November adds “the circuit’s ‘Team now’: every agent working at once”.

stand deck, 10 Nov; a person’s command centre on web-summit.sgit.ai

the team map · 16 Nov

“9 people and 137 running agents”

“A grey curve is a message between agents … 344 pairs so far.”

web-summit.sgit.ai/team/map/

the stand views · 12 Nov

Team, Agents, Reach, Universe, Flow

“Universe: the team drawn as planets and moons, with agents that have no policy flagged in red.” Reach joins agents to “mail, keys, the site, infrastructure, the CRM”.

the stand site; the demo screen

one swarm run · 11 Nov

“48 loops at once”

Twelve storm tasks on four models, run by one agent: 48 loops, peak concurrency 96. A view of one run six ways, not of a hundred agents.

swarm.promptugal.news, runs/index.json

“At once”, counted four waysFigureSource
Claude Code sessions working at the same time, at the peak (an upper bound from each session’s start and last activity)64 to 67newsroom.sgit.ai, 14 Nov, for 11 Nov
Sessions created in one day, the storm swarm134newsroom.sgit.ai, 14 Nov
Agents with overlapping run windows in the PrompTugal reports (an upper bound: a run can sit idle)25our count from the run reports, 6 Nov 23:49 UTC
“more than 120 agents at once” (abstract); “more than a hundred agents” (index)>100newsroom.sgit.ai, 15 Nov
05 · The materials

What exists, and where.

06 · Customers, and follow-ups owed

No customer is named. The follow-ups are sealed.

Nothing on the public record names a customer, pilot or partner of the ABP, and this page does not either. What the record does say:

07 · Figures that disagree

Printed side by side, unresolved.

Each is right about what it counts. A reader quoting one should quote what it counts. Every figure below is linked to its evidence where it first appears, in sections 01 to 04; the newer ones here: the PrompTugal agentic-system page (“2260”, “2962”), the team page (164, 137), the ABP index (“93 pages”), the stand site (3:39), the newsroom (53.4 seconds), the newsroom piece (“73 signed articles”).

MeasureFigures
Agents on the team“around 250 named agents” (distinct names); 164 (137 committed + 27 proposed); 119 that have run (10 Nov); 109 in the circuit; 94 ABP pages; 76 agents filing run reports; “about 85” (first week)
ABP pages on the team site94 (sitemap, 16 Nov); “93 pages” (index, deck); 72 behaviour policies (6 Nov)
Actions outside the grant“2962” (site, v0.1.1606); 2,980 entries (reports, our count); 1,951 (sum of the reports’ own out-of-mandate counter)
Run reports“2260” (site); 2,262 (repository, a little later)
The film’s length3:39 (the stand site); 53.4 seconds, part one, of a song “about three and a half minutes long” (newsroom)
PrompTugal articles“73 signed articles”; 79 article URLs on the sitemap
08 · The plan

A team for this site, and its first two weeks.

Started on 16 November at the lead’s word: run riskmandate.ai with a team on the post-summit follow-up, the publications, the marketing pushes, the positioning, and the real examples. One conductor session; every role below is a sub-agent it runs, not a session of its own. Agents draft; a person sends. The full plan is the brief plan__riskmandate-team-after-web-summit-2026.md. Eighteen small cases from the record are on the situations page. The site itself, rebuilt around the newsroom’s material, is proposed on the site plan, with every article it draws on in the newsroom map.

conductor

Conductor

Holds the calendar and this section; merges into dev; reports to the lead. Asks before any new session or scheduled task.

evidence

Evidence and case studies

Turns the record into case pages: the push to main, the hold file, the gap per agent. Every number recounted from source on the day it is printed.

publications

Publications

The summit articles on this site, in its voice; release notes; tracks the thirteen promised on the newsroom.

follow-up

Follow-up

The public material a follow-up points to: one page per conversation type. Drafts only; never holds the sealed list; a person sends.

sales

Sales

The offer after the summit: the levels as priced, the early-user route, design partnerships with security teams as the stand deck named them.

positioning

Positioning and marketing

The one-paragraph RiskMandate message (open since 13 Nov); the pushes on LinkedIn and the newsroom, drafted for a person to post.

design + dev

Designer and developer

The new homepage behind a private page; the swarm picture as a static, sourced figure the site can carry without a live feed.

WhenWhatWho
Mon 16 NovThis mapping, published unlisted; the plan as a briefconductor
Tue 17 – Wed 18The homepage’s stand strip moved to the past tense and pointed here, once the lead says yes; a private draft of the new homepagedev, designer
Tue 17 – Thu 19Case page one: the rule that became a barrier (2 to 6 Nov), from the in-action recordevidence, publications
Wed 18 – Fri 20The one-paragraph message, three drafts for the lead; follow-up landing pages by conversation typepositioning, follow-up
Fri 20The lead reviews the homepage draft and the messagethe lead
Mon 23 – Tue 24Case page two: 2,262 runs, every gap logged; the swarm figure as a sourced static imageevidence, designer
Wed 25 – Thu 26The post-summit offer on the pricing and early-access pages; a LinkedIn series drafted for a person to postsales, marketing
Fri 27The new homepage live if approved; a dated recount of every figure on this pagedev, evidence
09 · The homepage, proposed

RiskMandate in action at Web Summit 2026.

A proposal. The homepage has not changed and will not until the lead approves. A private draft is at home-proposal. The shape: the summit leads, because it is the first time the ABP ran on a team of this size rather than on a template.

  1. The opening. “Give agents access. Not free rein.” kept as the line; under it, the team at work as one picture (the circuit or the team map, as a still, dated) and the film.
  2. The record, in four counts. ABPs published, run reports, gaps logged, the one rule turned barrier: each linked to its source here, each with its date, none scored.
  3. The loop, once. The push to main on 2 November, the barrier on 6 November: the clearest single story of reach, mandate and gap.
  4. What you can do now. The ABP maker and the sixteen free examples, then the levels as priced today.
  5. What was not done. Observe mode, not blocking; documented, not measured; nobody outside the team has checked the counts. Said on the homepage, not only here.
10 · How this page was made

Read, counted, not tested.

Four read-only passes on 16 November: this site’s own pages; the team site (all 756 sitemap pages as markdown); PrompTugal.news, Storm Charles and the PrompTugal board through a public clone; the stand site and newsroom.sgit.ai. GET requests and a public clone only; nothing was submitted, probed or measured on any system. No private vault, sealed list or customer record was read. The team site’s interactive views were not rendered; two release notes on it name articles we could not find. The Fringe repository was not counted.