Infrastructure Architecture: Platform & Runtime Design

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Infrastructure architecture designs where and how software runs — compute resources, network topology, data storage, high availability, disaster recovery, identity management, and cost optimization. It answers: "How do we provide a platform for applications?" [EXPLICIT]

When to Use

• Designing cloud infrastructure (AWS, Azure, GCP) or on-premises platforms
• Planning network topology (VPCs, subnets, firewalls, load balancers, CDN)
• Defining HA/DR strategy (availability zones, failover, backup, recovery)
• Designing IAM model (service accounts, roles, least privilege, zero trust)
• Planning cost optimization (reserved instances, spot, auto-scaling, right-sizing)
• Establishing cloud landing zones (account structure, guardrails, compliance)
• Capacity planning (compute, storage, bandwidth for growth and peaks)

When NOT to Use

• Internal software structure → software-architecture
• End-to-end solution design → solutions-architecture
• Enterprise portfolio alignment → enterprise-architecture
• Build pipelines and security controls → devsecops-architecture

---

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Does not design application software (see software-architecture) · Does not design end-to-end solutions (see solutions-architecture) · Focuses on cloud infrastructure; on. [EXPLICIT]
• Casos borde: Caso Estrategia de Manejo --- --- Migracion on-premises a cloud Periodo hibrido con coexistencia on-prem y cloud; strangler fig con VPN connectivity; migracion por fase. [EXPLICIT]
• Supuestos: · Workload requirements understood (performance, availability, compliance) · Cloud platform chosen (AWS, Azure, GCP, or hybrid) · Budget exists for infrastructure · Team has cloud. [SUPUESTO]
• Trade-off: Decision Enables Constrains When to Use --- --- --- --- Multi-AZ Survive zone failure ~2x cost, complexity Critical workloads, availability SLA **Multi-. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.