- 0:00–0:06
Customer chats • Classify the data first • Before any model call • May hold personal data
Customer chats, an illustrative use case, is a badge fixed in its own lane in every scene. Under the title, Before any model call. A blank conversation card slides in and two empty speech bubbles appear on it. A tag reading May hold personal data travels onto the card. Only then does a dashed, pending arrow appear and a blank model block arrive at its end: nothing has been sent to a model.
- 0:06–0:12
Customer chats • Decide who controls versions • Retirement dates • Provider's API • Provider sets versions • Your servers • You pin the version
Customer chats stays fixed. The article's version figure enters: Provider's API feeds a conveyor of blank version tags under Provider sets versions; below, Your servers lead to one blank tag held by a pin, You pin the version. The conveyor advances one slot: a new blank tag enters from the start of the belt, the others move on, and the last tag slides into the conveyor's head and fades beside Retirement dates. The pinned tag does not move.
- 0:12–0:18
Customer chats • Get four answers in writing • Processing region • Retention • Training use • Sub-processors
Customer chats stays fixed. A blank written-answers sheet appears. Four question cards, Processing region, Retention, Training use and Sub-processors, slide onto it one after another, each beside its own answer slot. Every slot stays empty, its dashed edge still waiting.
- 0:18–0:24
Customer chats • Route by data class • Serving model logged • Sensitive request • Self-hosted model • Fallback blocked • Hosted model
Customer chats stays fixed. The article's routing figure enters: Sensitive request, a card with a lock; Self-hosted model; a barrier marked Fallback blocked; a plain request; and Hosted model. A marker runs the solid route from the sensitive request to the self-hosted model, and Serving model logged is written beside it. A second marker follows the dashed fallback route and stops before the barrier; nothing passes it. The plain request keeps its own solid route to the hosted model.
- 0:24–0:30
Customer chats • Write the decision on one page • Owner and on-call • Cost at doubled volume • Exit trigger
Customer chats stays fixed. A one-page decision sheet slides in. Three rows draw in one after another, Owner and on-call, Cost at doubled volume and Exit trigger, each with an empty dashed field. Nothing is filled in and no route is chosen: the page is still a draft.
An illustrative customer-chat use case is classified first, weighs who controls model versions, collects four written answers from a hosted provider, is routed by data class and ends on a one-page decision draft. No route is chosen.
Read the article: Open-Weight or Hosted? Choosing How to Run an Arabic LLM