Back to corpus
research noteexperiment writeup candidatescore 18

Two-sensor topology modes

_Five distinct ways to deploy a Mega + Bolt pair. Ranked by recommendation, with CAD impact, software impact, calibration effort, BOM cost per unit shipped, and aesthetic readout._

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

_Five distinct ways to deploy a Mega + Bolt pair. Ranked by recommendation, with CAD impact, software impact, calibration effort, BOM cost per unit shipped, and aesthetic readout._ **TL;DR — recommended primary path. Two complete bars, identical except for the front camera module. Mega-bar stays as Mac4 dev rig. Bolt-bar becomes the production-aesthetic flagship.** ### Geometry - Bar 1 (Mega): existing 500×120×85mm bar with current Mega cradle. Pod attached. K11 in pod. Wall-mount via pod VESA. - Bar 2 (Bolt): NEW slim bar at 500×120×60mm. Bolt cradle redesigned for 39mm depth + USB-C only. Pod attached. K11 in pod. Wall-mount via pod VESA. ### CAD impact - Net new Bolt-cradle module in `lume-shell.scad`. About 60 lines of SCAD. - New `lume-config-bolt.scad` overriding LUME_DEPTH=60, FEMTO_W=140 etc. - Bolt-bar shell halves regenerate at smaller dims (300×30×120, 200×30×120). - Pod stays identical between the two bars (K11 same, dims same). - **Estimated effort:** 1 day SCAD + half-day STL regen + half-day reslice in OrcaSlicer. ### Software impact - **Zero.** Both bars run the same wire format, same Unity components, same software. Two LUME bars = two unrelated installations from the software's perspective. Each has its own Mac running Unity, its own publisher, its own audio sidecar, its own user.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

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.