infra/.planning/ROADMAP.md

# Roadmap: NixOS Infrastructure with AI Assistant

## Overview

This roadmap outlines the implementation of a reproducible NixOS infrastructure with Docker service management, integrated with an AI assistant for automated operations. The system will automatically detect and integrate new Docker services while maintaining consistency across deployments.

## Domain Expertise

None

## Phases

- ✅ **Phase 1: Foundation Setup** - Establish core NixOS configuration with flakes
- ✅ **Phase 2: Docker Service Integration** - Integrate Docker Compose services
- ✅ **Phase 3: AI Assistant Integration** - Enable AI-assisted infrastructure management
- [ ] **Phase 4: Internet Access & MCP** - MCP server for web access


## Phase Details

### Phase 1: Foundation Setup
**Goal**: Establish the core NixOS configuration with flakes and basic infrastructure
**Depends on**: Nothing (first phase)
**Research**: Unlikely (established Nix patterns)
**Plans**: 3 plans
**Status**: Complete

Plans:
- [x] 01-01: Set up NixOS flake structure with hardware configuration
- [x] 01-02: Configure basic services and networking
- [x] 01-03: Implement secrets management with agenix

### Phase 2: Docker Service Integration
**Goal**: Integrate Docker service management with Traefik reverse proxy
**Depends on**: Phase 1
**Research**: Unlikely (existing Docker Compose patterns)
**Plans**: 3 plans
**Status**: Complete

Plans:
- [x] 02-01: Implement docker_manager.nix for service integration
- [x] 02-02: Configure Traefik reverse proxy with automatic TLS
- [x] 02-03: Set up persistent storage for Docker services

### Phase 3: AI Assistant Integration
**Goal**: Enable AI assistant to manage infrastructure operations
**Depends on**: Phase 2
**Research**: Likely (AI integration patterns)
**Research topics**: OpenCode AI API, infrastructure management patterns, natural language parsing for service operations
**Plans**: 2 plans
**Status**: Complete

Plans:
- [x] 03-01: Integrate OpenCode AI assistant with NixOS configuration
- [x] 03-02: Implement natural language command parsing

### Phase 4: Internet Access & MCP
**Goal**: Set up MCP server for web access and enhanced functionality
**Depends on**: Phase 3
**Research**: Likely (MCP server configuration)
**Research topics**: MCP server setup, web access integration, security considerations
**Plans**: 2 plans

Plans:
- [x] 04-01: Configure MCP server for external access
- [x] 04-02: Test web search capabilities and integration

### Phase 4.1: Organize Accumulated Commits (INSERTED)

**Goal**: Organize uncommitted changes into logical, meaningful commits
**Depends on**: Phase 4
**Status**: Complete
**Plans**: 5 plans

Plans:
- [x] 04-01: Stage Docker stack integration files
- [x] 04-02: Commit system configuration improvements
- [x] 04-03: Update service modules and remove deprecated systemd services
- [x] 04-04: Add n8n-worker user and update authentication
- [x] 04-05: Update flake imports and infrastructure secrets

**Details**:
Successfully organized accumulated changes into 5 logical commits:
1. Docker stack integration with improved service management
2. System configuration enhancements (hardware sensors, GPU support, security)
3. Service module updates and cleanup of deprecated systemd services
4. User and authentication configuration updates
5. Flake and infrastructure updates

### 🚧 v5.0 TAK Server (In Progress)

**Milestone Goal:** Add TAK (Tactical Assault Kit) server with web interface for team coordination and offsite operator integration

#### Phase 5: TAK Server Research & Selection

**Goal**: Research and select the optimal TAK-compatible server with web interface
**Depends on**: Previous milestone complete
**Research**: Likely (comparing different TAK implementations)
**Research Method**: Use DuckDuckGo tool for web research
**Research topics**: Open-source TAK-compatible servers with web UIs, COT protocol support, geospatial mapping, deployment requirements, security considerations
**Plans**: TBD

Plans:
- [ ] 05-01: Research TAK-compatible open-source implementations
- [ ] 05-02: Compare features and select optimal solution
- [ ] 05-03: Document research findings and recommendations

#### Phase 6: TAK Server Implementation

**Goal**: Implement TAK server as Docker service with Traefik integration
**Depends on**: Phase 5 (research completed)
**Research**: Unlikely (following established Docker patterns)
**Plans**: TBD

Plans:
- [ ] 06-01: Create Docker Compose configuration
- [ ] 06-02: Set up persistent storage and Traefik routing
- [ ] 06-03: Integrate with docker_manager.nix module

#### Phase 7: TAK Server Testing & Validation

**Goal**: Validate TAK server functionality and integration
**Depends on**: Phase 6 (implementation complete)
**Research**: Unlikely
**Plans**: TBD

Plans:
- [ ] 07-01: Test COT protocol functionality
- [ ] 07-02: Verify web interface and geospatial features
- [ ] 07-03: Validate security and integration



## Progress

**Execution Order:**
Phases execute in numeric order: 1 → 2 → 3 → 4 → 5 → 6 → 7

| Phase | Milestone | Plans Complete | Status | Completed |
|-------|-----------|----------------|--------|-----------|
| 1. Foundation Setup | v1.0 | 3/3 | Complete | - |
| 2. Docker Service Integration | v1.0 | 3/3 | Complete | - |
| 3. AI Assistant Integration | v1.0 | 2/2 | Complete | - |
| 4. Internet Access & MCP | v1.0 | 2/2 | Complete | - |
| 5. TAK Server Research | v5.0 | 0/3 | Not started | - |
| 6. TAK Server Implementation | v5.0 | 0/3 | Not started | - |
| 7. TAK Server Testing | v5.0 | 0/3 | Not started | - |