Back to corpus
architecturetechnical paper candidatescore 46
K11 Production System Architecture -- Master Plan
_Generated 2026-04-27 via Evo3 (Research -> 6 Divergent Paths -> Compound Synthesis -> Expand + Master Plan)._ _Full evolution output: Desktop/evo-cube-output/k11-production-system-architecture/_
Full HTML reader
Read the full artifact
Extracted abstract or opening context
_Generated 2026-04-27 via Evo3 (Research -> 6 Divergent Paths -> Compound Synthesis -> Expand + Master Plan)._ _Full evolution output: Desktop/evo-cube-output/k11-production-system-architecture/_
**Three-tier hybrid architecture** combining NSSM services for headless publishers, Task Scheduler for GPU-bound Unity, and Sony's native mocopi PC app for BT sensor management. New LUMM wire format (0x4C554D4D) carries 27-bone skeletal data as a 772-byte fixed datagram on :9702.
Rejected alternatives: - Monolith (everything in Unity) -- kills audio latency win, no cross-machine flexibility - Docker -- USB/BT passthrough impossible, massive overkill for 3 Python scripts - MotionMix-centric (K11 as sensor bridge) -- breaks product premise of self-contained hardware - Full microservice (Unity as NSSM service) -- GPU inaccessible from Session 0
| Port | Protocol | Wire Format | Producer | Consumer(s) | |------|----------|-------------|----------|-------------| | 9700 | UDP | LUMD (0x4C554D44, 40B hdr) | pointcloud_pub.py | Unity LumeUdpReceiver, Tailscale mesh | | 9701 | UDP | LUMF (0x4C554D46, 84B fixed) | audio_pub.py | Unity LumeAudioFftReceiver, Tailscale mesh | | 9702 | UDP | LUMM (0x4C554D4D, 772B fixed) | mocopi_bridge.py | Unity LumeMocopiReceiver, MotionMix iOS | | 12351 | UDP | Sony binary (skdf+fram) | Sony mocopi PC app | mocopi_bridge.py (localhost only) |
Bone ordering: Sony mocopi IDs 0-26 (root, spine, chest, neck, head, shoulders, arms, hands, legs, feet, toes, fingers).
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
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.