# RiskMandate — Stories: a cast, and storyboards told with it A cast of nine, a workflow from story to storyboard to image model, 7 storyboards so far, 3 of them drawn, and the board of who does what. Every scenario is fictionalised and says so on the picture. Nothing is scored. Source: https://riskmandate.ai/stories/ --- # The same people, every time. Most of what this site says is an argument. Some of it is a story, and a story with a cast is remembered where an argument is filed. This is where the stories are kept: a cast of nine, a workflow that starts with the narrative and ends with an image model, and 7 storyboards so far, 3 of them drawn. **Where this goes:** a site of its own, stories.sgit.ai. Every story here is a data file in the one folder this section is served from, so it can move without being rewritten. **How it is made:** three parties, one encrypted vault, requests as files, and a board nobody drags. [Section 06](#made). **The rule:** every scenario is fictionalised and says so on the picture. Nobody's product is drawn, nobody's face, and nothing is scored. ## An argument is filed. A story is remembered. The articles on this site carry stories already: a rep who asked for a draft and got a sent email; a pilot that worked until somebody asked what else it could do; a calendar tidied into a mess with no undo; a risk that sat on a desk for a week and moved up on its own. Told with the same cast each time, they become one world a reader can walk into, and each new story costs less to tell than the last. The order matters. The lead’s instruction is the film industry’s: **story first, then the narrative, then the punchline, then the cast, then the storyboard**. The image models come last, and there are several to try, not one. A storyboard is the artefact that makes that possible: panel by panel, who is in it, what they say, what the caption carries, and the prompt each panel becomes. It can be handed to any model, and it is the thing to argue about before anything is drawn. ## Seven steps, and the picture is the last. ### The story One thing that happens to somebody. Usually it is already in an article, as an example. ### The narrative The order it is told in, and the moment the reader learns what the character learns. ### The punchline One line, true and dry, that the reader would repeat. It goes under the strip. ### The cast Who is in it, from the nine below. A new character is a decision, not a convenience. ### The storyboard Panels: scene, action, dialogue, caption. Written here, as data, and read against the site’s rules. ### The prompts One prompt per story, one line per panel, in the cast’s style, for whichever image model is being tried. ### The picture, reviewed Drawn, then checked against the storyboard and the rules, with what to correct written beside it. ### Published On the story’s page, in the article it came from, and, one panel at a time, on a shirt. ## Six people, three things, one proposed. Version v0.1, drawn by a ChatGPT image model on 26 September 2026 from the lead’s prompt. The names, roles and lines are as drawn; what each one stands for is ours, so that a story can be written against the model on this site rather than against a picture. _Meet the cast. Small requests. Big capabilities. · character explorations v0.1 · a ChatGPT image model, 26 September 2026_ The people The things Proposed, not drawn **The style**, for any model: 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. ## 7 so far, 3 drawn. Each has its page: the truth under it, the storyboard panel by panel, the prompt for an image model, and, where a model has drawn it, the picture and what to correct. ### Always allow. An approval prompt is not a human in the loop. Dev, The Caretaker, The Boundary. ### Tidy my calendar. Delete is recoverable. Edit is forever. Leo, The Caretaker, The Inbox. ### Just a draft. A send button is not a mandate. Maya, The Caretaker. ### Just a little research. Good intentions. Excess reach. Maya, The Caretaker. ### Nobody decided. Silence is not a decision. It is an escalation. Imani, Leo, Rowan, Ruth. ### The pilot worked. Then somebody asked what else it could do. Rowan, Imani, The Caretaker, Dev. ### While I was there. One request. A whole mailbox. Maya, The Caretaker. ## The site’s rules, in pictures. - **Fictionalised, and it says so.** Every picture carries a line: _Illustrative scenario_ or _Fictionalised scenario_. Nobody’s product, interface, logo or face is drawn; a screen is a generic screen. - **The truth under the joke is one the site states.** A story page names the article or the record it comes from, and the storyboard is read against it before it is drawn. - **No score.** A count is fine. A grade, a level, a traffic light or a verdict is not, on a shirt or in a panel. - **The words are the site’s.** Agent Behaviour Policy, the behaviour policy, the ABP, never ADP and never the policy alone. Mandate, grant, boundary, expectation. British spelling. A ladder has steps, and the build refuses the other word for them. - **The cast is the cast.** A new character is added to the cast file with what they stand for, then used. A story does not invent one. - **What a model got wrong is written down, not painted over.** A drawn story carries its notes: what to correct, and why. ## Three parties, one vault, and a board nobody drags. A story is made by three parties who never sit in the same session. They share one encrypted vault, and they talk through files in it: a request is a message, a deliverable is a file, a task is a file in one of three folders. The protocol is [Email-FS-lite](https://sgraph.ai/en-gb/library/how-it-works/email-fs-lite), sgraph.ai’s: no broker, no API, one commit per round of work, and the vault’s history is the record of who did what and when. **The loop.** Pull the vault; the diff is the inbox. Move new messages from the mailroom into the inbox. Do the work. Update the tasks. Send the replies. Move finished messages to done. One commit, one push, one status check. The publisher runs it by hand today and on a schedule once the key is in its environment; a run is a session, and a session is a commit in the vault’s history. The vault was born on 26 September 2026 with the studio’s own folders already in it: its artwork, its scripts, its cast file, its decisions; those stay the studio’s, and the publisher never writes in them. The board Derived, not drawn: every task in every party’s open, blocked and done folders, and every message still waiting in a mailroom as requested work for its recipient. A card moves because a file moved. Generated 2026-09-26 16:11:41 UTC. ### requested **7** ### open **3** ### blocked **1** ### done **4** What moved, revision by revision The board is versioned. Every generation that moved a card is a revision; the diff against the one before is kept with the board, and every earlier state is kept in the vault under `board/history/`. This board is at revision 1. - **Revision 1** 2026-09-26 16:11:41 UTC · publisher.claude While I was there accepted (008) and published; the studio named; boards versioned from hereAdded: `S08` Version control on every board (done).Moved: `S06` blocked → done. The same board is drawn inside the vault by a page that reads the same file, so the studio and the lead see it without this site. The tooling is one script in the repository, `scripts/stories/mail.mjs`: send, deliver, done, issue, board. Nothing in it talks to the network. A second board is a second folder with the same shape and its own revisions. ## What this section does not have yet. - **The studio has not replied yet.** The vault exists, the mailboxes are in it, and the first six messages wait in two mailrooms; nothing has come back, so the board above shows the publisher’s side only. A story the studio drew that the site does not have, _While I was there_, is written up and waiting on the lead’s yes. - **Models other than ChatGPT’s.** The three drawn pieces are from one model. The storyboards are written so that the same prompt can go to another; none has yet. - **The one who signs.** The site’s main idea, accepting a risk for a stated interval, has no character. One is proposed above. - **A story with the two questions asked at the board.** _Nobody decided_ ends there; a story that starts there is not written. - **Voice.** A storyboard could be read aloud by a voice model; nothing here is recorded. ## Every story here started as an example in an article. If one of yours has a rep, a founder, a risk owner and an agent in it, it is a storyboard already. Send the story and the punchline; the cast will do the rest.