Back to corpus
technical noteexperiment writeup candidatescore 40

Codex context — where LUME started + how it got here

> **Topology correction, 2026-04-26:** Mac4 is the current Unity Editor / GUI smoke-test host and real-Femto capture host. Mac5 is still the synthpub LaunchAgent / synthetic fallback host. Do not blindly replace all Mac5 references; see `software/demo/TOPOLOGY-CORRECTION-2026-04-26.md`.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> **Topology correction, 2026-04-26:** Mac4 is the current Unity Editor / GUI smoke-test host and real-Femto capture host. Mac5 is still the synthpub LaunchAgent / synthetic fallback host. Do not blindly replace all Mac5 references; see `software/demo/TOPOLOGY-CORRECTION-2026-04-26.md`. _Read this BEFORE `CODEX-PLAN.md`. ARCHITECTURE.md describes WHAT is built; this file describes WHY it's built that way._ You're inheriting a 22-commit pipeline. The destination matters less than the load-bearing decisions made along the way — a dozen of them look "obvious" only because they were extracted painfully from constraints you don't see in the final tree. This file is the decision log. LUME v1's scope was anchored on a Saturday-night ship target. The work that became Wave 1 was sized to fit that window: - 1-3 vertical monitors, depth camera (Femto Mega) + audio (UMA-8), Unity URP scene rendering an audio-reactive point cloud. - Form factor: a 500mm wide × 120mm tall × 85mm deep bar (Sonos-style). - Compute target initially: NVIDIA Jetson AGX Orin 64GB ($1999) inside the bar.

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.