Serialized Interaction Runtime
The public design concept for Hussh's serialized interaction runtime: coordinates and sequences tap, voice, and native inputs across all client surfaces.
TL;DR: A client-side architecture that serializes and sequences user inputs, voice sessions, and navigation directives across web and native platforms, ensuring predictable action delivery and preventing race conditions.
Status as of 2026-07-19: see body.
Relations
Architectural Principle
The Serialized Interaction Runtime guarantees that all user inputs—including tactile screen taps, verbal voice triggers, and ambient native events—are organized into a single, predictably ordered stream. Rather than allowing multiple simultaneous actions to trigger competing UI transitions or overlapping network requests, this client-side coordinator serializes all interaction intents.
This architecture ensures a fluid, responsive, and secure experience, particularly during voice-enabled multi-turn sessions where tactile interactions can easily overlap with active speech playback.
Intent Serialization
The core mechanism of the runtime revolves around intent serialization:
- Navigation Continuity: Page transitions and route movements are sequential. A newly initiated navigation intent safely supersedes any uncommitted prior navigation attempt, while identical back-to-back target requests are resolved idempotently to prevent route stacking.
- Lease-Based Session Control: Active components, such as the voice control interface and the chat popover window, require a valid voice lease to interact with the device. If a lease becomes stale or is superseded by a newer transaction, it cannot update the user interface, play audio, or dispatch backend requests.
- Idempotent Directives: System-generated commands utilize unique, session-scoped identifiers. This prevents the same directive from executing multiple times, protecting the client state machine from race conditions and inconsistent layouts.
Dual-Audience Platform Parity
The serialized interaction runtime operates transparently across both web and native applications:
- Proxy Alignment: The web application accesses backend services through secure API proxy routes, while native applications (such as packaged iOS or Android bundles) make direct calls to the same underlying APIs.
- Unified State Machine: Both transport channels resolve to the same underlying React state and action schemas, ensuring absolute parity in state representation, interface transitions, and session continuity.