<!-- Generated from web-summit-2026/site-plan.html by scripts/site/generate.mjs. Edit the page, not this file. -->

# RiskMandate — The site plan: riskmandate.ai rebuilt around the newsroom

A proposed shape for riskmandate.ai after Web Summit 2026: sixteen pages and sections, what moves, what is rewritten, and which newsroom.sgit.ai articles feed each. A proposal; nothing on the live site has moved.

Source: https://riskmandate.ai/web-summit-2026/site-plan.html

---

# The site, rebuilt around what we already wrote.

The lead says the site needs a lot of work, and that the material for it is on newsroom.sgit.ai. We read all of it that touches RiskMandate. This page is the proposed shape of riskmandate.ai: the pages and sections, what moves, what is rewritten, and which newsroom articles feed each page.

**A proposal.** Nothing on the live site has moved. The homepage is untouched until the lead says yes; its draft is a private page in this section.

**As at** 16 November 2026. Read from newsroom.sgit.ai v0.14.124: 434 articles in its wire, five collections, six desks, the sections and the two features the lead named. Every row of the reading is on [the newsroom map](/web-summit-2026/newsroom-map.html).

## The lead’s brief changes the plan: we can control your agents.

The same night, the lead dictated one brief for riskmandate.ai and agenticcells.ai together ([recorded with his words](https://github.com/Risk-Mandate/riskmandate.ai/blob/dev/docs/briefs/direction__we-can-control-your-agents.md)). Where it differs from the shape below, it wins.

- **One message.** “We can control your agents”, from one agent to hundreds; less theory, more proof. The homepage draft is rebuilt around it: [home-proposal](/web-summit-2026/home-proposal.html).
- **Situations, small and large.** Real cases from our own agents (a permission needed, a gap found, a rule that failed and became a barrier) beside the hundred-agent picture. A situations page moves to the top of the backlog.
- **An honest order of strength.** A policy first (“a lot of value for money right now”), then hooks, then a boundary with SHarness. Open source, no lock-in.
- **One ladder with agenticcells.ai.** £500, £1,500, £5,000, £20,000, proposed; the live prices stay until the lead confirms. The two sites link each other: a policy alone is RiskMandate, a team is AgentiCCells.
- **An archive.** Older pages move out of the menu and are kept. This replaces most of the rewrites in section 03: a page that does not serve the message goes to the archive rather than being rebuilt.
- **The film, the photos, the book.** The film on the homepage; Web Summit photos of people who agreed; _One Human, Nine Agents, Nineteen Hours_ with its Leanpub link.
- **A team on an hourly loop.** Developer, designer, sherpa, synthetic users, ambassador, researchers, as sub-agents of one conductor; the backlog is task brief T18.

## The argument is written. The site does not carry it.

The newsroom has been writing RiskMandate in public since August, an article most days. The site carries sixteen example ABPs, four levels and a model; the newsroom carries the reasons, the measurements, the case of our own agents, the insurance argument and the replies to people who disagree. Five things stand out.

- **Where a rule is kept is the idea that recurs most.** Prompt, hook or boundary; expectation, setting or boundary; “a rule the agent can rewrite is a setting”. Thirty-three of the items on the map feed it ([Hope or enforcement](https://newsroom.sgit.ai/articles/hope-or-enforcement.html), [Where a check runs](https://newsroom.sgit.ai/articles/where-a-check-runs.html), [Proven controls for agents](https://newsroom.sgit.ai/articles/proven-controls-for-agents.html): “22 were expectations, 34 settings and one a boundary”). The site has no page for it.
- **The insurance argument is a series, not a page.** Five articles of 28 October and the whole-story piece rebuild `insurance.html` into a family ([Insuring agents, the whole story](https://newsroom.sgit.ai/articles/insuring-agents-the-whole-story.html), [A payout for every row](https://newsroom.sgit.ai/articles/a-payout-for-every-row.html)). They say themselves that no insurer has agreed to any of it.
- **Our own agents are the first case.** The summit record, [the ultimate insider](https://newsroom.sgit.ai/articles/the-ultimate-insider-case-study.html), [six agents, one inbox](https://newsroom.sgit.ai/articles/six-agents-one-inbox.html), the push to main. And one measured workflow on a system we are entitled to run: [our workflow on Odoo 20](https://newsroom.sgit.ai/articles/our-workflow-on-odoo-20.html), 25 probes.
- **There are vendor-shaped examples, read from documentation.** Manus, Cloudflare and Lovable, each “from [the vendor]’s documentation, read on 9 November 2026”, never run. They belong beside the sixteen, marked as documented.
- **The two features the lead named are the reviewed level, explained.** [Local trust, certified upwards](https://newsroom.sgit.ai/articles/local-trust-certified-upwards.html) says the person closest to a story vouches for it and the vouching travels up; on this site that is the reviewer closest to the deployment signing the ABP for a buyer or an insurer. [Sources and their shadows](https://newsroom.sgit.ai/articles/sources-and-shadows.html) is our rules 4 and 8 written as a method: every reference with its access, its quote and its date, and disagreements kept unresolved.

## Three entries, sixteen places.

The header stays at three entries and one button. _How it works_ becomes _In action_, because what the newsroom gives us is evidence, and the reading moves inside it. The number beside each is how many newsroom items feed it; the map lists them.

### What an ABP is · 11

Rewritten around reach, mandate, gap and barrier, with _the behaviour policy is the business logic_ and drift as the mandate moving. Today: `abp.html`.

### Where a rule is kept · 33

Prompt, hook, boundary; the enforcer test; the 57 checks; SHarness as the boundary when you want one. Absorbs `grant-gap.html`’s argument; links `secure-harness.html`.

### Levels and pricing · 10

Kept as priced. Fixes the level-1 price that reads £5 on one page and £10 on others, which the newsroom’s ten questions noted on 9 October.

### Reviewed upward · 5

The reviewed level and the reviewers, explained through _local trust, certified upwards_: the signature of the person closest to the deployment, carried up. Today: `abp-reviewed.html`, `reviewers.html`.

### Who it is for · 15

Corporate, founders, startups as now; a regulators page from the FCA crosswalk is proposed; the replies to named arguments (_the same argument_) as a strand.

### Insuring agents · 24

The 28 October series as a family: who carries the risk, a payout for every row, the underwriting blueprint read, the filing’s ten risks. Licence to Operate and the Index stay on the roadmap, labelled design.

### Web Summit 2026 · 11

This section: the record, then the summit articles as its reading.

### Case studies · 16

The rule that became a barrier; six agents, one inbox; the ultimate insider; Odoo 20 measured; the chat-only line under attack; our first merged change in Ruflo.

### Example ABPs · 27

The sixteen and the library, with skill policies and system prompts read as ABPs.

### Vendor-shaped examples · 8

Manus, Cloudflare, Lovable, Odoo, WSO2: documented from vendor pages, dated, never run, contradictions published.

### Invented twins · 3

Pellbridge, Northstar, Thistlewood: every one labelled invented at the top. Today: `demos.html`.

### Try it · 4

The rules, the ABP maker, write your first ABP. Today: `try-it.html`, `rules/`.

### What runs, what is designed · 1

The newsroom’s `/shipped/` page, done for us: every product claim with built, designed or proposed beside it, dated. Rule 8 as a page.

### Reading paths · 38

`articles.html` organised by reader: start here; the ABP in practice; deciding and stopping; insuring agents; provenance and review; for founders.

### Questions · 11

`questions.html`, with the ten questions of 9 October folded in.

### The team and how it runs · 26

Unchanged in place; fed by the mandate stack and the team series. SHarness, the Open Security Summit and the code stay here.

## In order of what a visitor meets first.

| # | Change | Fed by | Size |
| --- | --- | --- | --- |
| 1 | The homepage: the summit leads (draft: [home-proposal](/web-summit-2026/home-proposal.html), private). **On the lead’s yes only.** | the summit record; what can your agent reach | two days |
| 2 | New: _Where a rule is kept_, one explainer | hope or enforcement; where a check runs; proven controls; are hooks the sweet spot | a day |
| 3 | New: _What runs, what is designed_, and every page’s claims checked against it | the newsroom’s shipped page; the ten questions’ maturity table | a day |
| 4 | New: case studies, two first (the rule that became a barrier; Odoo 20 measured) | the summit record; our workflow on Odoo 20 | a day each |
| 5 | Rebuilt: the insurance family from the 28 October series | the five insurance articles; the blueprint reviewed | two days |
| 6 | Rewritten: `abp.html` around the four words, and `articles.html` as reading paths | the business logic; drift; the collections, updated | a day |
| 7 | New: vendor-shaped examples, three first | Manus, Cloudflare, Lovable mappings | half a day each |
| 8 | Fixed now: the level-1 price on every page agrees | the ten questions, 9 Oct | an hour |
| 9 | Renamed: _How it works_ to _In action_ (a menu change: every page, merged the same day) | — | an hour |

## Settled before anything is carried across.

The newsroom is the lead’s thinking out loud; the site is what we sell. Where they differ, the site’s rules win and the difference goes to the lead.

- **Prices.** The site: £10, £50, £500, £1,500, one-off. The newsroom also proposes prepaid credit (£5 or £50), services at £5,000 and £25,000, and one ladder for every site at £500 to £20,000. All are labelled proposals there. Nothing changes on the site without the lead.
- **The roadmap.** The site: ABP, Licence to Operate, Insurability Index. The newsroom’s roadmap of 20 October has six stages and calls itself “a proposal, not a decision”.
- **Words the site does not use.** Some articles use conformity words, a scale of levels for deciders, a traffic light in a collaborator’s app, or verdicts on named companies. Those passages are not carried; the map marks each one.
- **Claims as if shipped.** The ten questions of 9 October found the site describing continuous attestation and a first Index as if built. The _What runs_ page is where that is settled.
- **Invented examples.** Pellbridge, Northstar, Thistlewood, Tallyline and others are invented. Each carries the word at the top, wherever it appears.
- **Counts that move.** One article gives 2,032 run reports; the summit record, a day later, 2,262. A count is reprinted with its date or not at all.

## Read, not rewritten.

The agents that read the newsroom skimmed each article from its abstract, its short list and its “what this does not claim” section, and read in full where a figure or a caution needed it. A row on the map is a pointer, not a reprint; every page built from it rereads the article first. No page on the live site was changed; the menu was not changed; nothing was sent to anybody.
