Stage 2: COMPOUND
| Path | Core Insight | Adopt | Reject | |------|-------------|-------|--------| | A: Full Local | Zero-cloud voice ordering on Jetson is architecturally clean | Queue analytics via depth centroid tracking, Piper TTS, cart state machine port | GPU contention risk, LLM-for-NLU overkill, memory pressure | | B: Companion iPad | 100% BWB code reuse, zero technical risk | V0.5 pilot strategy, WebSocket relay between LUME and companion device | Two-device proposition permanently (acceptable for V0.5, not V1) | | C: Cloud
Full HTML reader
Read the full artifact
Extracted abstract or opening context
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.