openwhisper-orchestration-in-rust

Centralize state machine logic in Rust by moving phase transitions, gating rules, and status strings into the core module. Shells receive this orchestration logic through a stable snapshot and events, preventing state drift across different OS implementations.

Dictation orchestration drifts across macOS and Windows shells when state machines and status handling are duplicated in shell code. Keeping orchestration logic in the Rust core enforces a single source of truth and prevents inconsistent phase transitions.

The best way to separate UI from orchestration is to restrict shell implementations to OS APIs and UI concerns. All state machines, gating rules, and status strings must live in the Rust core and be surfaced to shells through stable snapshots and events.

Yes, you can keep platform-specific UI in shells while sharing state machines. The architecture specifies that shells handle OS APIs and UI concerns, while the Rust core handles orchestration logic and surfaces state through events and snapshots.

Refactor shell logic by moving orchestration decisions into the Rust core. Use this approach as a best-practice reference to determine where new orchestration logic belongs, ensuring shells only contain UI glue and OS API interactions.

You should not use a core Rust state machine for orchestration when an application only targets a single shell environment. This architecture applies to multi-shell applications across macOS and Windows where preventing divergence in state machines is necessary.