ai-playbook 1.0.0

package/roles/devops/cloud-platforms/README.md

@@ -0,0 +1,109 @@
+# Cloud Platforms Guidance
+
+This folder provides platform-specific guidance for AWS, Google Cloud Platform (GCP), and Microsoft Azure.
+
+## Scope
+
+Use this guidance when:
+
+- Choosing between cloud platforms
+- Implementing infrastructure on specific platforms
+- Understanding platform-specific services and capabilities
+- Migrating between cloud providers
+- Leveraging platform-native features and services
+
+## AWS (Amazon Web Services)
+
+### Core Services
+- **Compute:** EC2, ECS, EKS, Lambda
+- **Storage:** S3, EBS, EFS, Glacier
+- **Database:** RDS, DynamoDB, ElastiCache, Redshift
+- **Networking:** VPC, ALB, NLB, CloudFront
+- **Monitoring:** CloudWatch, X-Ray
+- **Security:** IAM, KMS, Secrets Manager, GuardDuty
+
+### Managed Services
+- AWS RDS for managed relational databases
+- AWS DynamoDB for serverless NoSQL
+- AWS Lambda for serverless compute
+- AWS ECS for container orchestration (alternative to EKS)
+- AWS Elasticache for managed caching
+
+### Best Practices
+- Use IAM roles instead of access keys
+- Enable VPC Flow Logs for network debugging
+- Use CloudWatch for metrics and alarms
+- Implement lifecycle policies for S3
+- Use RDS read replicas for scaling
+
+## Google Cloud Platform (GCP)
+
+### Core Services
+- **Compute:** Compute Engine, GKE, Cloud Run, App Engine
+- **Storage:** Cloud Storage, Persistent Disks, Firestore
+- **Database:** Cloud SQL, Cloud Spanner, Datastore, BigTable
+- **Networking:** VPC, Cloud Load Balancing, Cloud CDN
+- **Monitoring:** Cloud Monitoring, Cloud Trace
+- **Security:** Identity and Access Management, Secret Manager, Armor
+
+### Managed Services
+- Google Cloud SQL for managed relational databases
+- Google Firestore for serverless NoSQL
+- Google Cloud Run for serverless containers
+- Google Kubernetes Engine (GKE) for managed Kubernetes
+- Google Memorystore for managed caching
+
+### Best Practices
+- Use service accounts with specific roles
+- Enable VPC Flow Logs for network debugging
+- Use Cloud Monitoring for metrics and alarms
+- Implement lifecycle policies for Cloud Storage
+- Use Cloud SQL read replicas for scaling
+
+## Microsoft Azure
+
+### Core Services
+- **Compute:** Virtual Machines, Container Instances, AKS, Functions
+- **Storage:** Blob Storage, Disk Storage, Azure Data Lake
+- **Database:** SQL Database, Cosmos DB, MySQL, PostgreSQL
+- **Networking:** Virtual Networks, Load Balancer, Application Gateway
+- **Monitoring:** Azure Monitor, Application Insights
+- **Security:** Azure AD, Key Vault, Security Center
+
+### Managed Services
+- Azure SQL Database for managed relational databases
+- Azure Cosmos DB for serverless globally-distributed NoSQL
+- Azure Functions for serverless compute
+- Azure Kubernetes Service (AKS) for managed Kubernetes
+- Azure Cache for Redis for managed caching
+
+### Best Practices
+- Use managed identities for authentication
+- Enable Azure Network Watcher for network debugging
+- Use Azure Monitor for metrics and alarms
+- Implement lifecycle policies for Blob Storage
+- Use Azure SQL read replicas for scaling
+
+## Platform Comparison
+
+| Aspect | AWS | GCP | Azure |
+| --- | --- | --- | --- |
+| Market Share | ~32% | ~9% | ~23% |
+| Kubernetes | EKS | GKE (native) | AKS |
+| Serverless Compute | Lambda | Cloud Run | Functions |
+| Managed Database | RDS | Cloud SQL | SQL Database |
+| Regional Availability | Most | Growing | Growing |
+| Enterprise Support | Excellent | Good | Excellent |
+
+## Multi-Cloud Considerations
+
+- **Kubernetes:** Runs consistently across clouds (EKS, GKE, AKS)
+- **Terraform:** Write once, deploy to multiple clouds
+- **Containers:** Run on any cloud with container runtime
+- **APIs:** Use platform-agnostic APIs where possible
+
+## Files in This Folder
+
+- `README.md` – This file
+- `checklists.md` – Cloud platform-specific checklists
+- `examples.md` – Platform-specific configuration examples

