kerfmaster pin list · Big capabilities
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-14 — computed from the item itself, not typed.
Contract — nest+post stage
This contract states a decision, not an implementation.
takes start-points ?
makes nest ?gcode
fails if A nest that reserves pierce room on an arbitrary side; a start-side decided by file order or float noise where the safety tiers tie.
Contract last changed 2026-08-13 — computed, not typed. Dated separately from the text above, so neither date can speak for the other.
Ruling (Aristide, 2026-08-13), from the -71 sheet: “I noticed you left spacing for the lead in at the top side of the parts. New rule. leave space for the lead ins on the RIGHT side by default.”
Where it is wired (same commit as this pin):
split_parts.plan_lead: among flats long enough to hold the span (≥ half the longest), the most right-facing one wins; length only breaks ties. All-arc outers take the point of the longest arc nearest 3:00. Was: longest flat, side arbitrary — the -71 squares all put their leads on top.emit._choose: rightness of the start point is the FINAL tiebreak under every safety tier (usable lead > tab on a flat > pierce standoff > tipping arm / reachability). It decides only where those tie — squares and circles, where the side used to fall out of file order. Arm/lead/reach terms are rounded to a thou so healed-geometry float noise cannot steal a tie that belongs to this rule.“By default” means: safety still outranks it. A right-side start that cannot hold a lead, lands a tab on a corner, or worsens the standoff loses to a better side, and that is correct.
Already-delivered sheets predate the rule: O71, O72, O76, O77 (builds 054/056/064/066) carry top-side lead room. Re-post on request — one command each.
Refined (Jordan, 2026-08-14), from the 33215.NC review: “The lead-in on the circle is ~45 degrees down the right side to minimize material loss. Also, the lead-in for the odd shape we put it at the bottom right for the same reason... We bias the right side so that the employee who manually removes the parts from the sheet has some consistency as to where to expect the tab.” Verified in their own NC: the round part starts/tabs at -41°, the odd shape tabs its bottom flat (centred), the squares tab mid-right. Wired same commit: machine start_clock 12 → 4.5 (still a SETTING per Aristide 2026-07-30 — the value changed, not its nature); emit._choose final tiebreak is now projection onto the 4:30 bearing, pure rightness breaks the square's right-vs-bottom tie, and the outer's approach DISTANCE dropped below the side rule (crossings of held slugs stay above — safety outranks side, side outranks travel); split_parts.plan_lead ranks flats the same way and its half-the-longest length gate became absolute (0.5") — it had wrongly disqualified -80's 1.18" bottom flat against its 3.73" right edge; the packer's rotation variants must now buy 0.1" of real width to turn a part, because a free spin carries the planned tab off the lower-right (a circle spun 7.5° for 0.01" was the defect). O100 re-posted: squares mid-right 0°, -80 bottom-right pierce straight down, circle at -45° exactly, audit clean.