ilia/atlas

History

ilia 3b8b8e7d35 Evaluate and Select Wake-Word Engine (#3 )

# 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`

Reviewed-on: #3

2026-01-05 21:34:40 -05:00

backlog

Evaluate and Select Wake-Word Engine (#3 )

2026-01-05 21:34:40 -05:00

done

Evaluate and Select Wake-Word Engine (#3 )

2026-01-05 21:34:40 -05:00

in-progress

Initialize project structure with essential files and documentation

2026-01-05 20:09:44 -05:00

review

Initialize project structure with essential files and documentation

2026-01-05 20:09:44 -05:00

todo

# Complete Foundational Tickets: Repository Structure, Privacy Policy, and Safety Constraints (#1 )

2026-01-05 20:24:58 -05:00

.gitkeep

Initialize project structure with essential files and documentation

2026-01-05 20:09:44 -05:00

QUICK_START.md

Initialize project structure with essential files and documentation

2026-01-05 20:09:44 -05:00

README.md

Initialize project structure with essential files and documentation

2026-01-05 20:09:44 -05:00

TICKET_TEMPLATE.md

Initialize project structure with essential files and documentation

2026-01-05 20:09:44 -05:00

TICKETS_SUMMARY.md

docs(tickets): Mark TICKET-013 as done in summary

2026-01-05 20:34:05 -05:00

README.md

Kanban Tickets

This directory contains all project tickets organized by their kanban status.

Directory Structure

backlog/: Future work items that are planned but not yet ready to start
todo/: Items that are ready to be worked on
in-progress/: Items currently being actively developed
review/: Items that are complete but awaiting review, testing, or approval
done/: Completed items (archived for reference)

Ticket Naming Convention

Tickets should be named using the format:

[TICKET-ID]_[short-description].md

Example: TICKET-001_setup-project-structure.md

Workflow

Create: New tickets start in backlog/ or todo/ depending on readiness
Start Work: Move ticket from todo/ to in-progress/ when starting
Complete: Move ticket from in-progress/ to review/ when implementation is done
Approve: Move ticket from review/ to done/ when approved/merged

Using with Vibe Kanban

Create tickets in this directory structure
Import or reference these tickets in your Vibe Kanban board
Keep ticket files in sync with kanban board status
Use ticket IDs to reference in commits and PRs

Template

Use TICKET_TEMPLATE.md when creating new tickets to ensure consistency.