✅ 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/
1.2 KiB
1.2 KiB
Ticket: Tool-Calling Policy
Ticket Information
- ID: TICKET-026
- Title: Tool-Calling Policy
- Type: Documentation
- Priority: High
- Status: Backlog
- Track: LLM Infra, Safety/Memory
- Milestone: Milestone 2 - Voice Chat MVP
- Created: 2024-01-XX
Description
Define tool-calling policy:
- When model is encouraged/forbidden to call tools
- High-impact actions need confirmation
- Tool permission matrix
- Escalation rules
Acceptance Criteria
- Tool-calling policy documented
- High-impact actions identified
- Confirmation requirements defined
- Permission matrix created
- Policy integrated into prompts
Technical Details
Policy should cover:
- Low-risk tools: always allowed (weather, time)
- Medium-risk: require confirmation (tasks, notes)
- High-risk: explicit user approval (email, calendar, smart home)
- Tool categories and permissions
Dependencies
- TICKET-003 (safety constraints)
- TICKET-025 (system prompts)
- MCP tool definitions (from MCP tickets)
Related Files
docs/TOOL_CALLING_POLICY.md(to be created)
Notes
Ties into confirmation flows (TICKET-045). Should be defined before tool implementation.