Layer

kerfmaster pin list · Definitions

recordmixedStates what the code does today. Auditable against the code — this is the only type that can go stale.

Content last changed 2026-08-03 — computed from the item itself, not typed.

Vocabulary — Intake stage

Layer = a named grouping that every entity in a DXF belongs to. CAD packages use layers to switch groups of geometry on and off, colour them, and decide what is real geometry versus notes. We use them in three distinct places, and they should not be confused with each other.

1. On the way in — the customer's layers

A customer's layers may carry meaning we need (cut vs engrave vs construction lines vs dimensions) or may be meaningless. We never assume. Related: item 8 (cut vs engrave) and item 10 (export layer table).

2. On the way out — our layer table

Cut geometry and annotation are kept strictly apart, so a file can go to the machine without anything to explain away:

HEALED — the healed cut geometry
ORIGINAL — the customer's geometry, for reference
CM_BRIDGE_OK — bridges measured at or above the table minimum
CM_BRIDGE_ADJUST — undersized bridges, with the proposal drawn
CM_SPACING_FLAG — narrow webs that are spacing, not bridges
CM_NOTES — text callouts

The shop's DXF standard is R2000-2002 (AC1015), so that is what we write. We also ship a mark-up-only DXF containing the annotation layers and no geometry, for opening alongside the cut file.

The cut-path review DXF is a second table, and it is not this one. cutpath_dxf.LAYERS writes CUT, LEAD, PIERCE, SEQ, DIR, RAPID, RAPID_HAZARD, HELD, LEGEND, TAB, TIP_ARM, TIP_CENTRE. Both tables exist in code today; item 10 lists neither in full.

3. On screen — the base layer

House style: the original DXF is always the base layer, drawn thick and gray, with healed and generated work overlaid on top and each overlay toggleable. That is what makes a discrepancy visible instead of arguable. Half met, 2026-08-03: the vector board honours it (srclayer, fitlayer, hazlayer groups, each with a checkbox — build_vec_board.py:215-217, 364-372). The DXF board does not: the source paths are written straight into the SVG with no group id (build_board.py:195), and the only checkbox on that page toggles the bridge / spacing mark-up (brlayer). See item 6.