kerfmaster pin list · UI / workflow decisions
rulingmixedA decision by Aristide or Jordan. True because it was decided; it can be superseded, but it cannot be stale.
Content last changed 2026-08-03 — computed from the item itself, not typed.
Contract — Cross-cutting stage
This contract states a decision, not an implementation.
takes —
makes material-table
fails if A default that cannot be overridden in the interface.
Contract last changed 2026-08-06 — computed, not typed. Dated separately from the text above, so neither date can speak for the other.
The team has a best-practices table (tolerances, kerf, lead style, tab widths, spacing, …). cadmaster applies those as sensible defaults so a normal job needs no fiddling — but every value must be easily overridable in the interface for the exceptions.
⚑ Build state, 2026-08-03: the overridability half is intent. Every default today is a module-level Python literal — heal.TOL 0.010, heal.FIT_TARGET 5e-4, heal.CORNER_DEG 35.0, qc.WELD_TOL 1e-4, qc.GAP_FLAG 0.060, qc.DUP_TOL 0.006, vec_pipeline.PT_PER_IN 72.0, emit.MACHINE_DEFAULT, emit.SLUG_TAB_125_STEEL. There is no config file, no settings JSON, no environment variable and no flag surface; the only things any caller can set are the board scripts' sys.argv (source, label, tolerance, width). Some values are not even reachable as keyword arguments: qc.analyze(prims, weld_tol, gap_flag) calls find_duplicates(prims) with no arguments (qc.py:186), so DUP_TOL, DUP_FRAC and DUP_MIN_LEN cannot be overridden at all.
The actual table values — many are Jordan’s shop numbers — and where each override lives in the UI (global default vs. per-job vs. per-contour).
⚑ Jordan: the real default values for the table.