Built because: "The more escalation guidance you add, the more often Fin escalates."
Where Fin stopped, and what the human inherits
Kettle runs a Fin-style deployment on its support desk. A customer's export breaks, Fin fixes it, and then the customer asks something a guidance rule sends to a human. Watch what the human inherits today: the transcript, scrolled back. Fin's own decision and the guideline it cited stop at the glass.
The bet: the receiving human needs a briefing, not a scroll. Fin already computed the decision and the citation. Surfacing them at the handover should cut the first minute of re-asking. #6 puts the reviewer in that seat.
This is a designed scenario, written for this concept. Kettle is a fictional company and nothing on this page calls a model.
Designed scenario, not a recording of Fin's product.
Fin is answering this conversation.
The replay did not start.
This page was opened from the file system, so the browser refuses to load its module script and the scenario cannot be fetched. Serve this directory over HTTP and reload.
d-021 · The handover contract field set, kept or revised
- Decision
- All five contract fields stand, and confidence stays in a fixed form.
- Because
- Each was put to three tests against the rendered card, not the JSON.
- Rejected
- Merge whatWasSaid into whatNotToRepeat
- Would measure
- Whether whatWasSaid earns its place on scenario 2.