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
- Single Repository: All AdaptAI infrastructure in one repo
- Branch Strategy: Domain-specific branches that can be merged
- Centralized Documentation: Unified docs with domain-specific sections
- Operations Tracking: Each domain maintains operation history
- Server Registry: Central tracking of what's deployed where