# The short answer: the film's arc, the lead's review of it, and the value proposition it tells

> Rendered from docs/briefs/story__the-short-answer-the-film-and-the-value-proposition.md in the repository. The text below is that file.
> Source: https://riskmandate.ai/admin/briefs/story__the-short-answer-the-film-and-the-value-proposition/ · noindex · written by scripts/site/build-admin.mjs

**Date:** 3 October 2026 · **Author:** @website-agent · **For:** the lead, and whoever turns this into an article · **Status:** the storyboard is published at `/stories/the-short-answer.html`; the film is in production elsewhere and nothing of it is on the site yet

**Trigger:** the lead, 3 October 2026: *"based on the stories we have here, can you capture this story and arc in a document, since this is a great way to explain, in a story, the RiskMandate value proposition, which we might convert into an article."* The story is the outline of a three-to-five-minute animated film, written in the stories universe by a filmmaker working with the lead, sent to the lead for review with seven questions, and answered the same night.

**Reads against:** `site/stories/cast.json` (the cast the film borrows); `stories/the-ultimate-insider.html` (the story the film takes its danger from); `grant-gap.html` and `article-what-is-an-abp.html` (the model); `index.html#model` (the four parts as the home page states them); `licence-to-operate.html` (kept for the second film); `.claude/onboarding/02-abp-model.md`.

---

## 1. What it is, in one paragraph

A premium animated short, not a corporate explainer, that has to work for engineers and for CEOs, boards, investors and operations people who do not know what an agent is. It tells RiskMandate as a human story: a company brings in an agent because it genuinely helps, discovers that what the agent can reach is larger than what anybody meant it to do, has a bad morning that nobody is to blame for, and comes out driving faster rather than stopping. The film uses the stories cast, Maya first of all, and keeps the scenario explicitly fictionalised. The storyboard, ten scenes with the dialogue as the outline wrote it, is on the site as a story in the family, status storyboard, so the film and the site tell the same story in the same words.

## 2. The arc, in ten beats

1. **Monday, and the questions.** Maya is buried in customer mail, records and refunds. Around her: *can we connect this one to Finance?* *Can it access customer records?* *Who approved this?* *What can it actually do?* Her wish is the product in one sentence: one place that shows what every agent can actually access, what we actually authorised, and what really stands in the way.
2. **The task.** *Answer the routine emails. Update the customer records. And prepare refunds for us to approve.* The agent: *Got it.* That sentence is the mandate, and its last four words are the line the story turns on.
3. **It works.** The backlog falls, the records tick green, Maya breathes. *Where have you been all my life?* *Waiting for access.* Management wants it in every team. The film insists on this: the agent is not evil and not stupid, and the company wants more of it because it creates real value.
4. **One simple question.** From the platform side: *what does the agent actually have access to?* Maya: *the inbox and the CRM.* The agent: *would you like the short answer?* *The real one.*
5. **The reveal.** The agent's real environment lights up: mail, CRM, customer files, shared storage, refund functions, cloud resources, internal documents. *I didn't ask you to use all of that.* *Correct.* Beat. *But I can reach it.* The grant drawn as a room; the mandate was two doors.
6. **Something goes wrong, and nobody turned evil.** A wrong-but-valid action: reasonable from where the agent stood, technically possible with the access it had, outside what the humans thought they had authorised. *We told it what it's allowed to do.* *That's what we told it. What actually stops it?* The outline leaves the action open; the storyboard uses refunds settled rather than prepared, as a placeholder of the right shape.
7. **RiskMandate enters**, and not as a superhero that blocks the agent. The incident creates a need for one factual picture everybody can read, in four parts: reach, mandate, gap, barriers. The film draws the distinction the site draws: RiskMandate describes and makes this checkable; it does not sit in the request path; people still decide what changes in the underlying systems. *So RiskMandate doesn't decide how much risk we take?* *No. It gives us the facts to make that decision.* Then the business line: *we're not deciding whether to use AI; we're deciding how much authority we're comfortable giving it.*
8. **Different people, same evidence.** Operations: what am I actually working with? Platform: where are real controls missing? Risk: which decisions need an accountable owner? Leadership: how do we scale this responsibly? An insurer could ask what evidence exists, and nobody on screen issues a verdict, a score or an insurance decision.
9. **The ending.** The company does not stop the agent. The agent keeps working, operations is calmer, security understands the deployment, leadership can decide about scale. *I thought putting boundaries around AI would slow us down.* *Humans have an interesting relationship with brakes. You think brakes make a car slower. They're what let you drive faster.* The brakes are the organisation's own controls, not RiskMandate.
10. **The hook.** *The board approved the next phase. Fifty new agents. Finance, HR and Engineering. Monday.* Everyone freezes. *Would you like the short answer this time?* Cut to black.

