Box Styles / SAi 4-Pack draft

Dieline: none yet
How a dieline gets built and improved (the loop)
  1. Save test dims (panel 1) at the size you have a reference for. Everything below runs at these dims.
  2. Upload a reference (panel 5): a Pacdora DXF/PDF export, or a die maker's file. Pick the source — die-maker outranks Pacdora. The file is kept (⬇ file) and measured; if the style already has a generator, the report diffs the two.
  3. Ask Claude for the generator or the tuning. Paste this into a Claude Code session in ~/Web/rollfed-symfony:
    dieline: SAi 4-Pack — build or tune the generator from the latest reference on its bench, render it, run the goldens, push dieline dev, and tell me what the diff against the reference says.
    Claude pulls the file from this page, writes or adjusts the style in voom-dieline (code = this style's code), checks the flat size and a rendered PNG, runs the test suite, and pushes dev. Coolify rebuilds the service on Q within a few minutes.
  4. Reload this page. An unbound style binds itself to the new generator by code (green flash, SERVICE in the header). The preview, mechanics panel and exports then come from the service.
  5. Upload the reference again to get the comparison; repeat step 3 with what it says until the diff is noise. Move to testing.
  6. Cut it. Export the DXF, cut and fold it on real board, record the result in Test notes, then approve. Only approved styles are quotable in the calculator.
Something looks wrong in the die? Two ways, use both:
  • Tune it yourself first in panel 1b (Style options): glue flap, tuck depth, lock fractions… the preview follows as you type. When it looks right, Save as default — Claude bakes those values in as the style's defaults.
  • Say what is wrong in panel 6 (Feedback). Mechanical terms work best: which flap, which edge, too deep / too shallow / won't clear / missing crease / wrong side, and at what dims (they are captured automatically). Then hand Claude:
    dieline: SAi 4-Pack — fix the open feedback on its bench (and the saved style options), render it, run the goldens, push dieline dev, mark each item done with what changed.
Reload after the service rebuilds, check, and either close the item or add the next one. A screenshot pasted into the Claude session helps when words are hard.
A new style starts with a generator written from the reference (step 3), not from the upload alone; the upload teaches proportions to a generator that exists. Full write-up: docs/PACKAGING_DIELINE_LOOP.md.
Name
Group
Description
Usage
Service style
Test notes
Workflow
draft → testing → approved = physical DXF test cut folds correctly. Record the cut in test notes before sign-off.
1 · Test dimensions
Open in calculator ↗
2 · Dieline preview
Service SVG — Pacdora colours (bleed green · cut blue · crease red) for overlay diffs
No service dieline for this style yet — a true vector preview needs a generator bound via Service style (left).
This catalogue entry has no dieline at all — identify it from the description, then decide if it deserves a service generator.
3 · 3D fold check
Bind a Service style to fold this dieline in 3D.
4 · Files for physical test cut
Cut the DXF for real → record result in test notes → approve.
5 · Reference dielines (calibration corpus)
Upload a Pacdora export or a die maker's DXF/PDF at the CURRENT test dims. The dieline service measures it, compares it against our generator, and stores the report here. A few references per style is plenty — die-maker files outrank Pacdora when rules get tuned; every change still ends in a test cut.
6 · Feedback — what is wrong with this die
One problem per note, in mechanical terms (which flap / edge, too deep or shallow, won't clear, missing crease, wrong side). The current dims and style options are attached automatically. Stays open until the fix lands.