← back to pin list

6. Layering scheme

kerfmaster pin list · UI / workflow decisions

intentmixedWhat 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-03 — computed from the item itself, not typed.

Contract — Report stage

This contract describes a stage we intend to build — it is NOT a description of the code.

takes healed-geometrytopology

makes delivery

fails if A generated layer a CAD package will not render; our work indistinguishable from the original.

Contract last changed 2026-08-06 — computed, not typed. Dated separately from the text above, so neither date can speak for the other.

Intent. The interface will show the work as toggleable layers over the original; the final layer set and how they stack is still open. What exists today (2026-08-03) is two boards, and they disagree on the house rule. The vector board has real toggles — srclayer, fitlayer, hazlayer, each with a checkbox (build_vec_board.py:215-217, 364-372); the speck group exists but has no checkbox. The DXF board writes the source straight into the SVG with no group id (build_board.py:195) and offers one checkbox, for the bridge / spacing mark-up. So the base-layer rule is met on one board and not the other.

Layers on the table

Open