Back to corpus
technical noteexperiment writeup candidatescore 24

MotionMix Convergence Directive

MotionMix is no longer at the "invent the architecture" stage. The major runtime pieces already exist: the iPhone/iPad capture app, `multicam-server`, the Live Director macOS app, the Convex production ledger, the still-upload path, and the low-latency hero-feed/WebRTC seam. The current job is convergence. That means turning multiple partially completed coding sessions into one coordinated push with strict lane ownership, shared situational awareness, and no duplicate implementation. The product goal for this conve

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

MotionMix is no longer at the "invent the architecture" stage. The major runtime pieces already exist: the iPhone/iPad capture app, `multicam-server`, the Live Director macOS app, the Convex production ledger, the still-upload path, and the low-latency hero-feed/WebRTC seam. The current job is convergence. That means turning multiple partially completed coding sessions into one coordinated push with strict lane ownership, shared situational awareness, and no duplicate implementation. The product goal for this convergence pass is not "train the whole music brain today." The goal is to make the **AI photoshoot lane** trustworthy, operable, and logged well enough that it can be used as a real creative workflow. 1. Stabilize the AI photoshoot runtime. 2. Add operator supervision for Ghost mode. 3. Complete Convex production-session/event writes from the live photoshoot path. 4. Start the offline training pipeline as a separate branch, without touching the live runtime. - Photoshoot Mode shell exists in Live Director. - Coverage map exists in Live Director. - Convex production ledger exists. - WebRTC hero-feed signaling/publisher/consumer seam exists. - Per-device flip controls already exist. - Smarter iPhone lens switching has already been patched. - Real still-upload path exists. - Optional Mac webcam feeds are already hidden by default in the photoshoot workflow. - `MotionMixApp` on iPhone/iPad: - `[home]/Desktop/MotionMixApp/MotionMixApp` - `multicam-server`: - `[home]/Desktop/MotionMix/multicam-server/src/main.rs` - `MotionMixLiveDirector`: - `[home]/Desktop/MotionMixLiveDirector` - Convex production backend: - `[home]/Desktop/Comp-Core/apps/convex-memory/convex` - `[home]/Desktop/MotionMix/AI-PHOTOSHOOT-TODAY-RUNBOOK.md` - `[home]/Desktop/MotionMix/AI-PHOTOSHOOT-MOTION-MUSIC-PLAN.md` - `[home]/Desktop/MotionMix/CONVEX-PRODUCTION-IMPLEMENTATION-HANDOFF.md` - `[home]/Desktop/MotionMix/CANONICAL-STATE-CONTRACT.md` - `[home]/Desktop/MotionMix/HANDOFF-AUDIO-PREP.md`

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.