diff --git a/docs/gitops-cicd/06-implementation-plan.md b/docs/gitops-cicd/06-implementation-plan.md
deleted file mode 100644
index 758ee2b..0000000
--- a/docs/gitops-cicd/06-implementation-plan.md
+++ /dev/null
@@ -1,838 +0,0 @@
-# FinTech GitOps CI/CD - План внедрения
-
-**Версия:** 1.0  
-**Дата:** Январь 2026  
-**Целевая аудитория:** Management, Project Managers, All Teams
-
----
-
-## Содержание
-
-1. [Executive Summary](#1-executive-summary)
-2. [Timeline Overview](#2-timeline-overview)
-3. [Detailed Implementation Plan](#3-detailed-implementation-plan)
-4. [Risks and Mitigation](#4-risks-and-mitigation)
-5. [Resource Requirements](#5-resource-requirements)
-6. [Budget and ROI](#6-budget-and-roi)
-7. [Success Metrics](#7-success-metrics)
-8. [Communication Plan](#8-communication-plan)
-
----
-
-## 1. Executive Summary
-
-### 1.1 Project Overview
-
-**Цель:** Внедрение современной CI/CD методологии на базе GitOps принципов для автоматизации разработки, тестирования и развертывания приложений в закрытой инфраструктуре FinTech компании.
-
-**Scope:**
-- Полная инфраструктура CI/CD с GitOps automation
-- Development и Production окружения
-- AI-ассистент для технической поддержки
-- Обучение всех команд
-- Миграция существующих приложений
-
-**Duration:** 6 месяцев (Development environment: 5 недель, Production: 4 месяца, Migration: продолжается)
-
-**Budget:** $150,000 - $230,000 (hardware) + $20,000/year (software licenses) + внутренние ресурсы
-
-### 1.2 Expected Benefits
-
-**Количественные:**
-- Deployment frequency: с 1-2/месяц до 10+/день
-- Lead time: с 2-4 недель до <4 часов
-- MTTR: с 2-4 часов до <15 минут
-- Change failure rate: с 20-30% до <5%
-
-**Качественные:**
-- Полный audit trail для compliance
-- Снижение operational risks
-- Faster time to market
-- Improved team satisfaction
-- Better resource utilization
-
-**Финансовые:**
-- ROI: 12-18 месяцев
-- Экономия на downtime: ~$200k/year
-- Экономия времени команд: 40% → ~$150k/year
-- **Total annual benefit: ~$350k/year**
-
----
-
-## 2. Timeline Overview
-
-### 2.1 High-Level Phases
-
-```
-Month 1-2: Planning & Development Environment
-├── Week 1-2: Planning, approvals, procurement
-├── Week 3-5: Dev environment setup
-├── Week 6-8: Testing, validation, training
-
-Month 3-4: Production Infrastructure
-├── Week 9-10: Hardware procurement & delivery
-├── Week 11-14: Production setup
-├── Week 15-16: Testing & validation
-
-Month 5-6: Migration & Rollout
-├── Week 17-18: Pilot applications
-├── Week 19-22: Gradual migration
-├── Week 23-24: Stabilization & optimization
-
-Ongoing: Continuous Improvement
-```
-
-### 2.2 Critical Milestones
-
-| Milestone | Date | Deliverable |
-|-----------|------|-------------|
-| **M1: Project Kickoff** | Week 1 | Approved plan, team assigned |
-| **M2: Dev Environment Ready** | Week 5 | Fully functional dev environment |
-| **M3: Team Trained** | Week 8 | Team comfortable with tools |
-| **M4: Hardware Delivered** | Week 10 | All production hardware on-site |
-| **M5: Production Ready** | Week 16 | Production environment operational |
-| **M6: First Pilot Success** | Week 18 | 2 apps successfully migrated |
-| **M7: 50% Migration** | Week 22 | Half of apps using GitOps |
-| **M8: Project Complete** | Week 24 | All critical apps migrated |
-
----
-
-## 3. Detailed Implementation Plan
-
-### Month 1: Planning & Initial Setup
-
-#### Week 1-2: Project Initiation
-
-**Activities:**
-- Finalize project plan и получить approvals
-- Form project team и assign roles
-- Conduct stakeholder kickoff meeting
-- Submit hardware procurement requests
-- Setup project management tracking (Jira/Confluence)
-
-**Team:**
-- Project Manager (1 FTE)
-- DevOps Engineers (2 FTE)
-- Infrastructure Engineers (1 FTE)
-- Security Architect (0.5 FTE)
-- Network Engineer (0.5 FTE)
-
-**Deliverables:**
-- Approved project plan
-- Team roster и RACI matrix
-- Procurement orders submitted
-- Project tracking setup
-- Communication channels established
-
-**Approvals Required:**
-- Budget approval (Finance)
-- Security review (CISO)
-- Compliance sign-off (Compliance Officer)
-- Network changes (Network team)
-
-#### Week 3-5: Development Environment Setup
-
-**Week 3: Base Infrastructure**
-- Network setup (VLANs, firewall rules)
-- Server provisioning (12 VMs)
-- OS installation и basic hardening
-- Storage configuration
-
-**Week 4: Core Services**
-- Gitea deployment и configuration
-- Jenkins setup с essential plugins
-- Harbor installation
-- PostgreSQL databases
-- Initial testing
-
-**Week 5: Orchestration & AI**
-- Docker Swarm initialization
-- Portainer deployment
-- GitOps Operator setup
-- Ollama & MCP Server deployment
-- End-to-end integration testing
-
-**Deliverables:**
-- Fully functional dev environment
-- All services operational
-- Integration tests passed
-- Initial documentation
-
-### Month 2: Testing & Training
-
-#### Week 6-7: Comprehensive Testing
-
-**Functional Testing:**
-- CI/CD pipeline testing (multiple application types)
-- GitOps workflow validation
-- Rollback procedures
-- Security scanning
-
-**Performance Testing:**
-- Load testing Jenkins builds
-- High-frequency deployments
-- Monitoring under load
-
-**Security Testing:**
-- Vulnerability scanning
-- Penetration testing basics
-- Access control verification
-- Audit logging validation
-
-**Disaster Recovery:**
-- Backup/restore procedures
-- Failover testing
-- Data recovery scenarios
-
-**Deliverables:**
-- Test reports
-- Identified issues и resolutions
-- Performance baselines
-- Updated documentation
-
-#### Week 8: Team Training
-
-**Training Modules:**
-
-**Day 1-2: GitOps Fundamentals**
-- GitOps concepts и principles
-- Infrastructure as Code
-- Git workflows (branching, PR, merge)
-- Hands-on: Create repository, make changes
-
-**Day 3-4: CI/CD Pipelines**
-- Jenkins overview
-- Pipeline as Code (Jenkinsfile)
-- Docker image builds
-- Security scanning integration
-- Hands-on: Build first pipeline
-
-**Day 5-6: Docker Swarm & Deployment**
-- Docker Swarm concepts
-- Service deployment
-- Scaling и rolling updates
-- Troubleshooting
-- Hands-on: Deploy application
-
-**Day 7: AI Assistant & Monitoring**
-- Using Ollama AI for support
-- Grafana dashboards
-- Log analysis via Loki
-- Alerting
-- Hands-on: Query AI, create dashboard
-
-**Day 8-9: Troubleshooting & Best Practices**
-- Common issues и solutions
-- Debugging techniques
-- Security best practices
-- Compliance requirements
-- Hands-on: Troubleshooting scenarios
-
-**Day 10: Assessment & Certification**
-- Practical assessment
-- Q&A session
-- Certification ceremony
-- Feedback collection
-
-**Participants:**
-- All DevOps team members (mandatory)
-- Development team leads (mandatory)
-- Interested developers (optional)
-- Operations team (mandatory)
-- Security team representatives
-
-**Deliverables:**
-- Training materials
-- Certification list
-- Feedback summary
-- Improvement recommendations
-
-### Month 3-4: Production Infrastructure
-
-#### Week 9-10: Hardware Procurement
-
-**Activities:**
-- Track hardware orders
-- Prepare datacenter space
-- Network cabling preparation
-- Power и cooling verification
-- Receive и inventory hardware
-
-**Parallel Activities:**
-- Refine production architecture based на dev learnings
-- Update documentation
-- Prepare production deployment scripts
-- Security review production design
-
-#### Week 11-14: Production Deployment
-
-**Week 11: Base Infrastructure**
-- Rack и stack hardware
-- BIOS configuration
-- Network configuration
-- Storage setup (RAID, LVM)
-- OS installation (all servers)
-- Basic hardening
-
-**Week 12: Core Services**
-- PostgreSQL cluster setup (master-slave)
-- Gitea production deployment
-- Jenkins production setup
-- Harbor production installation
-- Backup systems configuration
-
-**Week 13: Orchestration**
-- Docker Swarm production cluster (3 managers, 6+ workers)
-- Overlay networks
-- Secrets management
-- GitOps Operator deployment
-- Portainer production
-
-**Week 14: AI & Monitoring**
-- Ollama production (with GPU if available)
-- MCP Server production
-- Full monitoring stack (Prometheus, Grafana, Loki)
-- AlertManager configuration
-- Integration testing
-
-**Deliverables:**
-- Fully operational production environment
-- All HA configured
-- Backups operational
-- Monitoring active
-- Documentation updated
-
-#### Week 15-16: Production Validation
-
-**Testing:**
-- Comprehensive security audit
-- Penetration testing (external vendor)
-- Performance testing (производственная нагрузка)
-- Disaster recovery full drill
-- Compliance validation
-
-**Documentation:**
-- Production runbooks
-- Incident response procedures
-- Escalation matrix
-- SLA definitions
-- Maintenance windows
-
-**Final Approvals:**
-- Security sign-off
-- Compliance approval
-- Change Management Board approval
-- Executive sponsor sign-off
-
-**Deliverables:**
-- Security audit report
-- Penetration test results
-- Performance benchmarks
-- DR test results
-- Go-live approval
-
-### Month 5-6: Migration & Stabilization
-
-#### Week 17-18: Pilot Migration
-
-**Select Pilot Applications:**
-Criteria for pilot selection:
-- Non-critical to business (low risk)
-- Active development (frequent changes)
-- Team willing to be early adopters
-- Representative of typical applications
-
-**Pilot Applications (2-3):**
-1. Internal tool (low risk, high visibility)
-2. API service (moderate complexity)
-3. Web application (full stack)
-
-**Migration Process:**
-- Create Git repositories
-- Setup CI pipeline
-- Configure CD automation
-- Migrate deployment to Swarm
-- Monitor closely (1-2 weeks)
-
-**Success Criteria:**
-- Successful automated deployments
-- No major incidents
-- Improved deployment frequency
-- Positive team feedback
-- Performance maintained or improved
-
-**Deliverables:**
-- Pilot migration report
-- Lessons learned
-- Refined procedures
-- Updated training materials
-
-#### Week 19-22: Gradual Migration
-
-**Migration Schedule:**
-
-**Week 19:** Batch 1 (5 applications)
-- Low complexity applications
-- Well-documented
-- Active maintenance
-
-**Week 20:** Batch 2 (5 applications)
-- Medium complexity
-- Multiple teams
-- Integration points
-
-**Week 21:** Batch 3 (5 applications)
-- Higher complexity
-- Critical services (with extra caution)
-- Legacy code
-
-**Week 22:** Batch 4 (5 applications)
-- Most complex applications
-- High availability requirements
-- Compliance-sensitive
-
-**Migration Approach per Batch:**
-- Planning meeting (Monday)
-- Repository setup (Tuesday)
-- CI pipeline creation (Wednesday)
-- CD configuration (Thursday)
-- Migration execution (Friday)
-- Weekend: Close monitoring
-- Week after: Stabilization
-
-**Support:**
-- War room during migrations
-- 24/7 on-call during first weekend
-- Daily standup с pilot teams
-- Quick issue resolution
-
-#### Week 23-24: Stabilization
-
-**Activities:**
-- Monitor all migrated applications
-- Fine-tune resource allocations
-- Optimize CI/CD pipelines
-- Address technical debt
-- Improve documentation
-
-**Retrospective:**
-- Lessons learned workshop
-- Process improvements
-- Team feedback
-- Success celebration
-
-**Final Deliverables:**
-- Migration complete report
-- Updated documentation
-- Performance metrics
-- Cost savings analysis
-- Recommendations для future
-
----
-
-## 4. Risks and Mitigation
-
-### 4.1 Technical Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| **Hardware delivery delays** | Medium | High | Order early, have backup vendors |
-| **Integration issues** | Medium | Medium | Thorough testing в dev, phased rollout |
-| **Performance problems** | Low | Medium | Performance testing, capacity planning |
-| **Security vulnerabilities** | Low | Critical | Security review at each phase, pen testing |
-| **Data loss during migration** | Low | Critical | Multiple backups, tested restore procedures |
-| **Compatibility issues** | Medium | Medium | Dev environment mirrors production, thorough testing |
-
-### 4.2 Organizational Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| **Resistance to change** | High | Medium | Clear communication, training, show benefits |
-| **Lack of skills** | Medium | High | Comprehensive training program, documentation |
-| **Key person dependency** | Medium | High | Knowledge sharing, documentation, cross-training |
-| **Scope creep** | Medium | Medium | Clear scope, change control process |
-| **Resource unavailability** | Medium | High | Buffer in schedule, backup resources |
-| **Stakeholder misalignment** | Low | High | Regular communication, demonstrate progress |
-
-### 4.3 Compliance Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| **Regulatory non-compliance** | Low | Critical | Compliance review at each phase, external audit |
-| **Audit findings** | Medium | High | Implement controls early, regular internal audits |
-| **Data privacy violations** | Low | Critical | Encrypt everything, access controls, GDPR compliance |
-
-### 4.4 Business Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| **Service disruption** | Low | Critical | Gradual rollout, rollback procedures, extensive testing |
-| **Budget overrun** | Medium | Medium | Detailed budgeting, contingency fund (20%) |
-| **Timeline slippage** | Medium | Medium | Realistic timeline, buffer in schedule, agile approach |
-| **Benefit realization delay** | Medium | Low | Quick wins, measure metrics, communicate successes |
-
----
-
-## 5. Resource Requirements
-
-### 5.1 Team Allocation
-
-**Full-time (for 6 months):**
-- Project Manager: 1 FTE
-- DevOps Engineers: 2 FTE
-- Infrastructure Engineer: 1 FTE
-
-**Part-time:**
-- Security Architect: 0.5 FTE (more в certain phases)
-- Network Engineer: 0.5 FTE (Week 1-3, Week 11-14)
-- DBA: 0.25 FTE (database setups)
-- Compliance Officer: 0.25 FTE (reviews)
-
-**As-needed:**
-- Development team leads (training, migration)
-- Application teams (migration weeks)
-- External consultants (penetration testing)
-
-**Total Person-Months:** ~30 PM
-
-### 5.2 External Resources
-
-**Consultants:**
-- Penetration testing vendor: 1 week, $15k
-- Training partner (optional): $10k
-
-**Contractors (optional):**
-- Additional DevOps help: 2-3 months, $60k
-
-### 5.3 Training Time
-
-**Team members:**
-- 10 days formal training
-- 5 days hands-on practice
-- Ongoing learning (20% time)
-
-**Total training cost (opportunity cost):**
-- 20 people * 15 days * $500/day = $150k
-
----
-
-## 6. Budget and ROI
-
-### 6.1 Implementation Costs
-
-**Capital Expenditure (CapEx):**
-
-| Category | Cost | Notes |
-|----------|------|-------|
-| **Servers** | $100,000 | 27 servers для production + dev |
-| **Storage** | $40,000 | SSD, HDD, NAS |
-| **Network Equipment** | $50,000 | Switches, firewall, VPN |
-| **GPU (Ollama)** | $15,000 | NVIDIA GPUs для AI |
-| **Backup Systems** | $10,000 | Backup appliance |
-| **Contingency (20%)** | $43,000 | Unexpected expenses |
-| **Total CapEx** | **$258,000** | |
-
-**Operational Expenditure (OpEx - Year 1):**
-
-| Category | Cost | Notes |
-|----------|------|-------|
-| **Software Licenses** | $20,000 | Portainer, monitoring tools |
-| **Training** | $25,000 | External training, materials |
-| **Consulting** | $25,000 | Penetration testing, consultants |
-| **Internal Resources** | $180,000 | 30 PM * $6k/PM |
-| **Misc** | $10,000 | Travel, documentation, etc. |
-| **Total OpEx (Year 1)** | **$260,000** | |
-
-**Total Implementation Cost:** $518,000
-
-### 6.2 Ongoing Costs (Annual)
-
-| Category | Annual Cost |
-|----------|-------------|
-| Software licenses | $20,000 |
-| Maintenance & support | $30,000 |
-| Training (ongoing) | $10,000 |
-| Infrastructure costs (power, cooling) | $15,000 |
-| **Total Ongoing** | **$75,000/year** |
-
-### 6.3 Expected Benefits (Annual)
-
-**Quantifiable Benefits:**
-
-| Benefit | Annual Savings | Calculation |
-|---------|----------------|-------------|
-| **Reduced Downtime** | $200,000 | Fewer incidents, faster recovery |
-| **Team Productivity** | $150,000 | 40% time savings on deployment tasks |
-| **Faster Time to Market** | $100,000 | Competitive advantage, revenue |
-| **Reduced Infrastructure** | $30,000 | Better utilization, fewer servers needed |
-| **Total Annual Benefits** | **$480,000** | |
-
-**Intangible Benefits:**
-- Improved security posture
-- Better compliance (avoid penalties)
-- Higher team morale
-- Attract/retain talent (modern stack)
-- Competitive advantage
-
-### 6.4 ROI Calculation
-
-```
-Total Investment: $518,000 (Year 0)
-Annual Benefit: $480,000
-Annual Cost: $75,000
-Net Annual Benefit: $405,000
-
-ROI Timeline:
-- Year 0: -$518,000
-- Year 1: -$518,000 + $405,000 = -$113,000
-- Year 2: -$113,000 + $405,000 = +$292,000
-- Year 3: +$697,000
-- Year 4: +$1,102,000
-- Year 5: +$1,507,000
-
-Payback Period: ~15 months
-5-Year ROI: 191%
-```
-
-**Sensitivity Analysis:**
-
-**Conservative (70% benefits):**
-- Net benefit: $284k/year
-- Payback: 22 months
-
-**Aggressive (130% benefits):**
-- Net benefit: $527k/year
-- Payback: 12 months
-
----
-
-## 7. Success Metrics
-
-### 7.1 DORA Metrics (Key Performance Indicators)
-
-**Deployment Frequency:**
-- Baseline: 1-2 deployments/month
-- Target Year 1: 5 deployments/week
-- Target Year 2: 10+ deployments/day
-
-**Lead Time for Changes:**
-- Baseline: 2-4 weeks
-- Target Year 1: 1 day
-- Target Year 2: <4 hours
-
-**Mean Time to Recovery (MTTR):**
-- Baseline: 2-4 hours
-- Target Year 1: 30 minutes
-- Target Year 2: <15 minutes
-
-**Change Failure Rate:**
-- Baseline: 20-30%
-- Target Year 1: 10%
-- Target Year 2: <5%
-
-### 7.2 Business Metrics
-
-**Cost Savings:**
-- Infrastructure utilization improvement: +30%
-- Operational cost reduction: -$200k/year
-- Productivity improvement: +40% for DevOps team
-
-**Quality Metrics:**
-- Incidents in production: -60%
-- Mean time between failures: +200%
-- Customer satisfaction: +20%
-
-**Compliance Metrics:**
-- Audit findings: -80%
-- Compliance report generation time: -90%
-- Audit trail completeness: 100%
-
-### 7.3 Team Metrics
-
-**Adoption:**
-- Applications migrated to GitOps: Target 80% within 6 months
-- Active users: 100% of DevOps, 80% of developers
-- AI assistant usage: 50+ queries/week
-
-**Satisfaction:**
-- Team satisfaction survey: Target >4.5/5
-- Would recommend to colleague: Target >90%
-- Reduction в deployment stress: Target >50%
-
----
-
-## 8. Communication Plan
-
-### 8.1 Stakeholder Communication
-
-**Executive Leadership:**
-- **Frequency:** Monthly
-- **Format:** Executive dashboard, brief report
-- **Content:** Progress, budget, risks, key decisions
-- **Owner:** Project Manager
-
-**Project Steering Committee:**
-- **Frequency:** Bi-weekly
-- **Format:** Steering committee meeting
-- **Content:** Detailed progress, risks, decisions needed
-- **Owner:** Project Manager
-
-**All Employees:**
-- **Frequency:** Monthly
-- **Format:** Company-wide email, demo sessions
-- **Content:** Project overview, benefits, what's coming
-- **Owner:** Project Manager + Comms team
-
-### 8.2 Team Communication
-
-**Project Team:**
-- **Daily standup:** 15 min, progress & blockers
-- **Weekly planning:** 1 hour, next week's work
-- **Retrospective:** Bi-weekly, lessons learned
-
-**Development Teams:**
-- **Migration briefings:** Before each batch migration
-- **Office hours:** Weekly Q&A sessions
-- **Slack channel:** Real-time support
-
-**Operations Team:**
-- **Operational readiness:** Weekly meetings during rollout
-- **Handover sessions:** Detailed knowledge transfer
-- **Run книги:** Comprehensive documentation
-
-### 8.3 Change Management
-
-**Communication Themes:**
-- Why are we doing this? (Benefits)
-- What does it mean for me? (Impact)
-- When will it happen? (Timeline)
-- How can I prepare? (Training)
-- Who can I ask? (Support)
-
-**Resistance Management:**
-- Listen к concerns
-- Address FUD (Fear, Uncertainty, Doubt)
-- Show early wins
-- Provide support
-- Celebrate successes
-
----
-
-## 9. Go/No-Go Decision Points
-
-### 9.1 Milestone Gates
-
-**Gate 1: Development Environment Complete (Week 5)**
-
-**Go Criteria:**
-- All services operational
-- Integration tests passing
-- Team trained
-- Security review passed
-
-**No-Go Actions:**
-- Extend dev environment phase
-- Address critical issues
-- Re-plan production timeline
-
-**Gate 2: Production Environment Ready (Week 16)**
-
-**Go Criteria:**
-- Production environment operational
-- HA configured and tested
-- Security audit passed
-- Compliance sign-off received
-- Disaster recovery tested
-
-**No-Go Actions:**
-- Address critical security findings
-- Complete remaining configuration
-- Delay pilot migration
-
-**Gate 3: Pilot Success (Week 18)**
-
-**Go Criteria:**
-- Pilot applications successfully migrated
-- No critical incidents
-- Team comfortable with process
-- Positive feedback
-
-**No-Go Actions:**
-- Refine migration process
-- Additional training
-- Delay gradual migration
-
-**Gate 4: Full Rollout (Week 22)**
-
-**Go Criteria:**
-- Majority of apps migrated
-- Metrics showing improvement
-- Teams satisfied
-- Stable operations
-
-**No-Go Actions:**
-- Slow down migration pace
-- Address outstanding issues
-- Extended stabilization period
-
----
-
-## 10. Post-Implementation
-
-### 10.1 Handover to Operations
-
-**Knowledge Transfer:**
-- Comprehensive runbooks
-- Architecture walkthrough
-- Troubleshooting guide
-- Escalation procedures
-
-**Operational Ownership:**
-- SRE team takes ownership
-- On-call rotation established
-- Incident management process
-- Continuous improvement backlog
-
-### 10.2 Continuous Improvement
-
-**Regular Activities:**
-- Monthly metrics review
-- Quarterly retrospectives
-- Annual architecture review
-- Ongoing optimization
-
-**Areas для Improvement:**
-- Performance tuning
-- Cost optimization
-- Security hardening
-- Feature enhancements
-- Team skill development
-
-### 10.3 Project Closure
-
-**Final Activities:**
-- Post-implementation review
-- Lessons learned documentation
-- Final cost accounting
-- Benefits realization tracking setup
-- Team recognition
-- Knowledge transfer complete
-- Project documentation archived
-
-**Success Celebration:**
-- Team dinner
-- Recognition awards
-- Company-wide announcement
-- Case study creation (internal)
-
----
-
-**Final Approval:**
-
-| Role | Name | Signature | Date |
-|------|------|-----------|------|
-| Project Sponsor | _______________ | _______________ | _____ |
-| CTO | _______________ | _______________ | _____ |
-| CISO | _______________ | _______________ | _____ |
-| CFO | _______________ | _______________ | _____ |
-| Compliance Officer | _______________ | _______________ | _____ |
\ No newline at end of file