Built because: "Whenever a user interacts with Fin, our system needs to make a real-time, three-way decision:"
The idea, in three working flows
Three tap-through flows show the handover from its three seats: the customer who asks, the colleague who inherits, and the supervisor who corrects. Each runs on the designed content of the two replay pages, compressed to its turning points.
These are designed prototypes, written for this concept. The conversations are fictional, Kettle is a fictional company, and nothing on this page calls a model.
Opened from the file system: the browser refuses module scripts here, so the flows cannot run. Serve the site folder over HTTP and reload.
Priya’s export question is settled by Fin; her contract question is not, and the seam is where the briefing earns its keep.
Four steps in the screen, from the settled fix to the handover that repeats nothing.
The same moment from Marta’s side of the glass, where the five fields land before the conversation does.
Four steps from queue to sent reply, with the briefing doing the work of the scroll.
Nadia’s rate card, the confident wrong answer, and the correction that becomes a rule with its cost attached.
Four steps from wrong answer to written rule, the cost stated rather than hidden.
d-049 · A seventh page shows the idea as three tap-through flows
- Decision
- Three tap-through flows on a seventh page, notes beside the glass.
- Because
- The replay pages argue at depth; the panel needs tap speed.
- Rejected
- Autoplaying walkthrough videos or GIF captures
- Would measure
- Whether a reviewer taps a full flow before a replay.