# 27. Craft-Dairy Process Training — Expert Interview to Floor-Ready Kit (amber, dairy-ledger)

**Audience:** new production operators at a craft dairy scaling 6 → 24 staff · **Artifacts:** `01-interview-capture.html` (designer practice) · `02-tankline-module.html` (2D) · `3d.html` + `tankline.js` and `cd-hall.js` (3D tank line) · shared data `tankline-data.js` · `03-enablement-pack.html` · **Case study:** `index.html`

**In one line:** a full SME-to-kit pipeline — a founder's expert interview becomes a CCP micro-module, a print floor manual, a KB article and a test plan, with every artifact traceable to a passage she actually said.

## Why this kit exists

Small producers scale faster than they can document. The craft that made the product good lives in a founder's hands, and the near-misses start when "what I do before I open that valve" is taught by having been watched once. This kit demonstrates the translator pipeline that fixes it — and, deliberately, the interview discipline underneath it.

## What the artifacts do

- **01 Interview capture** — for designers: the (fictional) transcript with ten highlighted passages; classify each as critical task, misconception, vocabulary or constraint, then see the requirement and the artifact it feeds.
- **02 Tank Line Gates** — for operators: four gates (surface cue vs. record vs. avoiding the call), then write the deviation note. Options shuffle; score /10; debrief names the habit.
- **3D tank line** (flagship) — the production hall walked at eye height on a May morning: the tanker at the door, CIP, the valve manifold and the release dock. At each station the surface cue stands next to a closed record you open and an over-cautious move; a labelled glass teaching line fills white, amber or red after each call. Frames from the build are in `storyboard.md`. Checked in headless Chrome with software rendering (SwiftShader) only; not tested on a real GPU, phone or tablet.
- **03 Enablement pack** — print floor manual (NL/EN), a KB article on why the note is the decision, predicted FAQ, the three-learner test protocol and pre-committed measures.

## The design decisions worth noticing

- **Traceability as the interaction** — the interview explorer makes the pipeline itself the thing you practise, not just the process
- **Constraints drive format** — no screens on the floor (hygiene, wet gloves), no logins (agency staff rotate), two languages: print at the tank, digital on the tablet, same words
- **The note is written and scored** — after Gate 4 the operator picks the entries that belong in the note; hearsay and surface cues count against it
- **Reuse and honesty** — the test plan maps each row to a learning objective, and failures route back to a named artifact, not to "more training"

## Independent learning value

Reference artifact (interview) + scored decision module + reference pack: a complete translator case that stands alone, and also demonstrates the SME-capture craft the target roles ask for by name.