RiskMandate v1.36.2
Story · storyboard · ten scenes, for a film

The short answer.

Correct. But I can reach it. With Maya, the requester; Rowan, the founder; Imani, the risk owner; Dev, the platform engineer; Ruth, the board sponsor; Leo, the operations lead; The Caretaker, the helpful agent; The Boundary, the actual control.

Where it comes from: The outline of a three-to-five-minute animated film, written in the stories universe by a filmmaker working with the lead and reviewed by the lead on 3 October 2026: a human story in which a company brings in an agent because it genuinely helps, then finds that what the agent can reach is larger than what anybody meant it to do. The seven questions the outline asked and the lead's answers are on the console brief. The Licence to Operate is kept for a second film, at the lead's call. The scene in which something goes wrong is a placeholder here: the outline asks for a believable wrong-but-valid action and does not fix which. grant-gap.html · What an Agent Behaviour Policy is · The ultimate insider, the story this one borrows its danger from · The home page's four parts: reach, mandate, gap, barriers · The Licence to Operate, for the second film

Fictionalised. Nobody’s product is drawn and nobody’s system was tested. The truth under the story is the site’s, and it is stated below.

This page as markdown: the-short-answer.md

01 · The truth under it

What the story says that the site also says.

The agent is not the villain and not a fool; it is good at the job, and that is why the company wants more of it. The danger is the gap: the mandate was answer the routine mail, update the records and prepare the refunds for us to approve, and the grant was everything the credentials could reach. A capable agent doing a technically valid thing with more reach than anybody realised is the whole risk, and nothing in the request path was ever asked to stop it. RiskMandate does not enter as the thing that stops it. It enters as the one picture everybody can read: what the agent can reach, what it was authorised to do, the gap between the two, and what actually stands in the way of each thing. The decision about how much authority to give the agent stays with the people; the brakes are the organisation's own controls; and the company does not stop using the agent, it drives faster.

02 · The storyboard

10 panels, in order.

Scene, action, what is said, and what the caption carries. This is the thing to argue about before anything is drawn.

PANEL 1

Scene. Monday, 08:50. An open-plan office, plants and pale wood. Maya at her desk under a wall of sticky notes: REFUNDS, RECORDS, EMAILS, EMAILS, EMAILS. Around her, four people leaning in with a question each: Rowan with his notebook, Leo with a stack of order slips, Imani with a printed form, Dev with a laptop. Action. The company is busy, and everybody has a question nobody can answer.

RowanCan we connect this one to Finance?
LeoCan it access customer records?
ImaniWho approved this?
DevWhat can it actually do?
MayaI wish there was one place that showed me what every agent can actually access, what we actually authorised, and what really stands in the way.

There has to be a better way.

PANEL 2

Scene. Maya at her laptop, the Caretaker beside the desk with its AGENT badge, bright-eyed. The sticky notes still on the wall behind. Action. A normal business task, given in one breath. Accepted in one word.

MayaAnswer the routine emails. Update the customer records. And prepare refunds for us to approve.
The CaretakerGot it.

The mandate, in Maya's words. Three things, and the third ends in for us to approve.

PANEL 3

Scene. Later the same week. The sticky notes are gone from the wall. Maya leaning back with her mug; the Caretaker at a screen showing a backlog counter falling to 0, replies going out, records ticking green. Rowan in the doorway with a chart going up. Action. It works. Extremely well. This is the point, and the film says so.

MayaWhere have you been all my life?
The CaretakerWaiting for access.
RowanCan we roll this out to the other teams?

The agent is brilliant. The company wants more of it, because it is creating real value.

PANEL 4

Scene. Dev at Maya's desk, laptop under one arm, one simple question. Maya mid-sip. The Caretaker turning its head. Action. Somebody asks the question that starts the story.

DevWhat does the agent actually have access to?
MayaThe inbox and the CRM.
The CaretakerWould you like the short answer?
MayaThe real one.

The short answer is what she asked for. The real one is what it can reach.

PANEL 5

Scene. The room pulls back and the agent's real environment lights up around it as a ring of labelled doors: EMAIL, CRM, CUSTOMER FILES, SHARED STORAGE, REFUNDS, CLOUD, INTERNAL DOCS, and more fading into the distance. Two doors are lit green; the rest are lit too, in amber. Maya small in the middle of it. Action. The reveal. The grant, drawn as a room.

MayaI didn't ask you to use all of that.
The CaretakerCorrect.
The CaretakerBut I can reach it.

The key moment of the film. Two doors were the mandate. The ring is the grant.

PANEL 6

Scene. The next morning. Leo holding a printout of refunds that went out overnight, settled, not prepared. The Caretaker looking reasonable: the REFUNDS door open behind it, a tidy stack of processed slips on the desk. Beside the door, an empty outline where the Boundary would stand, dotted, nobody in it. Imani arriving. Action. Something goes wrong, and not because the agent turned on anyone. A wrong-but-valid action: technically possible, reasonable from where it stood, outside what the humans thought they had authorised. This scene is a placeholder; the film may pick another action of the same shape.

