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/
61 lines
1.4 KiB
Markdown
61 lines
1.4 KiB
Markdown
# Ticket: Confirmation Flows
|
|
|
|
## Ticket Information
|
|
|
|
- **ID**: TICKET-045
|
|
- **Title**: Confirmation Flows
|
|
- **Type**: Feature
|
|
- **Priority**: High
|
|
- **Status**: Backlog
|
|
- **Track**: Safety/Memory
|
|
- **Milestone**: Milestone 3 - Memory, Reminders, Safety
|
|
- **Created**: 2024-01-XX
|
|
|
|
## Description
|
|
|
|
Implement confirmation flows for high-risk actions:
|
|
- Risk classification (high-impact actions list)
|
|
- Confirmation UX (text and voice prompts)
|
|
- Agent explains action, asks for "Yes/No"
|
|
- Log decisions
|
|
- Enforcement at tool level (signed confirmation token from client)
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] Risk classification system implemented
|
|
- [ ] High-impact actions identified and documented
|
|
- [ ] Confirmation UX designed (text + voice)
|
|
- [ ] Confirmation flow working
|
|
- [ ] Decision logging implemented
|
|
- [ ] Tool-level enforcement (confirmation token)
|
|
|
|
## Technical Details
|
|
|
|
High-impact actions:
|
|
- Send email
|
|
- Calendar changes
|
|
- File edits outside "safe" areas
|
|
- Smart-home actions
|
|
- High-value task changes
|
|
|
|
Confirmation flow:
|
|
1. Agent proposes action
|
|
2. User confirms (voice or UI)
|
|
3. Signed token generated
|
|
4. Tool validates token before execution
|
|
5. Action logged
|
|
|
|
## Dependencies
|
|
|
|
- TICKET-026 (tool-calling policy)
|
|
- TICKET-029 (MCP server)
|
|
- TICKET-039 (phone client) or TICKET-040 (web dashboard)
|
|
|
|
## Related Files
|
|
|
|
- `home-voice-agent/safety/confirmations/` (to be created)
|
|
|
|
## Notes
|
|
|
|
Ties into clients for presenting confirmations. Critical for safety.
|