Camera in the plan: roadmap Phase 5 split into camera then inference; proposed decisions 27 (live view) and 28 (paced Orin -> tablet senders)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz

docs/ORIN-RUNTIME.md

@@ -40,7 +40,7 @@ have taken their share.
 | Valhalla server | small; tiles are **mmap'd page cache** | evictable — see below |
 | Whisper | 273 MB (tiny) → 3.9 GB (large) | `small` is 244 M params; `large` does not fit |
 | GPT-SoVITS | upstream guidance assumes an 8 GB VRAM card | the largest unknown; **measure before designing around it** |
-| vision (Phase 5) | — | competes directly with voice for the same pool |
+| vision (Phase 5) | capture and H.264: small; inference: — | capture + software H.264 costs ~1.3–2 of 6 CPU cores at 1080p (no NVENC on the Orin Nano); inference competes directly with voice for the same pool |
 
 Four rules follow.
 
@@ -185,6 +185,9 @@ Whisper runs on the Orin, so its input does too. Audio *in* on one box and audio
 *out* on the other is asymmetric on purpose: each side does the simple thing, and
 a microphone has no reason to reach the head unit.
 
+The USB camera has a microphone (48 kHz stereo, ALSA card `U1080P`): a candidate
+input, if its placement and quality suit speech. Untested.
+
 The Orin runs headless with no sound server: capture reads the ALSA device
 directly. If a service ever needs PipeWire, run it for that service's user
 (lingering), not as a desktop session.