Extracted abstract or opening context
> Current-doc warning, 2026-04-30: parts of this README still describe the earlier Jetson/SVPro in-bar architecture. The active build is documented in `LUME_CURRENT_BUILD_SPEC.md` and `PRINT_APPROVAL_QUEUE_CURRENT.md`: K11 rear pod, ZHAOCAILIN top display cradle, centered Femto Mega, and Arducam IMX586 auxiliary camera.
| File | Purpose | |---|---| | `lume-config.scad` | Global dimensions, component footprints, toggles. **Edit here first.** | | `lume-primitives.scad` | Reusable helpers: `rbox`, `cchamfer`, `hex_grille`, `slot_grille`, `lens_cutout`, `insert_boss`, `insert_boss_gusseted`, `bolt_m3_counterbore`, `rib`, `cable_clip`, `strain_relief`, `lip_tongue`/`lip_groove`. | | `lume-components.scad` | Proxy volumes for Jetson, Femto Mega, UMA-8, Noctua fan, SVPRO, NeoPixel ring. Swap with vendor STEPs when available. | | `lume-shell.scad` | Exterior shell. Front/rear cutouts, interior ribs, gusseted corner bolt bosses, split halves (`lume_shell_front` / `lume_shell_rear`). | | `lume-internals.scad` | Jetson sled (96×96 pattern + heat-set bosses), Noctua fan shroud, thermal baffle, Femto bracket, SVPRO brackets (L+R), UMA-8 mic rail, cable backbone, port bracket anchor posts. | | `lume-bezel.scad` | Separate printable front bezel insert + blank camera plug (for v1 demo rigs using only 2 cameras). | | `lume-port-bracket.scad` | Rear port bracket with labeled cutouts: HDMI, USB-A ×2, Ethernet. Screws to interior-rear via 4 corner bolts. | | `lume-vesa.scad` | VESA 100×100 plate **or** French cleat (bar-side + wall-side). | | `lume-main.scad` | Top-level assembly. Shell + internals + proxies + bezel + diffuser + port bracket + VESA. Exploded view supported. | | `render.sh` | Headless render pipeline. |
- `assembly` — shell ghosted, internals + components solid - `shell_only` — just the assembled shell - `print_front` / `print_rear` — isolate each half for slicer
Pass `-D EXPLODED=true` with `assembly` to offset parts along Y for exploded-view docs.
1. Edit `lume-config.scad` (or any module) 2. `./render.sh preview` (fast, ~1 min total) 3. Check `exports/assembly.png` + `exports/exploded.png` 4. When fit looks right: `./render.sh stl` 5. Slice in Cura / PrusaSlicer → print
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.