package/roles/devops/cost-optimization/README.md

@@ -0,0 +1,131 @@
+# Cost Optimization Guidance
+
+This folder provides guidance for optimizing cloud infrastructure costs while maintaining performance and reliability.
+
+## Scope
+
+Use this guidance when:
+
+- Analyzing cloud spending
+- Identifying cost reduction opportunities
+- Right-sizing infrastructure
+- Optimizing reserved capacity
+- Implementing cost monitoring and budgets
+- Balancing cost, performance, and reliability
+
+## Cloud Cost Drivers
+
+### Compute
+- Instance type and size
+- Reserved instances vs. on-demand
+- Spot instances for non-critical workloads
+- Container pricing (pods)
+- Serverless pricing (invocations, duration)
+
+### Storage
+- Storage class (hot, warm, cold)
+- Data transfer costs
+- Backup storage
+- Snapshot retention
+
+### Data Transfer
+- Outbound data transfer (most expensive)
+- Inter-region transfer
+- Cross-AZ transfer
+- CDN usage
+
+### Databases
+- Managed database pricing (CPU, storage)
+- Read replicas
+- Backup storage
+- Data transfer
+
+### Networking
+- Load balancer pricing
+- VPN and connectivity
+- NAT gateway usage
+- CloudFront/CDN
+
+## Cost Optimization Strategies
+
+### Right-Sizing
+- Analyze usage patterns
+- Identify over-provisioned resources
+- Reduce instance sizes where appropriate
+- Use auto-scaling to match load
+
+### Reserved Instances/Commitments
+- AWS Reserved Instances (1 or 3-year)
+- Google Cloud Committed Use Discounts
+- Azure Reserved Instances
+- Discount percentage increases with commitment length
+
+### Spot Instances
+- Significant savings (60-70% discount)
+- For non-critical, interruptible workloads
+- Batch processing, non-production, dev/test
+- Short-term savings
+
+### Storage Class Selection
+- Hot storage (S3 Standard) - Frequent access
+- Warm storage (S3 Standard-IA) - Infrequent access
+- Cold storage (Glacier) - Long-term archival
+- Use lifecycle policies for automatic transition
+
+### Data Transfer Optimization
+- Minimize cross-region transfer
+- Use CloudFront/CDN to reduce data transfer
+- Implement caching to reduce requests
+- Use private links to avoid internet routing
+
+### Serverless Services
+- Pay only for usage, not idle capacity
+- AWS Lambda, Google Cloud Run, Azure Functions
+- Good for variable workloads
+- Can be more expensive for consistent workloads
+
+### Automation
+- Auto-scaling to match demand
+- Automatic resource cleanup
+- Scheduled scaling for predictable patterns
+- Stop/start schedules for dev/test environments
+
+## Cost Monitoring
+
+### Budgets & Alerts
+- Set monthly budgets
+- Configure alerts for budget threshold
+- Regular cost reviews
+- Trend analysis
+
+### Cost Allocation
+- Tag resources for cost tracking
+- Allocate costs to projects/teams
+- Show-back or charge-back to teams
+- Identify expensive services/projects
+
+### Cost Analysis Tools
+- AWS Cost Explorer
+- Google Cloud Billing
+- Azure Cost Management
+- Third-party tools (CloudHealth, Cloudability)
+
+## Cost vs. Reliability Trade-offs
+
+- Reserved instances offer 40-60% discount but require commitment
+- Spot instances offer 70% discount but can be interrupted
+- Cold storage saves costs but increases retrieve latency
+- Single region is cheaper than multi-region DR
+
+## Financial Responsibility
+
+- Each organization should track costs
+- Chargeback/show-back incentivizes efficiency
+- Finance team involvement in infrastructure decisions
+- Regular cost reviews with stakeholders
+
+## Files in This Folder
+
+- `README.md` – This file
+- `checklists.md` – Cost optimization checklist
+- `examples.md` – Cost analysis examples

