B1. Select the speech-to-text engine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
On-device versus cloud, Korean accuracy, latency budget, cost, and behaviour on mixed Korean-English utterances. Cloud STT contradicts nothing in the charter (the wearer's own phone calling a recognizer is not a hosted product server) but it is a dependency and a bill.
Blocks: B2, and #spec-voice-consent-integrity (a confidence threshold requires an engine that reports confidence).
Section B — Undecided forks. Registered from ISSUES.md.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Section B entry for this decision in ISSUES.md, then compare on-device and cloud speech-to-text options against Korean accuracy, latency, cost, mixed-language behavior, and confidence reporting. Done means selecting an engine and recording the decision and dependency implications so B2 and #spec-voice-consent-integrity can proceed.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100