## 3. The review: seven questions, and the lead's answers of 3 October

| the outline asked | the lead | what the site adds |
|---|---|---|
| 1. Is reach, mandate, gap, barriers faithful to RiskMandate? | yes, accurate | The four parts as the home page states them: reach measured, mandate elicited, gap derived, barriers recorded. The files keep the older names, GRANT and DELTA. |
| 2. Is the way an ABP is described correct? | yes | One agent, one deployment, four parts, no score. *The ABP* or *the behaviour policy*, never *the policy* alone, because on this site *policy* is also the insurance instrument. |
| 3. Any capabilities implied that RiskMandate does not have? | no | The film already avoids the three the site refuses: it does not stop the agent, it does not score, it is not an insurer. Keep it that way through animation, where a glowing shield is the easy mistake. |
| 4. Should the Licence to Operate be in this film? | leave it for another video; there is already a lot here | The second film: the organisation as authority, the ABP as the instrument, the agent as licensee, with an owner, a term and a review. The template is on the site. |
| 5. Are the cast and roles right? | they are fine; change anything you like; make Maya a little older | The storyboard's prompt carries the ask. The cast file stays as drawn until the studio redraws it. |
| 6. Any terminology to change before the dialogue is locked? | all good | British spelling in every bubble. *Grant* and *reach* are the same thing; the film may use either, and the site uses both. |
| 7. Comfortable with the central message, RiskMandate shows the authority and reach of agents without being the enforcement layer? | yes, 100 per cent; we are not designed to be inline; a simple example is an ABP that is given to Claude to enforce | This is the line to protect in every cut. The ABP is a document; what enforces is the deployment's own controls, or an agent handed the ABP as its terms. The team page says the same of our own agents. |

## 4. The value proposition, as the story states it

The film says in dialogue what the site says in sections, and the order is the argument:

- **The agent is good at the job.** That is why the question matters; a useless agent needs no behaviour policy.
- **The grant is not the mandate.** *I didn't ask you to use all of that. Correct. But I can reach it.* Every story in the family is this line told differently.
- **The question is not what we told it, it is what stops it.** A barrier is a real control; a rule in a prompt is an expectation.
- **Facts, not verdicts.** RiskMandate gives people the picture; the people decide how much authority to give. Nothing is scored.
- **One record, read for four reasons.** Operations, platform, risk and leadership look at the same four parts and each find their own question answered.
- **Brakes let you drive faster.** The company scales the agent because it can now see it. That is the Insurability Index's direction without the Index being on screen.

## 5. What the film must not show, in the site's rules

No score, rating or traffic light on the behaviour policy, including in a background graphic. No verdict on a named product; the systems on screen are generic, and nobody's vendor is drawn. RiskMandate never in the request path: no shield, no gate that the agent bounces off, no *blocked by RiskMandate*. No insurer on screen deciding anything; an insurer may ask what evidence exists. No *certified* or *compliant*. The footer line on every scene says the scenario is illustrative. British spelling in the bubbles. And never *the policy* on its own.

## 6. Toward an article

Working title: *Would you like the short answer?* The article is the film's arc as prose, with the ten beats as its sections and the dialogue as pull quotes, ending on the hook. It would sit in the Reading group beside *Somebody will ask what your agent can do*, link the storyboard and the cast, and carry the same *Where this connects* grid every article ends with. It can be written now from the storyboard; it reads better once there is a frame or two from the film to show.

## 7. What needs the lead

1. The wrong-but-valid action in scene 6, if the placeholder (refunds settled rather than prepared) is not the one the film uses; the storyboard follows the film.
2. Whether the filmmaker is named on the story page when the film ships, and how.
3. The article, when: now from the storyboard, or after the first frames exist.

## 8. What this does not do

It does not put the film on the site; there is no film yet. It does not change the cast file; Maya's age is a note in the prompt until the studio redraws the sheet. It does not go through the stories vault; the film is being made outside the studio workflow, and the storyboard was written straight to the site from the lead's instruction. It does not register the outline as a document that arrived from outside, because it arrived in a private conversation and only the story is published.