kerfmaster pin list · Preflight — how files come in
rulingA decision by Aristide or Jordan. True because it was decided; it can be superseded, but it cannot be stale.
Content last changed 2026-08-10 — computed from the item itself, not typed.
Vocabulary — preflight stage
Ruling (Aristide, 2026-08-10): “the letters in any of our files should always be arcs, unless we say otherwise. If the resolution is too low, just let us know and then we can figure that part out.” This supersedes the open question this pin used to carry.
What it means in the pipeline: coarse uniform facet chains on lettering are COARSE ARCS — the neighbor-consistency rule applies without a cap from the absolute corner threshold (Daisy TEST1's 16-gon i-dot was a circle, full stop). Where the resolution is too low to fit arcs confidently, the result is a REPORT to Aristide/Jordan (board + message), never a silent polygon and never a silent guess. The default is arcs; only an explicit 'we meant a polygon' overrides.
The case that produced it: Daisy Cross TEST1 letters at 22°+/facet healed to 259 lines silently; Jordan caught it by eye and re-exported 10x (TEST2, build 016: 13 lines + 282 arcs, PASS 0.84 thou). Wiring the uncapped rule into heal.py is queued behind the daisy bridge emission; until then any coarse-lettered file gets flagged by hand.