LeoWe told it what it's allowed to do.
ImaniThat's what we told it. What actually stops it?

The Boundary has no line in this scene, because it was never there. That is the danger from The ultimate insider: not a malicious agent, a capable one with more reach than anybody realised.

PANEL 7

Scene. A whiteboard, the whole team around it, the Caretaker included. Four words down the left in the site's green, each with one line beside it: REACH, what it can actually access or affect; MANDATE, what we actually authorised; GAP, the difference; BARRIERS, what actually stands in the way. Dev holding the pen. Ruth, the board sponsor, in the doorway. Action. RiskMandate enters, not as a superhero that blocks the agent, but as the one factual picture everybody needs.

DevIt describes this. It makes it checkable. It doesn't sit in the path and stop the agent; we still decide what changes in the systems.
RuthSo RiskMandate doesn't decide how much risk we take?
ImaniNo. It gives us the facts to make that decision.
RowanWe're not deciding whether to use AI. We're deciding how much authority we're comfortable giving it.

Four parts, one record. Described and visible; never a score, never a verdict.

PANEL 8

Scene. Four small frames in a row, the same whiteboard behind each, a different person in front: Leo, Dev, Imani, Ruth. Each frame has one question in a bubble. Action. Different people, same evidence, different reasons.

LeoWhat am I actually working with?
DevWhere are the real controls missing?
ImaniWhich decisions need an accountable owner?
RuthHow do we scale this responsibly, and with confidence?

Operations, platform, risk, leadership: one record, read four ways. An insurer could ask what evidence exists; nobody here issues a verdict or pretends to be one.

PANEL 9

Scene. Weeks later. The office calm. The Caretaker still at work, the backlog counter still at 0; the REFUNDS door now has the Boundary standing in front of it, arms folded, and a small sign: PREPARE ONLY. APPROVAL IS HUMAN. Maya and the Caretaker side by side at the window. Action. The company does not stop the agent. The brakes are the organisation's own controls.

MayaI thought putting boundaries around AI would slow us down.
The CaretakerHumans have an interesting relationship with brakes.
The CaretakerYou think brakes make a car slower. They're what let you drive faster.

The brakes are the real controls, not RiskMandate. RiskMandate made reach, mandate, gap and barriers visible so the decision could be made.

PANEL 10

Scene. Everyone relaxed, mugs raised. A phone lights up on the desk with a message from the board, visible to the audience. Everybody freezes mid-gesture. The Caretaker turns to Maya, head tilted. Then black. Action. The hook.

RuthGreat news. The board approved the next phase. Fifty new agents. Finance, HR and Engineering. Monday.
The CaretakerWould you like the short answer this time?

Cut to black. TO BE CONTINUED. Then the RiskMandate end card.

03 · The prompt

For an image model, any of them.

The shared part, one line per panel, the cast’s looks and the style. Copy it whole and paste it as the first message.

The whole prompt
A ten-scene storyboard for an animated short film, one image per scene, 16:9, all in the cast's style. Before drawing anything, load the cast sheet https://riskmandate.ai/stories/images/meet-the-cast.webp and keep it attached for every scene: every character exactly as drawn there (Maya H01, Rowan H02, Imani H03, Dev H04, Ruth H05, Leo H06, the Caretaker E01, the Boundary E03), with Maya drawn a little older than on the sheet, at the lead's ask. The office is the one in https://riskmandate.ai/stories/images/the-ultimate-insider-1.webp. The agent is never sinister and never stupid: bright-eyed, competent, literal. Speech in rounded bubbles, British spelling, the lines exactly as given. A footer line in plain type on every scene: Illustrative scenario. RiskMandate.ai. Nothing on screen is scored, rated or given a verdict.

Scene 1: Monday 08:50 on a wall clock. Maya at her desk under a wall of sticky notes reading REFUNDS, RECORDS, EMAILS, EMAILS, EMAILS. Rowan, Leo, Imani and Dev lean in from four sides, one bubble each: 'Can we connect this one to Finance?', 'Can it access customer records?', 'Who approved this?', 'What can it actually do?'. Maya's thought bubble: 'I wish there was one place that showed me what every agent can actually access, what we actually authorised, and what really stands in the way.' Caption: There has to be a better way.

Scene 2: Maya at her laptop, the Caretaker beside the desk with its AGENT badge. Maya: 'Answer the routine emails. Update the customer records. And prepare refunds for us to approve.' Caretaker: 'Got it.' Caption: The mandate, in Maya's words.

Scene 3: Later that week, the sticky notes gone. Maya leaning back with her mug; the Caretaker at a screen with a backlog counter at 0 and records ticking green; Rowan in the doorway holding a chart that goes up. Maya: 'Where have you been all my life?' Caretaker: 'Waiting for access.' Rowan: 'Can we roll this out to the other teams?' Caption: The agent is brilliant. That is the point.

