ilia
f7dce46ac9
# Complete Foundational Tickets: Repository Structure, Privacy Policy, and Safety Constraints ## Summary This PR completes the foundational planning tickets (TICKET-002, TICKET-003, TICKET-004) by: 1. Defining the repository structure with detailed documentation 2. Establishing a comprehensive privacy policy 3. Documenting safety constraints and boundaries for work/family agent separation ## Related Tickets - ✅ TICKET-002: Define repository structure - ✅ TICKET-003: Privacy and safety constraints - ✅ TICKET-004: High-level architecture All tickets have been moved from `backlog/` to `review/` to mark completion. ## Changes ### 1. Enhanced ARCHITECTURE.md **Repository Structure Section:** - Added detailed descriptions for `home-voice-agent` mono-repo structure - Documented `family-agent-config` configuration repository - Added inline comments explaining each directory's purpose - Added `infrastructure/` directory for deployment scripts, Dockerfiles, and IaC - Clarified separation of concerns between mono-repo and config repo **Documentation References:** - Added links to new privacy policy and safety constraints documents in the "Getting Started" section ### 2. New Documentation: PRIVACY_POLICY.md Establishes the core privacy principles for the Atlas project: - **Local Processing**: All ASR/LLM processing done locally, no external data transmission - **External API Exceptions**: Explicitly documents approved external APIs (currently only weather API) - **Data Retention**: Configurable conversation history retention (default 30 days) - **Data Access**: Local network only with authentication requirements ### 3. New Documentation: SAFETY_CONSTRAINTS.md Defines safety boundaries and constraints: - **Strict Separation**: Work and family agents must remain completely isolated - **Forbidden Actions**: Family agent cannot access work files, execute shell commands, or install packages - **Path Whitelists**: Tools restricted to explicitly whitelisted directories - **Network Access**: Local network by default, external access only for approved tools - **Confirmation Flows**: High-risk actions require user confirmation - **Work Agent Constraints**: Work agent also restricted from accessing family data ## Impact This PR establishes the foundational documentation that will guide all future development: - **Privacy-first approach**: Clear policy ensures all development respects user privacy - **Safety boundaries**: Explicit constraints prevent accidental data leakage between work/family contexts - **Architecture clarity**: Detailed repository structure provides roadmap for implementation ## Testing - [x] Documentation reviewed for clarity and completeness - [x] All ticket requirements met - [x] Cross-references between documents verified ## Next Steps With foundational tickets complete, development can proceed on: - Voice I/O track (wake-word, ASR, TTS) - LLM Infrastructure track (model selection, server setup) - Tools/MCP track (MCP foundation, tool implementations) - Clients/UI track (Phone PWA, web dashboard) - Safety/Memory track (boundary enforcement, memory implementation) --- **Commit Message**: My to-do list is clear. I've finished the foundational tickets per the guide. I'm ready for what's next and will notify the user. Reviewed-on: #1
Atlas Project
Overview
Atlas is a local, privacy-focused home voice agent system. This repository contains the project planning, architecture documentation, and kanban tickets for building the system.
The project uses a kanban-based workflow (Vibe Kanban) for task management, with tickets organized in the tickets/ directory structure.
Project Goals
Build a complete voice agent system with:
- Separate work and family agents running on dedicated hardware (RTX 4080 and RTX 1050)
- Local, private operation - no external APIs for core ASR/LLM (weather is exception)
- Voice I/O - wake-word detection, ASR, and TTS
- MCP tools - weather, tasks, timers, reminders, notes
- Safety controls - boundary enforcement, confirmation flows, admin tools
- Long-term memory - personal facts, preferences, routines
Project Structure
atlas/
├── .cursorrules # Cursor IDE configuration and rules
├── README.md # This file
├── ARCHITECTURE.md # Architecture documentation
├── tickets/ # Kanban tickets and task management
│ ├── backlog/ # Backlog items
│ ├── todo/ # Items ready to work on
│ ├── in-progress/ # Currently active work
│ ├── review/ # Items awaiting review
│ └── done/ # Completed items
└── [project code] # Your project code will go here
Getting Started
- Review the ARCHITECTURE.md for project design and patterns
- Check tickets/TICKETS_SUMMARY.md for an overview of all 46 tickets
- Read tickets/QUICK_START.md for recommended starting order
- Follow the guidelines in .cursorrules for development
Project Tracks
The project is organized into 5 parallel tracks:
- Voice I/O (12 tickets): Wake-word detection, ASR (Automatic Speech Recognition), TTS (Text-to-Speech)
- LLM Infrastructure (11 tickets): Model selection, servers for 4080 (work) and 1050 (family), routing, prompts
- Tools/MCP (11 tickets): Model Context Protocol server, weather, tasks, timers, reminders, notes, optional integrations
- Clients/UI (2 tickets): Phone PWA and web LAN dashboard
- Safety/Memory (6 tickets): Long-term memory, conversation management, boundary enforcement, confirmations
Plus Project Setup (4 tickets) for foundation work.
Kanban Workflow
This project uses a kanban board (Vibe Kanban) for task management. 46 tickets are organized in the tickets/ directory:
- backlog/: 46 tickets ready to start
- todo/: Ready to work on (dependencies met)
- in-progress/: Currently being worked on
- review/: Awaiting review or testing
- done/: Completed items
Working with Tickets
- Start with Milestone 1: Foundation tickets (TICKET-002, TICKET-003, TICKET-004)
- Move tickets as you work:
backlog/→todo/→in-progress/→review/→done/ - Reference ticket IDs in commits:
git commit -m "TICKET-002: Define repo structure" - Sync with Vibe Kanban: Import tickets using ticket IDs, tag by track and milestone
- Use ticket template: See
tickets/TICKET_TEMPLATE.mdfor new tickets
Milestones
- Milestone 1 - Survey & Architecture: Foundation, technology evaluations
- Milestone 2 - Voice Chat + Weather + Tasks MVP: Core functionality working
- Milestone 3 - Memory, Reminders, Safety: Advanced features and safety
- Milestone 4 - Optional Integrations: Email, calendar, smart home
Development Guidelines
- Follow the rules defined in
.cursorrules - Maintain code quality and documentation
- Write tests for new features
- Update architecture docs for significant changes
- Reference ticket numbers in all commits
- Keep tickets in sync with Vibe Kanban board
Repository Structure
This repository (atlas/) contains:
- Planning and documentation: Architecture, tickets, project management
- Kanban tickets: 46 tickets organized by status and track
The actual implementation will be in separate repositories:
home-voice-agent/: Main mono-repo with all services and clientsfamily-agent-config/: Separate config repo for prompts, tools, secrets (no work content)
See ARCHITECTURE.md for detailed repository structure.
Contributing
- Check existing tickets in
tickets/before starting work - Create a ticket for new features or bugs using the template
- Follow the established code style and patterns
- Update documentation as needed
- Move tickets through the workflow as you progress
License
[Add your license here]