How you get in & how it works
Entry (keyed devices only — strangers never see a hint):
① Hold the mic button ~1s → the deck does the x-ray-style flip into Direct Line. The mic is already "talk to the system" — holding it means "talk to my system."
② Keyboard C on desktop.
③ A GIA verb chip inside Signal Live.
(Three-finger tap stays screensaver; no new edge or vertical swipes — those belong to Android and the deck.)
Plumbing:
• Chat = OpenClaw session bus. The page talks to a tiny relay on Mia (Tailscale Funnel, key-cookie auth, no tokens in the client). Messages join Gia's existing session — so Telegram and this window are literally the same conversation, echoed both ways. Agent picker: Gia ▾ / backup.
• ⚡ DISPATCH = Claude Code job runner. "dispatch:" messages (or the verb) queue a job to Claude Code on Mia via the existing remote-control daemon — runs on your Max plan, not API. Progress streams back as job cards: started / step / done, tap for log. Guardrails: jobs run in a worktree, deploy steps still pass predeploy gates.
• 🎤 DICTATE = your real dictation pipeline, embedded: same capture-during-recording fix, same blob queue → OB1 consumer → destination chips. One tap from anywhere in the gallery.
• 📊 FLEET (later): the same rail Signal Live has — park / note / agent actions.
Security: the private route ships zero bytes in the public bundle — it's a separate keyed route (branded 401 without the cookie, same pattern as Signal Live). The relay only accepts the key + origin; Claude Code jobs require a second confirm for anything destructive.