Project index — October 2026
This catalogue links current repositories to architectural themes and implementation evidence. Last repository structure/README review: 11 October 2026. The review did not run or deploy every system.
Flagship studies
| Case study | Engineering focus | Starting evidence |
|---|---|---|
| PlatformPilot | Kubernetes observability and operational RBAC | Backend security tests, architecture |
| CloudOps Command Center | Risk processing, decision evidence and human approval | Contract, tests |
| OpsPilot SaaS | Multi-tenant product workflows, RBAC and persistence | Integration tests, schema |
| PropertyOps on Azure | Secure Azure application infrastructure | Bicep modules, deployment evidence |
Infrastructure and delivery
| Project | What to learn |
|---|---|
| Terraform AWS EKS | Modular IaC, Terraform native tests, cloud OIDC plan validation |
| Pharmacy API on EKS | Cognito auth, Pod Identity, DynamoDB and Kubernetes resilience |
| AZ-104 Azure Infrastructure | Bastion, VNet, scoped RBAC, Private Link, Bicep and backup |
| Backstage Developer Portal | Software catalog, developer golden paths and service scaffolding |
| GitOps with Argo CD | Declarative delivery and reconciliation in local Kubernetes |
| CI/CD Pipeline | Container scanning, SBOMs, ECR and attestations |
| Observability Platform | Metrics, traces, logs, SLOs and rule tests |
| Cloud-Native Pharmacy Platform | Multi-tenant serverless inventory workflow and integration status |
AI systems and automation
| Project | What to learn |
|---|---|
| RAG Ops Assistant | Bedrock, LangGraph, MCP, retrieval evaluation and AWS ECS |
| AI Resume Analyzer | Deterministic scoring, n8n and Bedrock workflow integration |
| AI Content Automation | Lambda, OAuth, AWS scheduling and human-reviewed publishing |
Reference and plans
The Cloud Control Plane is a vision/reference page, not a deployed unified control plane. The separately generated Backstage inventory API is a scaffold demonstration. The ASP.NET migration utility is retained as reference material; authorship/provenance is not established here. The portfolio source and this handbook are documentation repositories rather than application case studies.
Where to go next
- Evidence guide — what counts as implementation proof, and how to avoid overclaiming.
- Technology-to-project map — historical technology cross-reference (may require updating).
- Command reference — project commands and troubleshooting context.
Maintainer note: Older project pages include earlier verification dates; use the source links above for fresh source artifacts and update the individual case study before making a current production claim.