MVT option-C file — the four layers, finally documented

kerfmaster pin list · The spec — what we build to

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

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

Record (measured 2026-08-09, PyMuPDF forcing each OCG on): Aristide's OPTION_C_MVT-ICONtest_modified_mounting_template copy.ai — full table, renders and the source file at viewer/mvt/option-c-file/.

• Nested C Option Setup (ON, 902 items): the option-C cut nest — blue cloud plate with the chart as holes in one compound path, ring+triangle, 899 orange items dominated by individual chaser rings, the black never-seen-metal piece, the green template cloud.
• Layer C setup (OFF, 7 items): the mounting design assembled in place — green wall template outline, black never-seen-metal regions with dashed strap/slot marks, the bottom wall cleat bar. The stud-slot fields, measured (2026-08-09, scale 29.98" template ↔ 177.9 pt): two fields of slot marks (35 on the bottom cleat spanning 23.7", 16 on the mid never-seen bar, drawn 1.08" long as dashed depictions — cut height is the ruled 5/16"). Each field is TWO ROWS 0.60" apart, pitch 1.33", in-row gap 0.26", rows staggered 0.73". The math this encodes: pitch 1.33" < the 1.5" stud face, so each row ALONE puts ≥1.07" of slot over every stud at any lateral offset — no stud can ever be missed, and every stud takes a bolt in BOTH rows (the two-bolt vertical couple of [[stud-slot-rules]] exists at every offset). The stagger additionally covers each row's 0.26" gaps with 0.35" to spare, so the union coverage is CONTINUOUS — there is no x-position on the cleat where a lag bolt faces solid metal in both rows. Verified subpath-by-subpath from the black compound path. The green is the TEMPLATE WE CREATE (Aristide, 2026-08-09: “so it is easier to hang the sign for the customer”): not a plain outline but the silhouette-following band of [[mount-architecture]], measured outer 30.0" × 22.3", inner 28.6" × 21.3" — an installer deliverable cut with the job. It carries 4 zip-tie holes, and each one has a TWIN in the black never-seen metal ~0.17" away center-to-center, straddling the green/black boundary — the opposed-pair rule of [[fastener-holes]] drawn in the wild, one hole each side of the shared line so the tie pulls square. Four orange 0.49" × 0.34" lozenges mark the tie points; holes are DRAWN 0.075" (locators — under both the 0.110" strap diagonal and the 0.125" pierce floor; cut size is the ruled 1/8", same convention as the slot dashes drawn 0.11" but cut 5/16"). Four pairs total, plus one orphaned mark: a lone 0.108" orange dot on the band's left-middle edge — Aristide meant it as zip-tie holes, but verified 2026-08-09: NO holes exist there and NO black metal reaches it (nearest black geometry 2.77" away), so the intent was never drawn into geometry. Realizing it needs the black extended to the band there (or a strap), or the dot dropped — Aristide's call, open. A mark carrying intent with no geometry behind it is the same defect class as round 2's unregenerated claims — the self-QC clause applies to teaching files too.
• Washers (OFF, 159 items): the chaser map — every orange dot one cut ring, in register over the assembly, including the two free-floating grids. "The colored rings are the chasers we cut" (Aristide, 2026-08-09): the dot blocks in the art are physical rings cut from the job's own waste, doubling as design elements and as standoff stacks on the mounting pins ([[mvt-mounting-rulings]]).
• Option B (OFF, 3 items): assembled color reference — blue cloud + orange ring/triangle, the raised-plate build on pins and chaser stacks aided by magnets.

Layers 2–4 share one rectangle (215.5–393.4 x 330.0–462.1 pt): a back-to-front sandwich behind the art. This file was handled since July with three layers never opened — the miss that produced [[layers-are-the-manifest]].

The green band, ruled and derived (2026-08-10)

Function (Aristide): the green is the customer’s SPATIAL ID — “it is drawn so that the customer can have a spatial ID of how big the logo is going to be when they mount it on the wall.” The hard rule that follows: the band’s edge never takes up more space than the art — nothing proud of the silhouette beyond kerf-class. Coverage of every scallop matters less than the extremes; the footprint is the message.

The lone red dot is a BRIDGE MARKER, not zip-tie holes: “i added the red bridge to be able to create the outline green, to bridge the gap that was there in the artwork.” The gap is a bottle — a 1.13" mouth into a 28.6 in² void between the two cloud bodies — and the bridge is a DON’T-CARE: “just connect the two elements”; its exact line cannot mislead the spatial read because other elements set the leftmost and topmost extremes. This closes the orphan-dot question for THIS file.

Record: mvt_cut.derive_band() now CALCULATES the band instead of tracing his drawn one: outer edge = the plates’ silhouette flush (his hand trace was 0.017" off, called an illustration error); the marked mouth sealed by the shortest sharp-corner chord that provably closes the void ((40.88, 65.90)–(41.69, 66.71), matching his drawn line to 0.02"); inner edge kept as drawn (it hugs the bracket at each tie point so the pairs straddle the shared cut line); tie holes at his drawn dot positions, SIZED TO FUNCTION — 0.125" = max(2.5 mm strap diagonal 0.110", pierce floor), both plates alike (ruling, Aristide 2026-08-10, off the discrepancy he spotted in the emitted file: green was cut at his 0.075" marker dots, black blown to 0.28" by the slot corrector; the dots give the position, the function gives the size — marker dots are exempt from slot correction). Derived boundary healed to true arcs: 0 fit jogs, census clean, worst deviation 0.013" localized at the chord nub and one inner-line jag — both under kerf-class. acceptance_mvt.py grades the emitted DXF 8/8 with the chord as record data and a paired-hole gate (4 green + 4 black, each within a mil of 0.125", worst pair span measured).