# Ticket: Evaluate and Select Wake-Word Engine

## Ticket Information

- **ID**: TICKET-005
- **Title**: Evaluate and Select Wake-Word Engine
- **Type**: Research
- **Priority**: High
- **Status**: Backlog
- **Track**: Voice I/O
- **Milestone**: Milestone 1 - Survey & Architecture
- **Created**: 2024-01-XX

## Description

Evaluate wake-word detection options and select one:
- Compare openWakeWord and Porcupine for:
  - Hardware compatibility (Linux box/Pi/NUC)
  - Licensing requirements
  - Ability to train custom "Hey Atlas" wake-word
  - Performance and resource usage
  - False positive/negative characteristics

## Acceptance Criteria

- [ ] Comparison matrix of wake-word options
- [ ] Selected engine documented with rationale
- [ ] Hardware requirements documented
- [ ] Licensing considerations documented
- [ ] Decision recorded in architecture docs

## Technical Details

Options to evaluate:
- openWakeWord (open source, trainable)
- Porcupine (Picovoice, commercial)
- Other open-source alternatives

Considerations:
- Custom wake-word training capability
- Resource usage on target hardware
- Latency requirements
- Integration complexity

## Dependencies

- TICKET-004 (architecture) - helpful but not required
- Hardware availability for testing

## Related Files

- `docs/WAKE_WORD_EVALUATION.md` (to be created)
- `ARCHITECTURE.md`

## Notes

Can start in parallel with LLM infra and MCP design. Needs hardware + microphone availability for testing.