kerfmaster pin list · UI / workflow decisions
intentWhat we want to build. Never claimed the present, so it cannot be stale — and must never be read as a description of the code.
Content last changed 2026-08-28 — computed from the item itself, not typed.
Born 2026-08-28 in Jordan's common-line message: 'we should ask this question upon onboarding in the onboarding wizard.' First time the onboarding wizard is named — a setup-time interview that captures SHOP-level preferences, distinct from per-job values (tables) and per-contour overrides.
Questions that belong here as recorded so far: (1) common-line cutting wanted? (common-line-cutting — gates that UI block). (2) Natural candidates already in the record, to be confirmed with Jordan before listing them in the wizard: start_clock / start-point bias preferences (ruled 'a setting, destined for the operator Preferences panel'), the shop's flow type (two-step programmer/laser-operator split vs combined — drives where warnings surface per gcode-warning-callouts), machine list + per-machine envelopes, and the shop's own machine-condition table sheets (Rev2 model: 'each of our clients may want to change these for themselves').
The axis beneath the wizard (Jordan, 2026-08-28): 'There are two kinds of shops, ones that do very precise work (us), and shops that cut less critical components where speed and efficiency will take precedence over accuracy. We need to be able to accommodate both.' So the wizard's deepest job is profiling the SHOP ARCHETYPE — precision-first vs speed/efficiency-first — and that archetype seeds defaults across the product (common-line cutting is the first concrete case: an accuracy-for-speed trade a production shop wants and a precision shop leaves off). Reading, per aid-the-operator-philosophy: the archetype is a DEFAULT-SEEDER, never a mode that locks features away — a precision shop can still flip any individual preference on, and vice versa. First concrete seeding mechanism (Jordan, same day): DEFAULT DISCLOSURE — the common-line block of the layout modal defaults collapsed under a chevron for a precision shop, open for a speed shop; always one click away either way.
Shape: onboarding answers live in the shop profile and gate/seed the interface everywhere; every answer stays editable later in preferences (asked once ≠ locked). Phase rule: recorded intent, no UI built.