B2. Fix the consent vocabulary and confidence threshold
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
Choose affirmative and negative tokens by acoustic distance from each other and from ordinary speech, in Korean and English. Set the confidence floor below which a recognition is treated as no answer. Choose the differently-worded second confirmation for destructive actions.
Realizes: #spec-voice-consent-integrity.
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 #spec-voice-consent-integrity reference and review the Korean and English consent requirements. There is no file or test named; the work is done when the affirmative and negative tokens, confidence floor, and differently worded destructive-action confirmation are decided and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100