Nest name + program number — auto-assign next number from external sequence, easy override (Jordan 2026-08-28)

kerfmaster pin list · UI / workflow decisions

intentWhat 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-09-06 — computed from the item itself, not typed.

Source: Jordan's nesting walkthrough step 2, 2026-08-28 — screenshot Nesting_Step_2_Name_and_Prog_number (incoming/1787937986_645725_Nesting_Step_2_Name_and_Prog_number.JPG), MetaCam's Layout Settings dialog over the live 8VACUSEPRNG0001 nest.

• What the dialog carries: Name (auto from DXF file name: 8VACUSEPRNG0001), User (PC3), Program number (33285, spinner), Comments (MCWW J# 36381 — the customer code + shop job number ride in comments), Machine: 3015LVPlusII-45CFR / Material: SUSN7, 0.06 with a Change button, 'Process only one part of each type' checkbox, Defaults link. Settings tree: General (Basic, Sheet, Custom) / Process (Reposition, Laser Sequence, Bridge/Common cut, Traverse Routing, Element order) — joins EDIT_TOOLING and Layout Array as reference feature set; note Traverse Routing is MetaCam's name for the rapid routing lever our cut-order section records as not built.
• Program number — the ruled ask: the number follows a sequence the shop stores EXTERNALLY (outside MetaCam) today. We are asked to own it: auto-assign the next number from the last one used, with an easy override. Aid-the-operator shape: the tracked sequence seeds the field, the operator can type over it, the override is recorded beside the seeded value, never resisted. The counter is job data, not machine data — scope ANSWERED (Jordan 2026-09-06: 'This will vary per shop'): shop-wide vs per-machine is a per-shop CONFIGURATION, an onboarding-wizard/shop-profile item, never a fixed rule; today's single shop-wide sequence (app/progseq.json) stands as the default until the preference surface is built.
• Name + date + versioning (ours to propose, per his message): proposal — the name stays the human label (DXF-derived, editable); version identity does NOT ride in the name but in the job-versioning chain (every posted delivery creates an immutable internal version, GitHub model — pin job-versioning); the DISPLAY name auto-suffixes the date and internal version (e.g. 8VACUSEPRNG0001 — 2026-08-28 v3) so two nests of the same part never collide even if the operator never types a name. Awaiting Jordan's correction.
• (1) ANSWERED (Jordan 2026-08-31): the sequence is SHOP-WIDE ('we use a shop wide program # system'); the 6XXXX numbers are MetaCam trying to automate the next number — 'that's how far it's off, we can do better.' So the 65-66xxx range is MetaCam's wayward auto-assign, 33xxx is the shop's real sequence; our auto-assign = last used + 1 on the shop-wide sequence, operator-seeded and overridable. First live seed: Jordan set the next block to start at 33286 (Navistar jobs 3683209C2 / 3683147C1+3683175C1 / 3683148C1). Still open: the per-shop scope preference surface (shop.json question + per-machine sequences when a shop answers per-machine); (2) reserved ranges the auto-increment must skip: P9996/P9997 are live nest macros on the control, and 9000-series programs are typically protected macro space.