MotionMix Sphere Product Architecture - Current

MotionMix should treat a session as a Sphere: a shared capture room where people, phones, cameras, audio sources, gestures, stage controls, and later editing assets belong to one temporary production space. The user should not have to think in terms of IP addresses, ports, device tokens, or a Rust multicam server. The user-facing act is simple: create a Sphere, invite a friend, scan a QR code or open a link, assign what that friend contributes, and start recording or directing. This maps directly onto the infrastructure already built. The iPhone or iPad app is a node. The multicam server on port 9404 is the Sphere coordinator. Live Director is the production surface. K11 is the heavy local archive, command gate, and studio storage node. SAN and BodyTruth are analysis lanes. The future Studio tab is where the resulting rushes, body-motion evidence, cuts, and templates become reusable media. The clean consumer story is: you want to do a podcast with a friend, so you create a Sphere called something like "Saturday episode." Your friend downloads MotionMix, opens your invite link, and chooses a role. Their iPhone can become a guest camera, a guest mic, a room angle, a shared clap sync source, or just a contributor device for remote capture. The Sphere owns the relationship between all of these devices, not the individual app windows. For a podcast, the host may have one main iPhone, one side iPhone, one iPad running Director, and one Mac or K11 storage node. A friend can add another iPhone camera from across the table or from another location if the network mode supports it. The result is not just a video call. It is a structured capture session with labeled sources, synchronized recordings, optional live switching, and post-session assets that can be cut later. The same model works for dance, rehearsal, stage capture, interviews, DJ sets, choreography, fitness coaching, and community challenges. The common object is always the Sphere.