package/roles/devops/disaster-recovery/README.md

@@ -0,0 +1,118 @@
+# Disaster Recovery & Business Continuity Guidance
+
+This folder provides guidance for implementing backup strategies, disaster recovery plans, and business continuity procedures.
+
+## Scope
+
+Use this guidance when:
+
+- Planning disaster recovery for critical systems
+- Implementing backup strategies
+- Defining RTO and RPO targets
+- Testing disaster recovery procedures
+- Implementing multi-region failover
+- Meeting business continuity requirements
+
+## Core Concepts
+
+### RTO (Recovery Time Objective)
+- Maximum acceptable downtime
+- Measured in minutes/hours
+- Drives infrastructure choices (active-active vs. active-passive)
+- More aggressive RTOs require more investment
+
+### RPO (Recovery Point Objective)
+- Maximum acceptable data loss
+- Measured in time (5 minutes, 1 hour, etc.)
+- Drives backup and replication frequency
+- More aggressive RPOs require more resources
+
+### Recovery Strategies
+
+1. **Backup & Restore**
+   - Regular backups to separate location
+   - Restore from backup when needed
+   - Highest RTO, lowest cost
+
+2. **Standby (Active-Passive)**
+   - Standby resource ready to take over
+   - Lower RTO than backup-only
+   - Some resource waste during normal operation
+
+3. **Active-Active**
+   - Multiple regions handling traffic
+   - Instant failover
+   - Lowest RTO but highest cost
+
+## Backup Strategy
+
+### Backup Types
+- **Full Backup:** Complete copy of data
+- **Incremental Backup:** Only changes since last backup
+- **Differential Backup:** Changes since last full backup
+
+### Backup Targets
+- **On-site Storage:** Fast restore, vulnerable to local disasters
+- **Off-site Storage:** Protected from local disasters, slower restore
+- **Cloud Storage:** Scalable, cost-effective, potentially slower
+
+### Backup Frequency
+- Critical data: multiple times per day
+- Important data: daily
+- Non-critical data: weekly
+- Balance between RPO and storage costs
+
+### Backup Testing
+- Regularly test restore procedures
+- Verify data integrity after restore
+- Test restore time meets RTO targets
+- Document any issues found
+
+## Data Replication
+
+- Real-time or near-real-time replication
+- Active-active or active-passive
+- Synchronous (data fully replicated before ACK) vs. asynchronous
+- Replication lag monitoring
+
+## Failover Procedures
+
+### Automatic Failover
+- Automated health checks
+- Automatic traffic switching
+- Immediate but risk of false positives
+
+### Manual Failover
+- Human decision making
+- Slower but more controlled
+- Appropriate for lower RTO requirements
+
+### Failback
+- Procedure to return to primary after recovery
+- May involve data reconciliation
+- Document steps clearly
+
+## Disaster Recovery Plan
+
+- Document RTO and RPO targets
+- Identify critical systems and dependencies
+- Define backup and replication strategy
+- Define failover procedures
+- Define communication plan
+- Schedule regular testing (quarterly or semi-annual)
+- Maintain up-to-date contact information
+
+## Business Continuity
+
+- Extends beyond IT infrastructure
+- Considers business processes and people
+- Communication procedures during outages
+- Work-from-home capabilities
+- Alternative site operations
+- Vendor and supplier contingencies
+
+## Files in This Folder
+
+- `README.md` – This file
+- `checklists.md` – DR planning and testing checklist
+- `examples.md` – DR plan templates and examples

package/roles/devops/docker/README.md

@@ -0,0 +1,6 @@
+# Docker
+
+Use this folder for DevOps role guidance related to Docker.
+
+Add image design, Dockerfile standards, compose patterns, security checks, and
+troubleshooting notes when this packet becomes active.

package/roles/devops/examples/README.md

@@ -0,0 +1,6 @@
+# DevOps Examples
+
+Use this folder for DevOps role examples.
+
+Examples should show infrastructure changes, CI/CD flows, operational reviews,
+and deployment handoffs.