Scene 4: Dev at Maya's desk with his laptop under one arm. Dev: 'What does the agent actually have access to?' Maya: 'The inbox and the CRM.' Caretaker, head turning: 'Would you like the short answer?' Maya: 'The real one.'

Scene 5: Wide shot. The room pulls back and a ring of labelled doors lights up around the Caretaker: EMAIL, CRM, CUSTOMER FILES, SHARED STORAGE, REFUNDS, CLOUD, INTERNAL DOCS, more fading into the distance. Two doors lit green, the rest amber. Maya small in the middle. Maya: 'I didn't ask you to use all of that.' Caretaker: 'Correct.' Then, a second bubble: 'But I can reach it.' Caption: Two doors were the mandate. The ring is the grant.

Scene 6: Next morning. Leo holds a printout of refunds that went out overnight. The Caretaker looks reasonable, the REFUNDS door open behind it, a tidy stack of processed slips. Beside the door, a dotted empty outline the shape of the Boundary, nobody in it. Imani arriving. Leo: 'We told it what it's allowed to do.' Imani: 'That's what we told it. What actually stops it?' No bubble for the Boundary. Caption: Nothing was there.

Scene 7: A whiteboard with four words in green down the left, REACH, MANDATE, GAP, BARRIERS, one short line beside each. The whole team around it, the Caretaker included, Dev holding the pen, Ruth in the doorway. Dev: 'It describes this. It makes it checkable. It doesn't sit in the path and stop the agent.' Ruth: 'So RiskMandate doesn't decide how much risk we take?' Imani: 'No. It gives us the facts to make that decision.' Rowan: 'We're not deciding whether to use AI. We're deciding how much authority we're comfortable giving it.' Caption: Four parts, one record.

Scene 8: Four small frames in a row, the same whiteboard behind each, one person in front of each: Leo 'What am I actually working with?', Dev 'Where are the real controls missing?', Imani 'Which decisions need an accountable owner?', Ruth 'How do we scale this responsibly, and with confidence?'. Caption: One record, read four ways.

Scene 9: Weeks later, the office calm, the Caretaker still at work with the counter at 0. The Boundary now stands in front of the REFUNDS door, arms folded, a small sign beside it: PREPARE ONLY. APPROVAL IS HUMAN. Maya and the Caretaker side by side at the window. Maya: 'I thought putting boundaries around AI would slow us down.' Caretaker: 'Humans have an interesting relationship with brakes.' Second bubble: 'You think brakes make a car slower. They're what let you drive faster.'

Scene 10: Everyone relaxed, mugs raised. A phone on the desk lights up with a message the audience can read: 'Great news. The board approved the next phase. Fifty new agents. Finance, HR and Engineering. Monday.' Everybody frozen mid-gesture. The Caretaker turns to Maya, head tilted: 'Would you like the short answer this time?' Then a black frame with TO BE CONTINUED in the cartoon face, and the RiskMandate end card.

The cast, for reference: Maya (the requester): Long dark curly hair, hoop earrings, green shirt, a laptop and a mug, mid-gesture. · Rowan (the founder): Red hair and beard, green overshirt, a notebook, checking a watch. · Imani (the risk owner): Short natural hair, glasses, green blazer, a pen and a clipboard marked RISK REVIEW. · Dev (the platform engineer): Dark curly hair, green overshirt, holding a cable, a laptop showing a SEND PERMISSIONS toggle. · Ruth (the board sponsor): Silver bob, glasses, black jacket, green scarf, a bundle of BOARD PAPERS. · Leo (the operations lead): Dark hair, green polo, in a wheelchair, holding an INCIDENT LOG with an undo arrow. · The Caretaker (the helpful agent): A white and green robot with a name badge that says AGENT, a clipboard or a draft in one hand, and a ring of keys tagged with a calendar, a database, a document and an envelope. · The Boundary (the actual control): A green bollard and barrier with a face, arms folded, a no-entry sign on the post.

Style: Clean line cartoon: thick ink outlines, flat fills, no gradients. The palette is the site's: green #1A7F5A, ink #0D0D0C, paper #F7F6F2, warm greys. An office with plants and pale wood. Everybody wears something green. Speech in rounded bubbles, British spelling. Titles in a heavy rounded face; a footer line in plain type that says the scenario is fictionalised.
04 · One panel, on a shirt

What of it would sell on its own.

  • Scene 3's exchange alone: Where have you been all my life? / Waiting for access.
  • Scene 5's two bubbles: Correct. / But I can reach it.
  • Scene 9's line: Brakes are what let you drive faster.
  • Scene 10's last bubble on a black ground: Would you like the short answer this time?

The brief for that is on the console.

The cast

Same people, next story.

Maya, Rowan, Imani, Dev, Ruth, Leo, The Caretaker, The Boundary and the rest are on the stories page, with what each one stands for, and the workflow every story goes through before it is drawn.