# Proposed AdaptAI Unified Repository Structure

## Target Structure
```
/data/adaptai/
├── docs/
│   ├── architecture/
│   ├── runbooks/
│   └── deployment/
├── platform/
│   ├── dataops/           # Atlas domain
│   │   ├── docs/
│   │   │   ├── runbooks/
│   │   │   └── architecture/
│   │   ├── scripts/
│   │   │   ├── deployment/
│   │   │   ├── maintenance/
│   │   │   └── disaster-recovery/
│   │   ├── configs/
│   │   │   ├── databases/
│   │   │   └── monitoring/
│   │   └── operations_history.md
│   ├── mlops/             # Archimedes/Quartz domain
│   │   ├── docs/
│   │   ├── scripts/
│   │   ├── configs/
│   │   └── operations_history.md
│   ├── commsops/          # Vox domain
│   │   ├── docs/
│   │   ├── scripts/
│   │   ├── configs/
│   │   └── operations_history.md
│   └── devops/            # Zephyr domain
│       ├── docs/
│       ├── scripts/
│       ├── configs/
│       └── operations_history.md
├── deployment/
│   ├── server_registry.md
│   ├── deployment_history.md
│   └── environments/
│       ├── vast1/
│       ├── india-1/
│       └── production/
├── logs/                  # Centralized logging (existing)
├── secrets/               # Centralized secrets (existing)
└── CLAUDE.md             # Master operations guide
```

## Key Benefits
1. **Single Repository**: All AdaptAI infrastructure in one repo
2. **Branch Strategy**: Domain-specific branches that can be merged
3. **Centralized Documentation**: Unified docs with domain-specific sections
4. **Operations Tracking**: Each domain maintains operation history
5. **Server Registry**: Central tracking of what's deployed where