Back to corpus
proposalbacklog referencescore 22
LUME Agent Contracts — v1
**Status:** authoritative as of 2026-05-24. Lock these contracts before parallel agent work continues. If anything below changes, **update this doc first**, then the agents.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Status:** authoritative as of 2026-05-24. Lock these contracts before parallel agent work continues. If anything below changes, **update this doc first**, then the agents.
This document exists because the bar's runtime is forked across three agents (K11 audio, Mac4 visuals/cameras, Mac1 dev) and they will silently drift unless they all code against the same packet schema, IPs, ports, and conventions.
**Mac1** is dev only — not in the live runtime. Its job is the repo, this doc, and ensuring the bridge code is committed.
**Twitch / OBS / NDI / hotspot are explicitly out of scope for v1.** The bar runs local. Stream comes back later.
- **Mac4 cannot run Bolt depth.** `pyorbbecsdk` on macOS reports "Femto Bolt is unavailable on macOS due to Depth Engine." Mega depth works (~30 fps), Bolt is RGB-only on Mac4. Dual-depth on Mac4 is **not pursued**. - **K11 is where Bolt depth lives** if/when needed (the original Bolt depth pipeline was proven on K11/Windows). - **K11 Pose Coach Viewer is the current Bolt owner.** While `C:\temp\lume_pose_viewer.py` is open it owns the Bolt color stream, emits `source=orbbec_bolt`, `role=bolt-rgb` pose JSON to local UDP `:9705`, and overlays body plus hand landmarks for live debugging. - **Mac4 keeps the Mega depth → Unity baseline** at `[ip]:9700`. Don't touch it. - **Mac4 RGB publisher uses the Mega**, not the Bolt, for v1. Bolt RGB + MediaPipe is a future path; permissions need to be granted to the runtime process before it can capture.
Promotion decision
What has to happen next
Keep as idea/proposal unless evidence and implementation anchors exist.
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.