Roll out one LLM feature in a legacy system, stage by stage

Video transcript

1. 0:00–0:06

   CRM summary • Inventory before building • Data owner • Off switch • System of record • LLM feature • Reads • Proposes

   The one-record figure appears: System of record feeds the LLM feature along a solid Reads arrow, and a dashed Proposes arrow returns toward the record and stops before it. A marker carries data along Reads into the feature; a second marker runs back along Proposes and halts at its head, short of the record. Two tags, Data owner and Off switch, travel in and are tied to the record stack with cyan strings.

2. 0:06–0:12

   CRM summary • Pilot it read-only • Named reviewers • Record unchanged • LLM feature • Reads • Proposes • System of record

   A panel headed Named reviewers, with three faceless reviewers and an empty slot, slides in. One blank summary card rises from the LLM feature box and settles in the slot, and the reviewers' blank name bars draw in. The record stack does not move: its label fades and Record unchanged takes its place. Reads and Proposes stay as they were.

3. 0:12–0:18

   CRM summary • Run it in shadow • Outputs to a log • Own budget and cap • Shadow call • Side effects off • Protected log • Permitted data

   The shadow-controls figure appears: Permitted data enters through a screened inlet and a glass run into the Shadow call; one open drop leads down into the Protected log, and a second outlet ends in a sealed cap labelled Side effects off. Two cyan request pulses run from the inlet into the shadow call, vanish inside it and reappear in the drop, sinking into the log; the capped outlet carries nothing. Outputs to a log appears by the log, and an Own budget and cap tag is tied to the shadow call.

4. 0:18–0:24

   CRM summary • Widen by cohort • Internal team first • Route back if needed • Old path

   The routing band appears: an incoming track meets a switch whose blade is set for the thick track to the Old path block, and a thin branch rises to a small block. A request rides the old path. The blade swings toward the branch while its old position stays as a dim ghost; the branch lights up and a second request rides it to the small block, labelled Internal team first. A dashed outline marks that ghost: Route back if needed. Nothing is flipped back.

5. 0:24–0:30

   CRM summary • Write back last • One write type at a time • Recovery plan first • System of record

   The record stack returns with its System of record label, and a small routing switch appears to one side. A sheet headed Recovery plan first slides in beside the stack and its blank rows draw. A card reading One write type at a time moves toward the stack and stops beside the sheet; nothing is written. The routing switch dims: switching the route back cannot undo a completed write.