Back to corpus
research noteexperiment writeup candidatescore 32

LumeBodyTruth Contract

`LumeBodyTruth` is the perception authority above the camera/sensor feeds. It answers one question for every consumer: "what do we trust about the performer right now?"

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Implementation status: v0 read endpoint is live in `multicam-server` as `GET /body-truth`. `LumeBodyTruth` is the perception authority above the camera/sensor feeds. It answers one question for every consumer: "what do we trust about the performer right now?" It is not a custom neural network yet. It is a fused state layer that combines depth, RGB, mocopi, iPhone/SAN, and MotionMix signals into one stable body truth object. | Machine | Current role | Should own | |---|---|---| | Mac4 | Unity `lume-pcloud`, Femto Mega/Bolt, depth/stereo Arducam, Insta360 view/evidence feed, mocopi bridge | DYK visuals, rich BodyTruth capture, depth/matte, first Sony/mocopi proof | | Mac2 | Insta360 USB/UVC or desktop-bridge camera host when physically connected there | Room-wide reconstruction/evidence angle, calibration capture, session review | | K11 | Rekordbox, pose viewer, AirDeck bridge, optional UVC Arducam/Insta360/simple webcam, self-play, SAN receiver | DJ command safety gate, keyboard/MIDI dispatch, motion recording | | MotionMix hub | Rust multicam server, `/skeleton-3d`, `/mocopi/state` | Canonical shared body bus and `LumeBodyTruth` publisher | | iPhones | MotionMix/SAN/camera evidence | Supplemental sensors, training evidence, extra viewpoints | MotionMix already emits `fused_body_state` from `multicam-server/src/main.rs`. That state includes useful fields such as:

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.