atlas/tickets/done/TICKET-002_define-repos-structure.md
ilia a27af5bd54 TICKET-001: Complete initial project setup and structure
- Established foundational project files including .cursorrules, README.md, and ARCHITECTURE.md
- Created a structured tickets directory for effective management
- Configured .gitignore to streamline development

This commit finalizes the initial setup, providing a clear framework for future development and collaboration.
2026-01-05 20:24:30 -05:00

1.5 KiB

Ticket: Define Project Repos and Structure

Ticket Information

  • ID: TICKET-002
  • Title: Define Project Repos and Structure
  • Type: Setup
  • Priority: High
  • Status: Backlog
  • Track: Project Setup
  • Milestone: Milestone 1 - Survey & Architecture
  • Created: 2024-01-XX

Description

Create the repository structure for the home voice agent project:

  • Create home-voice-agent mono-repo containing:
    • LLM servers (4080 and 1050)
    • MCP tool servers
    • Clients (phone PWA, web dashboard)
    • Infrastructure code
  • Create separate family-agent-config repo for:
    • Prompts and system instructions
    • Tool configurations
    • Secrets and credentials (no work-related content)

Acceptance Criteria

  • home-voice-agent mono-repo structure defined and documented
  • family-agent-config repo structure defined
  • Clear separation between work and family agent code/config
  • Directory structure documented in ARCHITECTURE.md
  • Initial repos created (or structure documented for creation)

Technical Details

Mono-repo structure should support:

  • Separate services for LLM servers (4080 vs 1050)
  • MCP tool servers as independent services
  • Client applications (PWA, web dashboard)
  • Shared libraries and utilities
  • Clear boundaries for deployment and security

Dependencies

None - this is a foundational task.

  • ARCHITECTURE.md
  • README.md

Notes

This is a prerequisite for all other development work. Should be done first.