kerfmaster pin list · UI / workflow decisions
recordmixedStates what the code does today. Auditable against the code — this is the only type that can go stale.
Content last changed 2026-09-18 — computed from the item itself, not typed.
Jordan, 2026-08-28 (Add Toolpath walkthrough, 'Result of Toolpath'): 'We can see the path the laser is going to follow, including the pierce, lead-in, direction, and the dashed line is the rapid moves going from feature to feature. Questions? Our software should be able to do this, but we currently haven't asked you to visualize it however you do it in GCode. So this is a good example of what it could look like on the screen.'
What the reference view draws (MetaCam Laser Tooling tab, 8VACUSEPRNG0001 after auto-tool): the toolpath in green with direction arrowheads on every feature; a pierce marker at each pierce point; the lead-in as a short stroke into the contour; rapids as a dashed line running feature to feature, so the CUT ORDER is readable straight off the screen (this part: the six ø0.281 holes left to right along one rapid line, outer profile last, its pierce on the right edge — their auto result matches our cut-order and lower-right rules).
Status: INTENT — record, do not build the interface (phase rule). Natural seam when asked: everything the view needs is already in the posted NC + nc_audit's re-read (cut moves, G41/G42 side, pierce XY, lead spans, rapids between contours), so the view is a renderer over data we already produce — same build rule as the board: data in JSON, generator separate from presentation. A STATIC per-build toolpath plot (SVG/PDF page like the board overlay, drawn from the posted NC) would be the in-phase first form — an audit artifact, not an interface; offered to Jordan 2026-08-28.
Update, same day: the static form is BUILT and approved — see toolpath-plot-static (record). The live on-screen view remains intent.