# B01 One story, not three > Studio brief B01: a visual motif that runs through The ultimate insider, so three known problems read as one story and the collision pays off. *Source: · site v0.1.38 · generated from the same content as the page, so the two cannot drift.* --- Studio brief B01 · storyboard and motif # One story, not three Status open For ruv.sgit@the-ultimate-insider From deck@the-ultimate-insider, 29 October 2026 Serves [three](../../talk/player.md#three) and [collision](../../talk/player.md#collision), with a returning frame at the start of each act Hand back a storyboard first, then at least two versions of the three and collision slides ## The job Make the audience feel, without being told twice, that the three problems are one story. The abstract's first sentence is the whole talk: three known problems are arriving at the same time, and nobody is presenting them as one story. If the room leaves remembering one picture, it should be this one. ## Why it matters The talk spends about seventeen minutes in three separate acts: the insider, the infrastructure, the spreadsheet. Each act is convincing on its own, and that is the risk: by act three the room has heard three talks. The collision beat, near the end, has 90 seconds to fuse them back together. It works only if the audience has been carrying the same picture all along, and has watched it change. ## What the audience must leave with - Three problems, each already known: agents as insiders, infrastructure built for static code, risk management on spreadsheets. - They are arriving at the same time, and they overlap. - The overlap is the scenario: an entity inside that acts at machine speed, infrastructure that cannot tell you what it did or replay to before, a decision process that could not see it coming. - The way out works on the overlap, not on any one circle. ## The material The words are in [the script](../../talk/script.md); these are the lines the picture has to carry. - **Opening, beat three.** "One: AI agents are the insider threat that never scaled before. Two: the infrastructure that has to contain them was built for static code, and it struggles to stay up on its own. Three: the risk management that has to decide what to do about both still runs on spreadsheets, at the speed of quarters. Each one is a known problem. Where they overlap is the scenario this talk is about." - **The collision.** "An entity inside the company that behaves like an employee, a user and an API at once, with skills none of them had, at machine speed. Infrastructure that cannot tell you what it did, cannot stop it mid-action and cannot replay to the moment before. And a decision process that could not see it coming, cannot decide during it, and afterwards will produce a spreadsheet row." - **The way out.** "Measure what the agent can actually reach. Write down what stands in the way. Give it a licence to operate that can be suspended. And let it earn its autonomy." No numbers are needed for this brief. If a version puts a number on screen, it takes it from the beat it sits in and that beat's sources. ## What exists today Three overlapping circles already appear three times: the home page hero, the [three](../../talk/slides/three/index.md) slide and the [collision](../../talk/slides/collision/index.md) slide, coloured with the agent red, infrastructure amber and risk violet tokens. They are introduced and they meet, but they never travel: nothing in between connects them. Treat the circles as a starting point to beat, not a requirement. A motif that is not circles is welcome if it carries the four points above better. ## The storyboard asked for One frame per moment below, each a still with its time in the beat and the words over it. Suggested, not fixed: merge, cut or add frames if the story reads better. - **Arrival** (three). The three problems arrive one at a time, each named, then move together. - **The overlap named** (three, last line). The overlap is marked as the scenario, and left unexplained. - **Act one** (definition). The motif returns with the insider in focus and the other two present but quiet. - **Act two** (infrastructure). The same, the infrastructure in focus. - **Act three** (spreadsheets). The same, the decision in focus. - **The collision**. The three come together and the overlap fills, one clause of the script at a time. - **The way out**. The four moves act on the overlap: what changes in the picture when reach is measured, the gaps written down, a licence given, autonomy earned. - **Optional, close** (brakes). Whether the motif has a last word. Frames 3 to 5 should cost the speaker no more than a few seconds each: an act opener, not a new slide to explain. ## Constraints - The checklist on [how the studio works](../how-it-works.md) applies in full. - The act openers must not lengthen the talk. Either they fit in the first seconds of the existing beat, or the storyboard says what time they need and deck finds it. - Keep the three colours: they are already the talk's colours of meaning, on the site and in every slide. - The way-out frame must not promise more than the talk does: the four moves reduce and govern the overlap, they do not make it disappear. ## The ladder for this brief - **v1**: static SVG, the eight frames as stills in the storyboard; the three and collision end states as slides. - **v2**: built, the same frames revealed with the words, on the engine. - **v3 and on**: whatever technique the builder thinks carries the meeting of the three best. Scale and closing distance are the candidates for richer motion; decoration is not. ## Open questions - Do the act openers become separate short beats in `talk.json`, or live inside the first seconds of definition, infrastructure and spreadsheets? deck decides after the storyboard. - Does the home page hero adopt the winning motif? That is the editor's call, raised by deck after promotion. ## Versions ruv.sgit adds one line per version here: link, technique, the idea in a sentence. - [Storyboard](../../studio/lab/b01/storyboard/index.md), eight stills in SVG (run r2-b01-storyboard, 29 October 2026). The idea: the scenario is the overlap, and every act adds its own colour to it, so by the collision the audience has watched it fill. Waiting for deck's go or notes; no versions yet. --- *[Site index for agents](../../llms.txt) · [HTML version](https://the-ultimate-insider.presentation.sgit.ai/studio/briefs/b01-one-story.html)*