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 6 storyboards so far, 2 of them drawn.
Where this goes: a site of its own, stories.sgit.ai. Every story here is a data file, so it can move without being rewritten.
The rule: every scenario is fictionalised and says so on the picture. Nobody's product is drawn, nobody's face, and nothing is scored.
01 · Why stories
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.
02 · The workflow
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.
03 · The cast
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
WhoTheir lineStands forLooks like
MayaH01 · The requester“I only asked for a draft.”The person who connects an agent to get one small thing done, and finds it can do more than they asked. The rep in the role-ownership article; the one whose mandate is read and draft.Long dark curly hair, hoop earrings, green shirt, a laptop and a mug, mid-gesture.
RowanH02 · The founder“Can we ship it today?”Speed. The person who says yes to the pilot and is surprised when it is switched off. The founder of the pilots article.Red hair and beard, green overshirt, a notebook, checking a watch.
ImaniH03 · The risk owner“Who authorised that?”The person the map routes a risk to, and who has to say what was authorised. Holds risks, places them, asks for the mandate.Short natural hair, glasses, green blazer, a pen and a clipboard marked RISK REVIEW.
DevH04 · The platform engineer“The scope includes send.”The person who reads the consent screen and the scope, and can put a boundary in place. Says what the grant is, in the grant's words. A character called Dev in stories about developers will confuse readers; a rename is a decision for the lead.Dark curly hair, green overshirt, holding a cable, a laptop showing a SEND PERMISSIONS toggle.
RuthH05 · The board sponsor“Who owns the risk?”The board: where every path ends, and who asks the two questions of any register.Silver bob, glasses, black jacket, green scarf, a bundle of BOARD PAPERS.
LeoH06 · The operations lead“Can we undo it?”The person who runs the day on the shared calendar and the shared systems, and who finds out that an edit has no way back.Dark hair, green polo, in a wheelchair, holding an INCIDENT LOG with an undo arrow.
The things
WhatIts lineStands forLooks like
The CaretakerE01 · The helpful agent“I saved you a click.”The agent: the grant on legs. It means well, it holds a ring of keys it was given, and it does not know which of them it was meant to use.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 InboxE02 · The long-suffering witness“Please stop helping.”The system the agent acts on, which sees everything and can stop nothing.A green in-tray full of envelopes, with a face, a mug beside it.
The BoundaryE03 · The actual control“That action is blocked.”The one barrier that is a control: enforced by something the agent cannot reach. A gate arm, not a sign.A green bollard and barrier with a face, arms folded, a no-entry sign on the post.
Proposed, not drawn
WhoTheir lineWhy
to be namedH07 · The one who signs“Accepted, for a month. Then it comes back to me.”The site's main idea, accepting a risk for a stated interval, has nobody in the cast to do it. A person with a pen and a date. Alternatively Imani takes the line.
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.
04 · The stories
6 so far, 2 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.
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.
What is not done
What this section does not have yet.
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.
Tell one
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.