Back to corpus
architecturetechnical paper candidatescore 20

Stage 1 Path C: The Unified Voice Router — One Intent Classifier for All Devices

> Grounded in: Stage 0 finding that VoiceRouter (35 intents, iOS), FleetVoiceRouter (fleet intents, iOS), and SpeakFlow VoiceCommandService (15 commands, macOS) are three separate intent classifiers with incompatible taxonomies. Voice commands work differently depending on which device you're on.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Stage 1 Path C: The Unified Voice Router — One Intent Classifier for All Devices > Grounded in: Stage 0 finding that VoiceRouter (35 intents, iOS), FleetVoiceRouter (fleet intents, iOS), and SpeakFlow VoiceCommandService (15 commands, macOS) are three separate intent classifiers with incompatible taxonomies. Voice commands work differently depending on which device you're on. Port intent classification to the server. One classifier, shared across all clients. The iPhone, Mac, glasses, and any future device all send audio/text to the same endpoint. The server classifies the intent, resolves the target, and dispatches. Device-specific logic is limited to audio capture and playback. **3. Client Updates:** - iOS OpenClawHub: Replace VoiceRouter.classify() + FleetVoiceRouter.classify() with POST to /voice/command - SpeakFlow macOS: Replace VoiceCommandService local classification with POST - Mac Ear Daemon (Path A): Use /voice/command directly - Benefit: fix a classification bug once, all devices get the update - One intent classifier for all devices — consistent behavior everywhere - Pronoun resolution and context tracking work across device switches - New intents added once, available everywhere - Server-side classification can use more powerful models (embedding similarity, LLM fallback) - Device-agnostic: any device that can capture audio and play TTS can be a voice client

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.