Back to corpus
architecturetechnical paper candidatescore 28

Path A: K11-Centric -- K11 Does Everything Possible Locally

K11 is the god-node. All sensor processing, visual rendering, audio analysis, motion feature extraction, and coordination happen on K11. Other machines are optional consumers or ML inference servers. K11 runs its own feature extractor for mocopi (replacing MotionMix's MocopiFeatureExtractor), its own motion-to-music parameter mapper (port of ParamMapper logic), and its own coordination layer. MotionMix becomes a camera-only node or is removed entirely.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

K11 is the god-node. All sensor processing, visual rendering, audio analysis, motion feature extraction, and coordination happen on K11. Other machines are optional consumers or ML inference servers. K11 runs its own feature extractor for mocopi (replacing MotionMix's MocopiFeatureExtractor), its own motion-to-music parameter mapper (port of ParamMapper logic), and its own coordination layer. MotionMix becomes a camera-only node or is removed entirely. - **Minimal network dependency.** Sensor-to-visual path is entirely local. Zero Tailscale hops for the core loop. - **Single point of deployment.** All code runs on one machine. One git clone, one set of services. - **Lowest latency for visuals.** Sensor -> publisher -> Unity is loopback UDP, sub-2ms. - **Simplest failure mode.** If K11 works, everything works. No distributed failure scenarios. - **Duplicates MotionMix intelligence.** ParamMapper, ChestFlexDetector, MocopiFeatureExtractor would need C# ports in Unity or Python equivalents. That's ~800 lines of logic that already works in Swift. - **No CUDA.** ML inference still requires network hop. Can't run diffusion locally. - **Echelon not available.** The 20-crate Rust engine (128D latent, SAN, lexicon) has never been compiled for Windows. Porting is weeks of work, not hours. - **Music synthesis gap.** K11 has no audio synthesis engine. Strudel.js is on Mac5. Echelon's audio engine is iOS. Building a new audio engine on K11 is a massive undertaking. - **Single point of failure.** If K11 crashes, everything dies. No redundancy. - **Loses MotionMix's camera intelligence.** Vision body pose from iPhone, face analysis, AutoDirector scoring are iPhone-native capabilities. K11 can't run Vision framework. PARTIAL ADOPT. The sensor-to-visual path SHOULD be K11-local (it already is). But duplicating MotionMix's motion intelligence and Echelon's coordination is wrong. K11 should be sovereign for visual rendering and sensor ingestion, but should not try to replicate the iOS intelligence stack.

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.