- Added .cursorrules for project guidelines and context - Created README.md for project overview and goals - Established ARCHITECTURE.md for architectural documentation - Set up tickets directory with initial ticket management files - Included .gitignore to manage ignored files and directories This commit lays the foundation for the Atlas project, ensuring a clear structure for development and collaboration.
6.2 KiB
6.2 KiB
Tickets Summary
This document provides an overview of all tickets organized by track and milestone.
Ticket Organization
Tickets are organized in the tickets/ directory by status:
backlog/- Future work itemstodo/- Ready to work onin-progress/- Currently activereview/- Awaiting review/testingdone/- Completed
Tickets by Track
Project Setup (4 tickets)
- TICKET-002: Define Project Repos and Structure
- TICKET-003: Document Privacy Policy and Safety Constraints
- TICKET-004: High-Level Architecture Document
- TICKET-047: Hardware & Purchases
Voice I/O (12 tickets)
- TICKET-005: Evaluate and Select Wake-Word Engine
- TICKET-006: Prototype Local Wake-Word Node
- TICKET-007: Train or Configure Custom Wake-Word
- TICKET-008: Wake-Word False Positive/Negative Tuning
- TICKET-009: Select ASR Engine and Target Hardware
- TICKET-010: Implement Streaming Audio Capture → ASR Service
- TICKET-011: Define ASR API Contract
- TICKET-012: Benchmark ASR Latency and Quality
- TICKET-013: Evaluate TTS Options
- TICKET-014: Build TTS Service
- TICKET-015: Voice Consistency and Volume Leveling
- TICKET-016: Integrate TTS with Clients
LLM Infra (11 tickets)
- TICKET-017: Survey Candidate Open-Weight Models
- TICKET-018: LLM Capacity Assessment
- TICKET-019: Select Work Agent Model (4080)
- TICKET-020: Select Family Agent Model (1050)
- TICKET-021: Stand Up 4080 LLM Service
- TICKET-022: Stand Up 1050 LLM Service
- TICKET-023: Implement LLM Routing Layer
- TICKET-024: LLM Logging & Metrics
- TICKET-025: System Prompts for Family vs Work Agents
- TICKET-026: Tool-Calling Policy
- TICKET-027: Multi-Turn Conversation Handling
Tools/MCP (11 tickets)
- TICKET-028: Learn and Encode MCP Concepts
- TICKET-029: Implement Minimal MCP Server
- TICKET-030: Integrate MCP with LLM Host
- TICKET-031: Weather Tool
- TICKET-032: Time / Date / World-Clock Tools
- TICKET-033: Timers and Reminders
- TICKET-034: Home Tasks/Chores (Markdown Kanban)
- TICKET-035: Notes & Files (Markdown, PDFs)
- TICKET-036: Email Integration (Optional)
- TICKET-037: Calendar Integration (Optional)
- TICKET-038: Smart Home Integration (Optional)
Clients/UI (2 tickets)
- TICKET-039: Phone-Friendly Client (PWA or Native)
- TICKET-040: Web LAN Dashboard
Safety/Memory (6 tickets)
- TICKET-041: Long-Term Memory Design
- TICKET-042: Long-Term Memory Implementation
- TICKET-043: Conversation Summarization & Pruning
- TICKET-044: Boundary Enforcement
- TICKET-045: Confirmation Flows
- TICKET-046: Admin Tools
Tickets by Milestone
Milestone 1 - Survey & Architecture
- TICKET-002: Define Project Repos and Structure
- TICKET-003: Document Privacy Policy and Safety Constraints
- TICKET-004: High-Level Architecture Document
- TICKET-005: Evaluate and Select Wake-Word Engine
- TICKET-009: Select ASR Engine and Target Hardware
- TICKET-013: Evaluate TTS Options
- TICKET-017: Survey Candidate Open-Weight Models
- TICKET-018: LLM Capacity Assessment
- TICKET-019: Select Work Agent Model (4080)
- TICKET-020: Select Family Agent Model (1050)
- TICKET-028: Learn and Encode MCP Concepts
- TICKET-029: Implement Minimal MCP Server
Milestone 2 - Voice Chat + Weather + Tasks MVP
- TICKET-006: Prototype Local Wake-Word Node
- TICKET-007: Train or Configure Custom Wake-Word
- TICKET-008: Wake-Word False Positive/Negative Tuning
- TICKET-010: Implement Streaming Audio Capture → ASR Service
- TICKET-011: Define ASR API Contract
- TICKET-014: Build TTS Service
- TICKET-015: Voice Consistency and Volume Leveling
- TICKET-016: Integrate TTS with Clients
- TICKET-021: Stand Up 4080 LLM Service
- TICKET-022: Stand Up 1050 LLM Service
- TICKET-023: Implement LLM Routing Layer
- TICKET-025: System Prompts for Family vs Work Agents
- TICKET-027: Multi-Turn Conversation Handling
- TICKET-030: Integrate MCP with LLM Host
- TICKET-031: Weather Tool
- TICKET-032: Time / Date / World-Clock Tools
- TICKET-034: Home Tasks/Chores (Markdown Kanban)
- TICKET-039: Phone-Friendly Client (PWA or Native)
- TICKET-040: Web LAN Dashboard
Milestone 3 - Memory, Reminders, Safety
- TICKET-012: Benchmark ASR Latency and Quality
- TICKET-024: LLM Logging & Metrics
- TICKET-026: Tool-Calling Policy
- TICKET-033: Timers and Reminders
- TICKET-035: Notes & Files (Markdown, PDFs)
- TICKET-041: Long-Term Memory Design
- TICKET-042: Long-Term Memory Implementation
- TICKET-043: Conversation Summarization & Pruning
- TICKET-044: Boundary Enforcement
- TICKET-045: Confirmation Flows
- TICKET-046: Admin Tools
Milestone 4 - Optional Integrations & Smart Features
- TICKET-036: Email Integration (Optional)
- TICKET-037: Calendar Integration (Optional)
- TICKET-038: Smart Home Integration (Optional)
Dependency Graph
Foundation (No Dependencies)
- TICKET-002: Define Project Repos and Structure
- TICKET-003: Document Privacy Policy and Safety Constraints
- TICKET-004: High-Level Architecture Document (depends on TICKET-002, TICKET-003)
Parallel Tracks (Can Start After Foundation)
- Voice I/O: TICKET-005, TICKET-009, TICKET-013 (evaluations can start)
- LLM Infra: TICKET-017, TICKET-018 (surveys can start)
- MCP: TICKET-028 (MCP concepts can start)
Critical Path for MVP
- TICKET-002, TICKET-003, TICKET-004 (Foundation)
- TICKET-005, TICKET-009, TICKET-013 (Voice evaluations)
- TICKET-017, TICKET-018, TICKET-019, TICKET-020 (Model selection)
- TICKET-028, TICKET-029 (MCP foundation)
- TICKET-006, TICKET-010, TICKET-014 (Voice implementation)
- TICKET-021, TICKET-022 (LLM servers)
- TICKET-030 (MCP-LLM integration)
- TICKET-031, TICKET-034 (Core tools)
- TICKET-039 (Phone client)
- End-to-end testing
Quick Start
- Start with Milestone 1 tickets (surveys and architecture)
- Move tickets from
backlog/totodo/as you're ready to work on them - Move to
in-progress/when actively working - Move to
review/when complete and ready for testing - Move to
done/when approved/merged
Notes
- Many tickets can be worked on in parallel (e.g., Voice I/O, LLM Infra, MCP)
- Some tickets have explicit dependencies listed in their descriptions
- Optional tickets (TICKET-036, TICKET-037, TICKET-038) should be done after MVP
- Hardware purchases (TICKET-047) can be done in parallel with software development