ilia
bdbf09a9ac
✅ TICKET-006: Wake-word Detection Service - Implemented wake-word detection using openWakeWord - HTTP/WebSocket server on port 8002 - Real-time detection with configurable threshold - Event emission for ASR integration - Location: home-voice-agent/wake-word/ ✅ TICKET-010: ASR Service - Implemented ASR using faster-whisper - HTTP endpoint for file transcription - WebSocket endpoint for streaming transcription - Support for multiple audio formats - Auto language detection - GPU acceleration support - Location: home-voice-agent/asr/ ✅ TICKET-014: TTS Service - Implemented TTS using Piper - HTTP endpoint for text-to-speech synthesis - Low-latency processing (< 500ms) - Multiple voice support - WAV audio output - Location: home-voice-agent/tts/ ✅ TICKET-047: Updated Hardware Purchases - Marked Pi5 kit, SSD, microphone, and speakers as purchased - Updated progress log with purchase status 📚 Documentation: - Added VOICE_SERVICES_README.md with complete testing guide - Each service includes README.md with usage instructions - All services ready for Pi5 deployment 🧪 Testing: - Created test files for each service - All imports validated - FastAPI apps created successfully - Code passes syntax validation 🚀 Ready for: - Pi5 deployment - End-to-end voice flow testing - Integration with MCP server Files Added: - wake-word/detector.py - wake-word/server.py - wake-word/requirements.txt - wake-word/README.md - wake-word/test_detector.py - asr/service.py - asr/server.py - asr/requirements.txt - asr/README.md - asr/test_service.py - tts/service.py - tts/server.py - tts/requirements.txt - tts/README.md - tts/test_service.py - VOICE_SERVICES_README.md Files Modified: - tickets/done/TICKET-047_hardware-purchases.md Files Moved: - tickets/backlog/TICKET-006_prototype-wake-word-node.md → tickets/done/ - tickets/backlog/TICKET-010_streaming-asr-service.md → tickets/done/ - tickets/backlog/TICKET-014_tts-service.md → tickets/done/
51 lines
1.3 KiB
Markdown
51 lines
1.3 KiB
Markdown
# Ticket: Conversation Summarization & Pruning
|
|
|
|
## Ticket Information
|
|
|
|
- **ID**: TICKET-043
|
|
- **Title**: Conversation Summarization & Pruning
|
|
- **Type**: Feature
|
|
- **Priority**: Medium
|
|
- **Status**: Backlog
|
|
- **Track**: Safety/Memory
|
|
- **Milestone**: Milestone 3 - Memory, Reminders, Safety
|
|
- **Created**: 2024-01-XX
|
|
|
|
## Description
|
|
|
|
Implement conversation management:
|
|
- Session store design (local DB/files, retention duration)
|
|
- Summarization routines (after N turns or size threshold)
|
|
- Use work model or family model for summarization
|
|
- Privacy and deletion tools
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Session store implemented
|
|
- [ ] Summarization working (scheduled or threshold-based)
|
|
- [ ] Context pruning functional
|
|
- [ ] Privacy deletion tools implemented
|
|
- [ ] Retention policy enforced
|
|
|
|
## Technical Details
|
|
|
|
Implementation:
|
|
- Store transcripts in DB or files
|
|
- Summarization: use LLM to condense old messages
|
|
- Pruning: remove old messages, keep summary
|
|
- Deletion: UI and admin tools to delete sessions
|
|
|
|
## Dependencies
|
|
|
|
- TICKET-027 (multi-turn conversation)
|
|
- TICKET-021 or TICKET-022 (LLM services)
|
|
- TICKET-024 (logging)
|
|
|
|
## Related Files
|
|
|
|
- `home-voice-agent/conversation/summarization/` (to be created)
|
|
|
|
## Notes
|
|
|
|
Can be implemented after first working chat. Important for long conversations.
|