Add optional Cosmos/Engine-X/act-runner templates, CWUSDC/EI-matrix tooling, non-EVM route planner in multi-chain-execution (tests passing), token list and extraction updates, and documentation (MetaMask matrix, GRU/CWUSDC packets). Ignore institutional evidence tarballs/sha256 under reports/status. Validated with: bash scripts/verify/run-all-validation.sh --skip-genesis Co-authored-by: Cursor <cursoragent@cursor.com>
Architecture & Design
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
This directory contains core architecture and design documents.
Documents
- CLIENT_DIVISION_TERMINOLOGY.md ⭐⭐⭐ - Canonical Phoenix / Sankofa / Gitea client and division terminology; reserved-word policy for
realm,tenant, andsite - NETWORK_ARCHITECTURE.md ⭐⭐⭐ - Complete network architecture with 6×/28 blocks, VLANs, NAT pools
- ORCHESTRATION_DEPLOYMENT_GUIDE.md ⭐⭐⭐ - Enterprise-grade deployment orchestration guide
- VMID_ALLOCATION_FINAL.md ⭐⭐⭐ - Complete VMID allocation registry (11,000 VMIDs)
Quick Reference
Network Architecture:
- 6× /28 public IP blocks with role-based NAT pools
- 19 VLANs with complete subnet plan
- Hardware role assignments (2× ER605, 3× ES216G, 1× ML110, 4× R630)
Deployment Orchestration:
- Phase-by-phase deployment workflow
- CCIP fleet deployment matrix (41-43 nodes)
- Proxmox cluster orchestration
Client / Division Model:
Client= GitHub Enterprise = Azure billing profile = current Gitea OrganizationDivision= generic subdivision below ClientTenant= technical isolation onlySite= infrastructure location only
Related Documentation
- ../03-deployment/ - Deployment guides
- ../04-configuration/ - Configuration guides
- ../05-network/ - Network infrastructure details
- ../07-ccip/ - CCIP deployment specification