diff --git a/.DS_Store b/.DS_Store index a12667f3..65b99dcb 100644 Binary files a/.DS_Store and b/.DS_Store differ diff --git a/Hermes/yunzhi/技术笔记/django-tenants 完整配置指南.md b/Hermes/yunzhi/技术笔记/django-tenants 完整配置指南.md new file mode 100644 index 00000000..192cacb9 --- /dev/null +++ b/Hermes/yunzhi/技术笔记/django-tenants 完整配置指南.md @@ -0,0 +1,222 @@ +--- +title: django-tenants 完整配置指南 +created: 2026-04-21 +tags: [django, django-tenants, postgresql, saas, multi-tenant] +category: 技术笔记 +--- + +# django-tenants 完整配置指南 + +## 一、安装依赖 + +pip install django-tenants psycopg2-binary django-jazzmin + +## 二、项目目录结构 + +myproject/ +├── config/ +│ ├── settings/ +│ │ ├── base.py +│ │ ├── development.py +│ │ └── production.py +│ ├── urls.py +│ └── wsgi.py +├── apps/ +│ ├── tenants/ +│ ├── subscription/ +│ ├── accounts/ +│ ├── listings/ +│ ├── clients/ +│ └── showings/ +├── manage.py +└── requirements.txt + +## 三、核心 Model：租户与域名 + +- Company 继承 TenantMixin +- Domain 继承 DomainMixin +- 每一个中介公司 = 一个租户 = 一个独立 PostgreSQL Schema +- 每个公司可绑定多个域名/子域名 + +## 四、Settings 完整配置 + +关键点： +- SHARED_APPS 放公共 Schema 应用 +- TENANT_APPS 放租户私有应用 +- TENANT_MODEL = "tenants.Company" +- TENANT_DOMAIN_MODEL = "tenants.Domain" +- DATABASES 使用 django_tenants.postgresql_backend +- DATABASE_ROUTERS 使用 TenantSyncRouter +- TenantMainMiddleware 必须第一个 +- ROOT_URLCONF / PUBLIC_SCHEMA_URLCONF 分离 +- AUTH_USER_MODEL = accounts.User + +## 五、URL 路由拆分 + +- config/urls_public.py：公共域名、官网、注册、登录、超级管理后台 +- config/urls_tenant.py：租户子域名、租户后台、房源/客源/带看/员工模块 + +## 六、自定义 User Model（跨租户关键） + +- User 继承 AbstractUser +- role 支持平台超管、公司管理员、门店经理、资深经纪人、经纪人、实习经纪人 +- Branch 作为门店模型 + +## 七、初始化与常用命令 + +- createdb realestate_saas +- python manage.py migrate_schemas --shared +- python manage.py createsuperuser +- python manage.py shell 创建 Company 与 Domain + +示例： +- schema_name = zuoan +- domain = zuoan.localhost +- 访问 http://zuoan.localhost:8000/admin/ 进入专属后台 + +## 八、本地开发配置（hosts 文件） + +- 127.0.0.1 localhost +- 127.0.0.1 zuoan.localhost +- 127.0.0.1 lianhe.localhost +- 127.0.0.1 xincheng.localhost + +开发环境要点： +- ALLOWED_HOSTS 包含 .localhost +- 本地不用 HTTPS + +## 九、数据隔离验证 + +使用 schema_context 切换 schema，验证 Listing 等数据互相隔离。 + +## 下一步建议 + +推荐顺序： +1. 先做房源/客源/带看完整数据模型 +2. 再做 Django Admin 深度定制（Jazzmin 主题） +3. 最后补三级权限体系（总部/门店/经纪人） + + +--- + +# 上海房产中介 SaaS 系统规划 + +## 一、多租户架构选型 + +Django 多租户有三种主流方案，针对这个场景推荐独立 Schema 方案，也就是基于 PostgreSQL Schema 隔离的 django-tenants。 + +| 方案 | 原理 | 优点 | 缺点 | 适用场景 | +|---|---|---|---|---| +| 共享 Schema | 每张表加 tenant_id 字段 | 简单，运维成本低 | 数据隔离风险高 | 小规模、低安全需求 | +| 独立 Schema | PostgreSQL Schema 隔离 | 隔离好，性能佳 | 稍复杂 | 中介 SaaS，推荐 | +| 独立数据库 | 每租户独立 DB | 最高隔离 | 运维成本极高 | 超高安全需求 | + +推荐使用 django-tenants： + +pip install django-tenants + +## 二、整体系统模块规划 + +SaaS 平台层： +- 租户注册 +- 套餐管理 +- 计费 +- 超级后台 + +各中介公司 Tenant： +- 房源管理 +- 客源管理 +- 员工 / 权限管理 +- 带看管理 +- 合同管理 +- 报表 / BI 看板 +- 渠道推广 +- 财务佣金 +- 消息 / 通知中心 + +核心 Django App 拆分： +- tenants：租户管理（公共 Schema） +- accounts：用户 / 员工 / 角色权限 +- listings：房源管理（核心） +- clients：客源 / 客户跟进 +- showings：带看记录 +- contracts：合同管理 +- commissions：佣金 / 财务 +- reports：数据报表 +- notifications：消息通知 +- subscription：套餐订阅（公共 Schema） + +## 三、房源模块数据模型（核心） + +Listing 关键字段包括： +- 基础信息：title、listing_type、status +- 上海地址结构：district、street、community、building、floor、unit +- 房屋属性：area、inner_area、layout、orientation、decoration、floor_total +- 价格：price、price_unit +- 归属：agent、source、exclusive +- 证件：certificate_no +- 时间：created_at、updated_at + +## 四、技术栈推荐 + +后端： +- Django 5.x + DRF +- django-tenants +- django-guardian +- celery + redis +- django-filter +- PostgreSQL 15+ + +前端路径： +- 路径 A：Django Admin + 定制，最快上手，适合 MVP +- 路径 B：HTMX + Alpine.js + Tailwind，推荐中期方案 +- 路径 C：Vue3 / React + DRF，长期推荐 + +建议：先 A，再 B，最后 C。 + +## 五、租户路由设计 + +通过子域名区分租户： +- company-a.yourapp.com +- company-b.yourapp.com +- admin.yourapp.com + +核心设置： +- TENANT_MODEL = "tenants.Company" +- TENANT_DOMAIN_MODEL = "tenants.Domain" +- SHARED_APPS 放公共应用 +- TENANT_APPS 放租户私有应用 + +## 六、开发阶段规划 + +Phase 1（1-2 月）MVP： +- 租户注册 / 登录 +- 房源 CRUD + 图片上传 +- 客源基础管理 +- Django Admin 后台 + +Phase 2（2-3 月）核心业务： +- 带看流程 +- 合同模板 + 生成 +- 员工角色权限 +- 基础报表 + +Phase 3（3-4 月）增长功能： +- 佣金结算 +- 渠道推广（链家 / 安居客对接） +- 微信小程序端 +- BI 数据看板 + +Phase 4 商业化： +- 套餐 / 计费系统 +- 多城市扩展 + +## 七、优先推进建议 + +如果要最快落地，建议优先顺序： +1. django-tenants 完整配置 +2. 房源 / 客源 / 带看数据模型 +3. Django Admin 深度定制 +4. 权限系统设计 +5. 前端升级到 HTMX 或 Vue + diff --git a/Hermes/yunzhi/技术笔记/django-tenants 完整配置指南.md.bak.2026-04-21-184051 b/Hermes/yunzhi/技术笔记/django-tenants 完整配置指南.md.bak.2026-04-21-184051 new file mode 100644 index 00000000..6d28bc1b --- /dev/null +++ b/Hermes/yunzhi/技术笔记/django-tenants 完整配置指南.md.bak.2026-04-21-184051 @@ -0,0 +1,98 @@ +--- +title: django-tenants 完整配置指南 +created: 2026-04-21 +tags: [django, django-tenants, postgresql, saas, multi-tenant] +category: 技术笔记 +--- + +# django-tenants 完整配置指南 + +## 一、安装依赖 + +pip install django-tenants psycopg2-binary django-jazzmin + +## 二、项目目录结构 + +myproject/ +├── config/ +│ ├── settings/ +│ │ ├── base.py +│ │ ├── development.py +│ │ └── production.py +│ ├── urls.py +│ └── wsgi.py +├── apps/ +│ ├── tenants/ +│ ├── subscription/ +│ ├── accounts/ +│ ├── listings/ +│ ├── clients/ +│ └── showings/ +├── manage.py +└── requirements.txt + +## 三、核心 Model：租户与域名 + +- Company 继承 TenantMixin +- Domain 继承 DomainMixin +- 每一个中介公司 = 一个租户 = 一个独立 PostgreSQL Schema +- 每个公司可绑定多个域名/子域名 + +## 四、Settings 完整配置 + +关键点： +- SHARED_APPS 放公共 Schema 应用 +- TENANT_APPS 放租户私有应用 +- TENANT_MODEL = "tenants.Company" +- TENANT_DOMAIN_MODEL = "tenants.Domain" +- DATABASES 使用 django_tenants.postgresql_backend +- DATABASE_ROUTERS 使用 TenantSyncRouter +- TenantMainMiddleware 必须第一个 +- ROOT_URLCONF / PUBLIC_SCHEMA_URLCONF 分离 +- AUTH_USER_MODEL = accounts.User + +## 五、URL 路由拆分 + +- config/urls_public.py：公共域名、官网、注册、登录、超级管理后台 +- config/urls_tenant.py：租户子域名、租户后台、房源/客源/带看/员工模块 + +## 六、自定义 User Model（跨租户关键） + +- User 继承 AbstractUser +- role 支持平台超管、公司管理员、门店经理、资深经纪人、经纪人、实习经纪人 +- Branch 作为门店模型 + +## 七、初始化与常用命令 + +- createdb realestate_saas +- python manage.py migrate_schemas --shared +- python manage.py createsuperuser +- python manage.py shell 创建 Company 与 Domain + +示例： +- schema_name = zuoan +- domain = zuoan.localhost +- 访问 http://zuoan.localhost:8000/admin/ 进入专属后台 + +## 八、本地开发配置（hosts 文件） + +- 127.0.0.1 localhost +- 127.0.0.1 zuoan.localhost +- 127.0.0.1 lianhe.localhost +- 127.0.0.1 xincheng.localhost + +开发环境要点： +- ALLOWED_HOSTS 包含 .localhost +- 本地不用 HTTPS + +## 九、数据隔离验证 + +使用 schema_context 切换 schema，验证 Listing 等数据互相隔离。 + +## 下一步建议 + +推荐顺序： +1. 先做房源/客源/带看完整数据模型 +2. 再做 Django Admin 深度定制（Jazzmin 主题） +3. 最后补三级权限体系（总部/门店/经纪人） + diff --git a/raw/Agent/agency-agents/README.md b/raw/Agent/agency-agents/README.md deleted file mode 100644 index 2dfcf361..00000000 --- a/raw/Agent/agency-agents/README.md +++ /dev/null @@ -1,920 +0,0 @@ -# 🎭 The Agency: AI Specialists Ready to Transform Your Workflow - -> **A complete AI agency at your fingertips** - From frontend wizards to Reddit community ninjas, from whimsy injectors to reality checkers. Each agent is a specialized expert with personality, processes, and proven deliverables. - -[![GitHub stars](https://img.shields.io/github/stars/msitarzewski/agency-agents?style=social)](https://github.com/msitarzewski/agency-agents) -[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) -[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://makeapullrequest.com) -[![Sponsor](https://img.shields.io/badge/Sponsor-%E2%9D%A4-pink?logo=github)](https://github.com/sponsors/msitarzewski) - ---- - -## 🚀 What Is This? - -Born from a Reddit thread and months of iteration, **The Agency** is a growing collection of meticulously crafted AI agent personalities. Each agent is: - -- **🎯 Specialized**: Deep expertise in their domain (not generic prompt templates) -- **🧠 Personality-Driven**: Unique voice, communication style, and approach -- **📋 Deliverable-Focused**: Real code, processes, and measurable outcomes -- **✅ Production-Ready**: Battle-tested workflows and success metrics - -**Think of it as**: Assembling your dream team, except they're AI specialists who never sleep, never complain, and always deliver. - ---- - -## ⚡ Quick Start - -### Option 1: Use with Claude Code (Recommended) - -```bash -# Install all agents to your Claude Code directory -./scripts/install.sh --tool claude-code - -# Or manually copy a category if you only want one division -cp engineering/*.md ~/.claude/agents/ - -# Then activate any agent in your Claude Code sessions: -# "Hey Claude, activate Frontend Developer mode and help me build a React component" -``` - -### Option 2: Use as Reference - -Each agent file contains: -- Identity & personality traits -- Core mission & workflows -- Technical deliverables with code examples -- Success metrics & communication style - -Browse the agents below and copy/adapt the ones you need! - -### Option 3: Use with Other Tools (GitHub Copilot, Antigravity, Gemini CLI, OpenCode, OpenClaw, Cursor, Aider, Windsurf, Kimi Code) - -```bash -# Step 1 -- generate integration files for all supported tools -./scripts/convert.sh - -# Step 2 -- install interactively (auto-detects what you have installed) -./scripts/install.sh - -# Or target a specific tool directly -./scripts/install.sh --tool antigravity -./scripts/install.sh --tool gemini-cli -./scripts/install.sh --tool opencode -./scripts/install.sh --tool copilot -./scripts/install.sh --tool openclaw -./scripts/install.sh --tool cursor -./scripts/install.sh --tool aider -./scripts/install.sh --tool windsurf -./scripts/install.sh --tool kimi -``` - -See the [Multi-Tool Integrations](#-multi-tool-integrations) section below for full details. - ---- - -## 🎨 The Agency Roster - -### 💻 Engineering Division - -Building the future, one commit at a time. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎨 [Frontend Developer](engineering/engineering-frontend-developer.md) | React/Vue/Angular, UI implementation, performance | Modern web apps, pixel-perfect UIs, Core Web Vitals optimization | -| 🏗️ [Backend Architect](engineering/engineering-backend-architect.md) | API design, database architecture, scalability | Server-side systems, microservices, cloud infrastructure | -| 📱 [Mobile App Builder](engineering/engineering-mobile-app-builder.md) | iOS/Android, React Native, Flutter | Native and cross-platform mobile applications | -| 🤖 [AI Engineer](engineering/engineering-ai-engineer.md) | ML models, deployment, AI integration | Machine learning features, data pipelines, AI-powered apps | -| 🚀 [DevOps Automator](engineering/engineering-devops-automator.md) | CI/CD, infrastructure automation, cloud ops | Pipeline development, deployment automation, monitoring | -| ⚡ [Rapid Prototyper](engineering/engineering-rapid-prototyper.md) | Fast POC development, MVPs | Quick proof-of-concepts, hackathon projects, fast iteration | -| 💎 [Senior Developer](engineering/engineering-senior-developer.md) | Laravel/Livewire, advanced patterns | Complex implementations, architecture decisions | -| 🔧 [Filament Optimization Specialist](engineering/engineering-filament-optimization-specialist.md) | Filament PHP admin UX, structural form redesign, resource optimization | Restructuring Filament resources/forms/tables for faster, cleaner admin workflows | -| 🔒 [Security Engineer](engineering/engineering-security-engineer.md) | Threat modeling, secure code review, security architecture | Application security, vulnerability assessment, security CI/CD | -| ⚡ [Autonomous Optimization Architect](engineering/engineering-autonomous-optimization-architect.md) | LLM routing, cost optimization, shadow testing | Autonomous systems needing intelligent API selection and cost guardrails | -| 🔩 [Embedded Firmware Engineer](engineering/engineering-embedded-firmware-engineer.md) | Bare-metal, RTOS, ESP32/STM32/Nordic firmware | Production-grade embedded systems and IoT devices | -| 🚨 [Incident Response Commander](engineering/engineering-incident-response-commander.md) | Incident management, post-mortems, on-call | Managing production incidents and building incident readiness | -| ⛓️ [Solidity Smart Contract Engineer](engineering/engineering-solidity-smart-contract-engineer.md) | EVM contracts, gas optimization, DeFi | Secure, gas-optimized smart contracts and DeFi protocols | -| 🧭 [Codebase Onboarding Engineer](engineering/engineering-codebase-onboarding-engineer.md) | Fast developer onboarding, read-only codebase exploration, factual explanation | Helping new developers understand unfamiliar repos quickly by reading the code, tracing code paths, and stating facts about structure and behavior | -| 📚 [Technical Writer](engineering/engineering-technical-writer.md) | Developer docs, API reference, tutorials | Clear, accurate technical documentation | -| 🎯 [Threat Detection Engineer](engineering/engineering-threat-detection-engineer.md) | SIEM rules, threat hunting, ATT&CK mapping | Building detection layers and threat hunting | -| 💬 [WeChat Mini Program Developer](engineering/engineering-wechat-mini-program-developer.md) | WeChat ecosystem, Mini Programs, payment integration | Building performant apps for the WeChat ecosystem | -| 👁️ [Code Reviewer](engineering/engineering-code-reviewer.md) | Constructive code review, security, maintainability | PR reviews, code quality gates, mentoring through review | -| 🗄️ [Database Optimizer](engineering/engineering-database-optimizer.md) | Schema design, query optimization, indexing strategies | PostgreSQL/MySQL tuning, slow query debugging, migration planning | -| 🌿 [Git Workflow Master](engineering/engineering-git-workflow-master.md) | Branching strategies, conventional commits, advanced Git | Git workflow design, history cleanup, CI-friendly branch management | -| 🏛️ [Software Architect](engineering/engineering-software-architect.md) | System design, DDD, architectural patterns, trade-off analysis | Architecture decisions, domain modeling, system evolution strategy | -| 🛡️ [SRE](engineering/engineering-sre.md) | SLOs, error budgets, observability, chaos engineering | Production reliability, toil reduction, capacity planning | -| 🧬 [AI Data Remediation Engineer](engineering/engineering-ai-data-remediation-engineer.md) | Self-healing pipelines, air-gapped SLMs, semantic clustering | Fixing broken data at scale with zero data loss | -| 🔧 [Data Engineer](engineering/engineering-data-engineer.md) | Data pipelines, lakehouse architecture, ETL/ELT | Building reliable data infrastructure and warehousing | -| 🔗 [Feishu Integration Developer](engineering/engineering-feishu-integration-developer.md) | Feishu/Lark Open Platform, bots, workflows | Building integrations for the Feishu ecosystem | -| 🧱 [CMS Developer](engineering/engineering-cms-developer.md) | WordPress & Drupal themes, plugins/modules, content architecture | Code-first CMS implementation and customization | -| 📧 [Email Intelligence Engineer](engineering/engineering-email-intelligence-engineer.md) | Email parsing, MIME extraction, structured data for AI agents | Turning raw email threads into reasoning-ready context | -| 🎙️ [Voice AI Integration Engineer](engineering/engineering-voice-ai-integration-engineer.md) | Speech-to-text pipelines, Whisper, ASR, speaker diarization | End-to-end transcription pipelines, audio preprocessing, structured transcript delivery | - -### 🎨 Design Division - -Making it beautiful, usable, and delightful. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎯 [UI Designer](design/design-ui-designer.md) | Visual design, component libraries, design systems | Interface creation, brand consistency, component design | -| 🔍 [UX Researcher](design/design-ux-researcher.md) | User testing, behavior analysis, research | Understanding users, usability testing, design insights | -| 🏛️ [UX Architect](design/design-ux-architect.md) | Technical architecture, CSS systems, implementation | Developer-friendly foundations, implementation guidance | -| 🎭 [Brand Guardian](design/design-brand-guardian.md) | Brand identity, consistency, positioning | Brand strategy, identity development, guidelines | -| 📖 [Visual Storyteller](design/design-visual-storyteller.md) | Visual narratives, multimedia content | Compelling visual stories, brand storytelling | -| ✨ [Whimsy Injector](design/design-whimsy-injector.md) | Personality, delight, playful interactions | Adding joy, micro-interactions, Easter eggs, brand personality | -| 📷 [Image Prompt Engineer](design/design-image-prompt-engineer.md) | AI image generation prompts, photography | Photography prompts for Midjourney, DALL-E, Stable Diffusion | -| 🌈 [Inclusive Visuals Specialist](design/design-inclusive-visuals-specialist.md) | Representation, bias mitigation, authentic imagery | Generating culturally accurate AI images and video | - -### 💰 Paid Media Division - -Turning ad spend into measurable business outcomes. - -| Agent | Specialty | When to Use | -| --- | --- | --- | -| 💰 [PPC Campaign Strategist](paid-media/paid-media-ppc-strategist.md) | Google/Microsoft/Amazon Ads, account architecture, bidding | Account buildouts, budget allocation, scaling, performance diagnosis | -| 🔍 [Search Query Analyst](paid-media/paid-media-search-query-analyst.md) | Search term analysis, negative keywords, intent mapping | Query audits, wasted spend elimination, keyword discovery | -| 📋 [Paid Media Auditor](paid-media/paid-media-auditor.md) | 200+ point account audits, competitive analysis | Account takeovers, quarterly reviews, competitive pitches | -| 📡 [Tracking & Measurement Specialist](paid-media/paid-media-tracking-specialist.md) | GTM, GA4, conversion tracking, CAPI | New implementations, tracking audits, platform migrations | -| ✍️ [Ad Creative Strategist](paid-media/paid-media-creative-strategist.md) | RSA copy, Meta creative, Performance Max assets | Creative launches, testing programs, ad fatigue refreshes | -| 📺 [Programmatic & Display Buyer](paid-media/paid-media-programmatic-buyer.md) | GDN, DSPs, partner media, ABM display | Display planning, partner outreach, ABM programs | -| 📱 [Paid Social Strategist](paid-media/paid-media-paid-social-strategist.md) | Meta, LinkedIn, TikTok, cross-platform social | Social ad programs, platform selection, audience strategy | - -### 💼 Sales Division - -Turning pipeline into revenue through craft, not CRM busywork. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎯 [Outbound Strategist](sales/sales-outbound-strategist.md) | Signal-based prospecting, multi-channel sequences, ICP targeting | Building pipeline through research-driven outreach, not volume | -| 🔍 [Discovery Coach](sales/sales-discovery-coach.md) | SPIN, Gap Selling, Sandler — question design and call structure | Preparing for discovery calls, qualifying opportunities, coaching reps | -| ♟️ [Deal Strategist](sales/sales-deal-strategist.md) | MEDDPICC qualification, competitive positioning, win planning | Scoring deals, exposing pipeline risk, building win strategies | -| 🛠️ [Sales Engineer](sales/sales-engineer.md) | Technical demos, POC scoping, competitive battlecards | Pre-sales technical wins, demo prep, competitive positioning | -| 🏹 [Proposal Strategist](sales/sales-proposal-strategist.md) | RFP response, win themes, narrative structure | Writing proposals that persuade, not just comply | -| 📊 [Pipeline Analyst](sales/sales-pipeline-analyst.md) | Forecasting, pipeline health, deal velocity, RevOps | Pipeline reviews, forecast accuracy, revenue operations | -| 🗺️ [Account Strategist](sales/sales-account-strategist.md) | Land-and-expand, QBRs, stakeholder mapping | Post-sale expansion, account planning, NRR growth | -| 🏋️ [Sales Coach](sales/sales-coach.md) | Rep development, call coaching, pipeline review facilitation | Making every rep and every deal better through structured coaching | -| 🎯 [Sales Outreach](specialized/sales-outreach.md) | Cold prospecting, multi-touch cadences, objection handling, proposals | Top-of-funnel B2B outreach — from cold email to booked discovery call | - -### 📢 Marketing Division - -Growing your audience, one authentic interaction at a time. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🚀 [Growth Hacker](marketing/marketing-growth-hacker.md) | Rapid user acquisition, viral loops, experiments | Explosive growth, user acquisition, conversion optimization | -| 📝 [Content Creator](marketing/marketing-content-creator.md) | Multi-platform content, editorial calendars | Content strategy, copywriting, brand storytelling | -| 🐦 [Twitter Engager](marketing/marketing-twitter-engager.md) | Real-time engagement, thought leadership | Twitter strategy, LinkedIn campaigns, professional social | -| 📱 [TikTok Strategist](marketing/marketing-tiktok-strategist.md) | Viral content, algorithm optimization | TikTok growth, viral content, Gen Z/Millennial audience | -| 📸 [Instagram Curator](marketing/marketing-instagram-curator.md) | Visual storytelling, community building | Instagram strategy, aesthetic development, visual content | -| 🤝 [Reddit Community Builder](marketing/marketing-reddit-community-builder.md) | Authentic engagement, value-driven content | Reddit strategy, community trust, authentic marketing | -| 📱 [App Store Optimizer](marketing/marketing-app-store-optimizer.md) | ASO, conversion optimization, discoverability | App marketing, store optimization, app growth | -| 🌐 [Social Media Strategist](marketing/marketing-social-media-strategist.md) | Cross-platform strategy, campaigns | Overall social strategy, multi-platform campaigns | -| 📕 [Xiaohongshu Specialist](marketing/marketing-xiaohongshu-specialist.md) | Lifestyle content, trend-driven strategy | Xiaohongshu growth, aesthetic storytelling, Gen Z audience | -| 💬 [WeChat Official Account Manager](marketing/marketing-wechat-official-account.md) | Subscriber engagement, content marketing | WeChat OA strategy, community building, conversion optimization | -| 🧠 [Zhihu Strategist](marketing/marketing-zhihu-strategist.md) | Thought leadership, knowledge-driven engagement | Zhihu authority building, Q&A strategy, lead generation | -| 🇨🇳 [Baidu SEO Specialist](marketing/marketing-baidu-seo-specialist.md) | Baidu optimization, China SEO, ICP compliance | Ranking in Baidu and reaching China's search market | -| 🎬 [Bilibili Content Strategist](marketing/marketing-bilibili-content-strategist.md) | B站 algorithm, danmaku culture, UP主 growth | Building audiences on Bilibili with community-first content | -| 🎠 [Carousel Growth Engine](marketing/marketing-carousel-growth-engine.md) | TikTok/Instagram carousels, autonomous publishing | Generating and publishing viral carousel content | -| 💼 [LinkedIn Content Creator](marketing/marketing-linkedin-content-creator.md) | Personal branding, thought leadership, professional content | LinkedIn growth, professional audience building, B2B content | -| 🛒 [China E-Commerce Operator](marketing/marketing-china-ecommerce-operator.md) | Taobao, Tmall, Pinduoduo, live commerce | Running multi-platform e-commerce in China | -| 🎥 [Kuaishou Strategist](marketing/marketing-kuaishou-strategist.md) | Kuaishou, 老铁 community, grassroots growth | Building authentic audiences in lower-tier markets | -| 🔍 [SEO Specialist](marketing/marketing-seo-specialist.md) | Technical SEO, content strategy, link building | Driving sustainable organic search growth | -| 📘 [Book Co-Author](marketing/marketing-book-co-author.md) | Thought-leadership books, ghostwriting, publishing | Strategic book collaboration for founders and experts | -| 🌏 [Cross-Border E-Commerce Specialist](marketing/marketing-cross-border-ecommerce.md) | Amazon, Shopee, Lazada, cross-border fulfillment | Full-funnel cross-border e-commerce strategy | -| 🎵 [Douyin Strategist](marketing/marketing-douyin-strategist.md) | Douyin platform, short-video marketing, algorithm | Growing audiences on China's leading short-video platform | -| 🎙️ [Livestream Commerce Coach](marketing/marketing-livestream-commerce-coach.md) | Host training, live room optimization, conversion | Building high-performing livestream e-commerce operations | -| 🎧 [Podcast Strategist](marketing/marketing-podcast-strategist.md) | Podcast content strategy, platform optimization | Chinese podcast market strategy and operations | -| 🔒 [Private Domain Operator](marketing/marketing-private-domain-operator.md) | WeCom, private traffic, community operations | Building enterprise WeChat private domain ecosystems | -| 🎬 [Short-Video Editing Coach](marketing/marketing-short-video-editing-coach.md) | Post-production, editing workflows, platform specs | Hands-on short-video editing training and optimization | -| 🔥 [Weibo Strategist](marketing/marketing-weibo-strategist.md) | Sina Weibo, trending topics, fan engagement | Full-spectrum Weibo operations and growth | -| 🔮 [AI Citation Strategist](marketing/marketing-ai-citation-strategist.md) | AEO/GEO, AI recommendation visibility, citation auditing | Improving brand visibility across ChatGPT, Claude, Gemini, Perplexity | -| 🇨🇳 [China Market Localization Strategist](marketing/marketing-china-market-localization-strategist.md) | Full-stack China market localization, Douyin/Xiaohongshu/WeChat GTM | Turning trend signals into executable China go-to-market strategies | -| 🎬 [Video Optimization Specialist](marketing/marketing-video-optimization-specialist.md) | YouTube algorithm strategy, chaptering, thumbnail concepts | YouTube channel growth, video SEO, audience retention optimization | - -### 📊 Product Division - -Building the right thing at the right time. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎯 [Sprint Prioritizer](product/product-sprint-prioritizer.md) | Agile planning, feature prioritization | Sprint planning, resource allocation, backlog management | -| 🔍 [Trend Researcher](product/product-trend-researcher.md) | Market intelligence, competitive analysis | Market research, opportunity assessment, trend identification | -| 💬 [Feedback Synthesizer](product/product-feedback-synthesizer.md) | User feedback analysis, insights extraction | Feedback analysis, user insights, product priorities | -| 🧠 [Behavioral Nudge Engine](product/product-behavioral-nudge-engine.md) | Behavioral psychology, nudge design, engagement | Maximizing user motivation through behavioral science | -| 🧭 [Product Manager](product/product-manager.md) | Full lifecycle product ownership | Discovery, PRDs, roadmap planning, GTM, outcome measurement | - -### 🎬 Project Management Division - -Keeping the trains running on time (and under budget). - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎬 [Studio Producer](project-management/project-management-studio-producer.md) | High-level orchestration, portfolio management | Multi-project oversight, strategic alignment, resource allocation | -| 🐑 [Project Shepherd](project-management/project-management-project-shepherd.md) | Cross-functional coordination, timeline management | End-to-end project coordination, stakeholder management | -| ⚙️ [Studio Operations](project-management/project-management-studio-operations.md) | Day-to-day efficiency, process optimization | Operational excellence, team support, productivity | -| 🧪 [Experiment Tracker](project-management/project-management-experiment-tracker.md) | A/B tests, hypothesis validation | Experiment management, data-driven decisions, testing | -| 👔 [Senior Project Manager](project-management/project-manager-senior.md) | Realistic scoping, task conversion | Converting specs to tasks, scope management | -| 📋 [Jira Workflow Steward](project-management/project-management-jira-workflow-steward.md) | Git workflow, branch strategy, traceability | Enforcing Jira-linked Git discipline and delivery | - -### 🧪 Testing Division - -Breaking things so users don't have to. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 📸 [Evidence Collector](testing/testing-evidence-collector.md) | Screenshot-based QA, visual proof | UI testing, visual verification, bug documentation | -| 🔍 [Reality Checker](testing/testing-reality-checker.md) | Evidence-based certification, quality gates | Production readiness, quality approval, release certification | -| 📊 [Test Results Analyzer](testing/testing-test-results-analyzer.md) | Test evaluation, metrics analysis | Test output analysis, quality insights, coverage reporting | -| ⚡ [Performance Benchmarker](testing/testing-performance-benchmarker.md) | Performance testing, optimization | Speed testing, load testing, performance tuning | -| 🔌 [API Tester](testing/testing-api-tester.md) | API validation, integration testing | API testing, endpoint verification, integration QA | -| 🛠️ [Tool Evaluator](testing/testing-tool-evaluator.md) | Technology assessment, tool selection | Evaluating tools, software recommendations, tech decisions | -| 🔄 [Workflow Optimizer](testing/testing-workflow-optimizer.md) | Process analysis, workflow improvement | Process optimization, efficiency gains, automation opportunities | -| ♿ [Accessibility Auditor](testing/testing-accessibility-auditor.md) | WCAG auditing, assistive technology testing | Accessibility compliance, screen reader testing, inclusive design verification | - -### 🛟 Support Division - -The backbone of the operation. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 💬 [Support Responder](support/support-support-responder.md) | Customer service, issue resolution | Customer support, user experience, support operations | -| 📊 [Analytics Reporter](support/support-analytics-reporter.md) | Data analysis, dashboards, insights | Business intelligence, KPI tracking, data visualization | -| 💰 [Finance Tracker](support/support-finance-tracker.md) | Financial planning, budget management | Financial analysis, cash flow, business performance | -| 🏗️ [Infrastructure Maintainer](support/support-infrastructure-maintainer.md) | System reliability, performance optimization | Infrastructure management, system operations, monitoring | -| ⚖️ [Legal Compliance Checker](support/support-legal-compliance-checker.md) | Compliance, regulations, legal review | Legal compliance, regulatory requirements, risk management | -| 📑 [Executive Summary Generator](support/support-executive-summary-generator.md) | C-suite communication, strategic summaries | Executive reporting, strategic communication, decision support | - -### 🥽 Spatial Computing Division - -Building the immersive future. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🏗️ [XR Interface Architect](spatial-computing/xr-interface-architect.md) | Spatial interaction design, immersive UX | AR/VR/XR interface design, spatial computing UX | -| 💻 [macOS Spatial/Metal Engineer](spatial-computing/macos-spatial-metal-engineer.md) | Swift, Metal, high-performance 3D | macOS spatial computing, Vision Pro native apps | -| 🌐 [XR Immersive Developer](spatial-computing/xr-immersive-developer.md) | WebXR, browser-based AR/VR | Browser-based immersive experiences, WebXR apps | -| 🎮 [XR Cockpit Interaction Specialist](spatial-computing/xr-cockpit-interaction-specialist.md) | Cockpit-based controls, immersive systems | Cockpit control systems, immersive control interfaces | -| 🍎 [visionOS Spatial Engineer](spatial-computing/visionos-spatial-engineer.md) | Apple Vision Pro development | Vision Pro apps, spatial computing experiences | -| 🔌 [Terminal Integration Specialist](spatial-computing/terminal-integration-specialist.md) | Terminal integration, command-line tools | CLI tools, terminal workflows, developer tools | - -### 🎯 Specialized Division - -The unique specialists who don't fit in a box. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎭 [Agents Orchestrator](specialized/agents-orchestrator.md) | Multi-agent coordination, workflow management | Complex projects requiring multiple agent coordination | -| 🔍 [LSP/Index Engineer](specialized/lsp-index-engineer.md) | Language Server Protocol, code intelligence | Code intelligence systems, LSP implementation, semantic indexing | -| 📥 [Sales Data Extraction Agent](specialized/sales-data-extraction-agent.md) | Excel monitoring, sales metric extraction | Sales data ingestion, MTD/YTD/Year End metrics | -| 📈 [Data Consolidation Agent](specialized/data-consolidation-agent.md) | Sales data aggregation, dashboard reports | Territory summaries, rep performance, pipeline snapshots | -| 📬 [Report Distribution Agent](specialized/report-distribution-agent.md) | Automated report delivery | Territory-based report distribution, scheduled sends | -| 🔐 [Agentic Identity & Trust Architect](specialized/agentic-identity-trust.md) | Agent identity, authentication, trust verification | Multi-agent identity systems, agent authorization, audit trails | -| 🔗 [Identity Graph Operator](specialized/identity-graph-operator.md) | Shared identity resolution for multi-agent systems | Entity deduplication, merge proposals, cross-agent identity consistency | -| 💸 [Accounts Payable Agent](specialized/accounts-payable-agent.md) | Payment processing, vendor management, audit | Autonomous payment execution across crypto, fiat, stablecoins | -| 🛡️ [Blockchain Security Auditor](specialized/blockchain-security-auditor.md) | Smart contract audits, exploit analysis | Finding vulnerabilities in contracts before deployment | -| 📋 [Compliance Auditor](specialized/compliance-auditor.md) | SOC 2, ISO 27001, HIPAA, PCI-DSS | Guiding organizations through compliance certification | -| 🌍 [Cultural Intelligence Strategist](specialized/specialized-cultural-intelligence-strategist.md) | Global UX, representation, cultural exclusion | Ensuring software resonates across cultures | -| 🗣️ [Developer Advocate](specialized/specialized-developer-advocate.md) | Community building, DX, developer content | Bridging product and developer community | -| 🔬 [Model QA Specialist](specialized/specialized-model-qa.md) | ML audits, feature analysis, interpretability | End-to-end QA for machine learning models | -| 🗃️ [ZK Steward](specialized/zk-steward.md) | Knowledge management, Zettelkasten, notes | Building connected, validated knowledge bases | -| 🔌 [MCP Builder](specialized/specialized-mcp-builder.md) | Model Context Protocol servers, AI agent tooling | Building MCP servers that extend AI agent capabilities | -| 📄 [Document Generator](specialized/specialized-document-generator.md) | PDF, PPTX, DOCX, XLSX generation from code | Professional document creation, reports, data visualization | -| ⚙️ [Automation Governance Architect](specialized/automation-governance-architect.md) | Automation governance, n8n, workflow auditing | Evaluating and governing business automations at scale | -| 📚 [Corporate Training Designer](specialized/corporate-training-designer.md) | Enterprise training, curriculum development | Designing training systems and learning programs | -| 🏛️ [Government Digital Presales Consultant](specialized/government-digital-presales-consultant.md) | China ToG presales, digital transformation | Government digital transformation proposals and bids | -| ⚕️ [Healthcare Marketing Compliance](specialized/healthcare-marketing-compliance.md) | China healthcare advertising compliance | Healthcare marketing regulatory compliance | -| 🎯 [Recruitment Specialist](specialized/recruitment-specialist.md) | Talent acquisition, recruiting operations | Recruitment strategy, sourcing, and hiring processes | -| 🎓 [Study Abroad Advisor](specialized/study-abroad-advisor.md) | International education, application planning | Study abroad planning across US, UK, Canada, Australia | -| 🔗 [Supply Chain Strategist](specialized/supply-chain-strategist.md) | Supply chain management, procurement strategy | Supply chain optimization and procurement planning | -| 🗺️ [Workflow Architect](specialized/specialized-workflow-architect.md) | Workflow discovery, mapping, and specification | Mapping every path through a system before code is written | -| ☁️ [Salesforce Architect](specialized/specialized-salesforce-architect.md) | Multi-cloud Salesforce design, governor limits, integrations | Enterprise Salesforce architecture, org strategy, deployment pipelines | -| 🇫🇷 [French Consulting Market Navigator](specialized/specialized-french-consulting-market.md) | ESN/SI ecosystem, portage salarial, rate positioning | Freelance consulting in the French IT market | -| 🇰🇷 [Korean Business Navigator](specialized/specialized-korean-business-navigator.md) | Korean business culture, 품의 process, relationship mechanics | Foreign professionals navigating Korean business relationships | -| 🏗️ [Civil Engineer](specialized/specialized-civil-engineer.md) | Structural analysis, geotechnical design, global building codes | Multi-standard structural engineering across Eurocode, ACI, AISC, and more | -| 🎧 [Customer Service](specialized/customer-service.md) | Omnichannel support, complaint handling, retention, escalation | Any industry customer support — retail, SaaS, hospitality, finance, logistics | -| 🏥 [Healthcare Customer Service](specialized/healthcare-customer-service.md) | HIPAA-aware patient support, billing, insurance, emergency routing | Healthcare organizations needing compliant, empathetic patient support | -| 🏨 [Hospitality Guest Services](specialized/hospitality-guest-services.md) | Reservations, concierge, complaint recovery, loyalty, events | Hotels, resorts, restaurants, and event venues | -| 🤝 [HR Onboarding](specialized/hr-onboarding.md) | Pre-boarding, compliance, benefits enrollment, 30-60-90 day plans | Any company onboarding new hires — from startups to enterprise | -| 🌐 [Language Translator](specialized/language-translator.md) | Spanish ↔ English translation, dialect awareness, cultural context | Travel, business, medical, and legal translation needs | -| ⏱️ [Legal Billing & Time Tracking](specialized/legal-billing-time-tracking.md) | Time capture, billing narratives, IOLTA compliance, collections | Law firms maximizing revenue recovery and billing accuracy | -| 📋 [Legal Client Intake](specialized/legal-client-intake.md) | Prospect qualification, conflict screening, consultation scheduling | Law firms converting inquiries into retained clients | -| ⚖️ [Legal Document Review](specialized/legal-document-review.md) | Contract review, risk flagging, version comparison, compliance | Attorney-ready first-pass review across any practice area | -| 🏦 [Loan Officer Assistant](specialized/loan-officer-assistant.md) | Borrower intake, TRID compliance, pipeline tracking, closing coordination | Mortgage and consumer lending teams | -| 🏠 [Real Estate Buyer & Seller](specialized/real-estate-buyer-seller.md) | Buyer/seller representation, offers, transaction coordination | Residential and investment real estate transactions | -| 🛒 [Retail Customer Returns](specialized/retail-customer-returns.md) | Return processing, fraud prevention, exchanges, vendor returns | Brick-and-mortar, e-commerce, and omnichannel retail | - -### 💵 Finance Division - -Accounting, financial analysis, tax strategy, and investment research specialists. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 📒 [Bookkeeper & Controller](finance/finance-bookkeeper-controller.md) | Month-end close, reconciliation, GAAP compliance, internal controls | Day-to-day accounting operations, audit readiness, financial record-keeping | -| 📊 [Financial Analyst](finance/finance-financial-analyst.md) | Financial modeling, forecasting, scenario analysis, decision support | Three-statement models, variance analysis, data-driven business intelligence | -| 📈 [FP&A Analyst](finance/finance-fpa-analyst.md) | Budgeting, rolling forecasts, variance analysis, business reviews | Annual operating plans, monthly business reviews, strategic resource allocation | -| 🔍 [Investment Researcher](finance/finance-investment-researcher.md) | Due diligence, portfolio analysis, asset valuation, equity research | Investment thesis development, risk assessment, market research | -| 🏛️ [Tax Strategist](finance/finance-tax-strategist.md) | Tax optimization, multi-jurisdictional compliance, transfer pricing | Entity structuring, ETR analysis, audit defense, strategic tax planning | - -### 🎮 Game Development Division - -Building worlds, systems, and experiences across every major engine. - -#### Cross-Engine Agents (Engine-Agnostic) - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🎯 [Game Designer](game-development/game-designer.md) | Systems design, GDD authorship, economy balancing, gameplay loops | Designing game mechanics, progression systems, writing design documents | -| 🗺️ [Level Designer](game-development/level-designer.md) | Layout theory, pacing, encounter design, environmental storytelling | Building levels, designing encounter flow, spatial narrative | -| 🎨 [Technical Artist](game-development/technical-artist.md) | Shaders, VFX, LOD pipeline, art-to-engine optimization | Bridging art and engineering, shader authoring, performance-safe asset pipelines | -| 🔊 [Game Audio Engineer](game-development/game-audio-engineer.md) | FMOD/Wwise, adaptive music, spatial audio, audio budgets | Interactive audio systems, dynamic music, audio performance | -| 📖 [Narrative Designer](game-development/narrative-designer.md) | Story systems, branching dialogue, lore architecture | Writing branching narratives, implementing dialogue systems, world lore | - -#### Unity - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🏗️ [Unity Architect](game-development/unity/unity-architect.md) | ScriptableObjects, data-driven modularity, DOTS/ECS | Large-scale Unity projects, data-driven system design, ECS performance work | -| ✨ [Unity Shader Graph Artist](game-development/unity/unity-shader-graph-artist.md) | Shader Graph, HLSL, URP/HDRP, Renderer Features | Custom Unity materials, VFX shaders, post-processing passes | -| 🌐 [Unity Multiplayer Engineer](game-development/unity/unity-multiplayer-engineer.md) | Netcode for GameObjects, Unity Relay/Lobby, server authority, prediction | Online Unity games, client prediction, Unity Gaming Services integration | -| 🛠️ [Unity Editor Tool Developer](game-development/unity/unity-editor-tool-developer.md) | EditorWindows, AssetPostprocessors, PropertyDrawers, build validation | Custom Unity Editor tooling, pipeline automation, content validation | - -#### Unreal Engine - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| ⚙️ [Unreal Systems Engineer](game-development/unreal-engine/unreal-systems-engineer.md) | C++/Blueprint hybrid, GAS, Nanite constraints, memory management | Complex Unreal gameplay systems, Gameplay Ability System, engine-level C++ | -| 🎨 [Unreal Technical Artist](game-development/unreal-engine/unreal-technical-artist.md) | Material Editor, Niagara, PCG, Substrate | Unreal materials, Niagara VFX, procedural content generation | -| 🌐 [Unreal Multiplayer Architect](game-development/unreal-engine/unreal-multiplayer-architect.md) | Actor replication, GameMode/GameState hierarchy, dedicated server | Unreal online games, replication graphs, server authoritative Unreal | -| 🗺️ [Unreal World Builder](game-development/unreal-engine/unreal-world-builder.md) | World Partition, Landscape, HLOD, LWC | Large open-world Unreal levels, streaming systems, terrain at scale | - -#### Godot - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 📜 [Godot Gameplay Scripter](game-development/godot/godot-gameplay-scripter.md) | GDScript 2.0, signals, composition, static typing | Godot gameplay systems, scene composition, performance-conscious GDScript | -| 🌐 [Godot Multiplayer Engineer](game-development/godot/godot-multiplayer-engineer.md) | MultiplayerAPI, ENet/WebRTC, RPCs, authority model | Online Godot games, scene replication, server-authoritative Godot | -| ✨ [Godot Shader Developer](game-development/godot/godot-shader-developer.md) | Godot shading language, VisualShader, RenderingDevice | Custom Godot materials, 2D/3D effects, post-processing, compute shaders | - -#### Blender - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🧩 [Blender Addon Engineer](game-development/blender/blender-addon-engineer.md) | Blender Python (`bpy`), custom operators/panels, asset validators, exporters, pipeline automation | Building Blender add-ons, asset prep tools, export workflows, and DCC pipeline automation | - -#### Roblox Studio - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| ⚙️ [Roblox Systems Scripter](game-development/roblox-studio/roblox-systems-scripter.md) | Luau, RemoteEvents/Functions, DataStore, server-authoritative module architecture | Building secure Roblox game systems, client-server communication, data persistence | -| 🎯 [Roblox Experience Designer](game-development/roblox-studio/roblox-experience-designer.md) | Engagement loops, monetization, D1/D7 retention, onboarding flow | Designing Roblox game loops, Game Passes, daily rewards, player retention | -| 👗 [Roblox Avatar Creator](game-development/roblox-studio/roblox-avatar-creator.md) | UGC pipeline, accessory rigging, Creator Marketplace submission | Roblox UGC items, HumanoidDescription customization, in-experience avatar shops | - -### 📚 Academic Division - -Scholarly rigor for world-building, storytelling, and narrative design. - -| Agent | Specialty | When to Use | -|-------|-----------|-------------| -| 🌍 [Anthropologist](academic/academic-anthropologist.md) | Cultural systems, kinship, rituals, belief systems | Designing culturally coherent societies with internal logic | -| 🌐 [Geographer](academic/academic-geographer.md) | Physical/human geography, climate, cartography | Building geographically coherent worlds with realistic terrain and settlements | -| 📚 [Historian](academic/academic-historian.md) | Historical analysis, periodization, material culture | Validating historical coherence, enriching settings with authentic period detail | -| 📜 [Narratologist](academic/academic-narratologist.md) | Narrative theory, story structure, character arcs | Analyzing and improving story structure with established theoretical frameworks | -| 🧠 [Psychologist](academic/academic-psychologist.md) | Personality theory, motivation, cognitive patterns | Building psychologically credible characters grounded in research | - ---- - -## 🎯 Real-World Use Cases - -### Scenario 1: Building a Startup MVP - -**Your Team**: -1. 🎨 **Frontend Developer** - Build the React app -2. 🏗️ **Backend Architect** - Design the API and database -3. 🚀 **Growth Hacker** - Plan user acquisition -4. ⚡ **Rapid Prototyper** - Fast iteration cycles -5. 🔍 **Reality Checker** - Ensure quality before launch - -**Result**: Ship faster with specialized expertise at every stage. - ---- - -### Scenario 2: Marketing Campaign Launch - -**Your Team**: -1. 📝 **Content Creator** - Develop campaign content -2. 🐦 **Twitter Engager** - Twitter strategy and execution -3. 📸 **Instagram Curator** - Visual content and stories -4. 🤝 **Reddit Community Builder** - Authentic community engagement -5. 📊 **Analytics Reporter** - Track and optimize performance - -**Result**: Multi-channel coordinated campaign with platform-specific expertise. - ---- - -### Scenario 3: Enterprise Feature Development - -**Your Team**: -1. 👔 **Senior Project Manager** - Scope and task planning -2. 💎 **Senior Developer** - Complex implementation -3. 🎨 **UI Designer** - Design system and components -4. 🧪 **Experiment Tracker** - A/B test planning -5. 📸 **Evidence Collector** - Quality verification -6. 🔍 **Reality Checker** - Production readiness - -**Result**: Enterprise-grade delivery with quality gates and documentation. - ---- - -### Scenario 4: Paid Media Account Takeover - -**Your Team**: - -1. 📋 **Paid Media Auditor** - Comprehensive account assessment -2. 📡 **Tracking & Measurement Specialist** - Verify conversion tracking accuracy -3. 💰 **PPC Campaign Strategist** - Redesign account architecture -4. 🔍 **Search Query Analyst** - Clean up wasted spend from search terms -5. ✍️ **Ad Creative Strategist** - Refresh all ad copy and extensions -6. 📊 **Analytics Reporter** (Support Division) - Build reporting dashboards - -**Result**: Systematic account takeover with tracking verified, waste eliminated, structure optimized, and creative refreshed — all within the first 30 days. - ---- - -### Scenario 5: Full Agency Product Discovery - -**Your Team**: All 8 divisions working in parallel on a single mission. - -See the **[Nexus Spatial Discovery Exercise](examples/nexus-spatial-discovery.md)** -- a complete example where 8 agents (Product Trend Researcher, Backend Architect, Brand Guardian, Growth Hacker, Support Responder, UX Researcher, Project Shepherd, and XR Interface Architect) were deployed simultaneously to evaluate a software opportunity and produce a unified product plan covering market validation, technical architecture, brand strategy, go-to-market, support systems, UX research, project execution, and spatial UI design. - -**Result**: Comprehensive, cross-functional product blueprint produced in a single session. [More examples](examples/). - ---- - -## 🤝 Contributing - -We welcome contributions! Here's how you can help: - -### Add a New Agent - -1. Fork the repository -2. Create a new agent file in the appropriate category -3. Follow the agent template structure: - - Frontmatter with name, description, color - - Identity & Memory section - - Core Mission - - Critical Rules (domain-specific) - - Technical Deliverables with examples - - Workflow Process - - Success Metrics -4. Submit a PR with your agent - -### Improve Existing Agents - -- Add real-world examples -- Enhance code samples -- Update success metrics -- Improve workflows - -### Share Your Success Stories - -Have you used these agents successfully? Share your story in the [Discussions](https://github.com/msitarzewski/agency-agents/discussions)! - ---- - -## 📖 Agent Design Philosophy - -Each agent is designed with: - -1. **🎭 Strong Personality**: Not generic templates - real character and voice -2. **📋 Clear Deliverables**: Concrete outputs, not vague guidance -3. **✅ Success Metrics**: Measurable outcomes and quality standards -4. **🔄 Proven Workflows**: Step-by-step processes that work -5. **💡 Learning Memory**: Pattern recognition and continuous improvement - ---- - -## 🎁 What Makes This Special? - -### Unlike Generic AI Prompts: -- ❌ Generic "Act as a developer" prompts -- ✅ Deep specialization with personality and process - -### Unlike Prompt Libraries: -- ❌ One-off prompt collections -- ✅ Comprehensive agent systems with workflows and deliverables - -### Unlike AI Tools: -- ❌ Black box tools you can't customize -- ✅ Transparent, forkable, adaptable agent personalities - ---- - -## 🎨 Agent Personality Highlights - -> "I don't just test your code - I default to finding 3-5 issues and require visual proof for everything." -> -> -- **Evidence Collector** (Testing Division) - -> "You're not marketing on Reddit - you're becoming a valued community member who happens to represent a brand." -> -> -- **Reddit Community Builder** (Marketing Division) - -> "Every playful element must serve a functional or emotional purpose. Design delight that enhances rather than distracts." -> -> -- **Whimsy Injector** (Design Division) - -> "Let me add a celebration animation that reduces task completion anxiety by 40%" -> -> -- **Whimsy Injector** (during a UX review) - ---- - -## 📊 Stats - -- 🎭 **144 Specialized Agents** across 12 divisions -- 📝 **10,000+ lines** of personality, process, and code examples -- ⏱️ **Months of iteration** from real-world usage -- 🌟 **Battle-tested** in production environments -- 💬 **50+ requests** in first 12 hours on Reddit - ---- - -## 🔌 Multi-Tool Integrations - -The Agency works natively with Claude Code, and ships conversion + install scripts so you can use the same agents across every major agentic coding tool. - -### Supported Tools - -- **[Claude Code](https://claude.ai/code)** — native `.md` agents, no conversion needed → `~/.claude/agents/` -- **[GitHub Copilot](https://github.com/copilot)** — native `.md` agents, no conversion needed → `~/.github/agents/` + `~/.copilot/agents/` -- **[Antigravity](https://github.com/google-gemini/antigravity)** — `SKILL.md` per agent → `~/.gemini/antigravity/skills/` -- **[Gemini CLI](https://github.com/google-gemini/gemini-cli)** — extension + `SKILL.md` files → `~/.gemini/extensions/agency-agents/` -- **[OpenCode](https://opencode.ai)** — `.md` agent files → `.opencode/agents/` -- **[Cursor](https://cursor.sh)** — `.mdc` rule files → `.cursor/rules/` -- **[Aider](https://aider.chat)** — single `CONVENTIONS.md` → `./CONVENTIONS.md` -- **[Windsurf](https://codeium.com/windsurf)** — single `.windsurfrules` → `./.windsurfrules` -- **[OpenClaw](https://github.com/openclaw/openclaw)** — `SOUL.md` + `AGENTS.md` + `IDENTITY.md` per agent -- **[Qwen Code](https://github.com/QwenLM/qwen-code)** — `.md` SubAgent files → `~/.qwen/agents/` -- **[Kimi Code](https://github.com/MoonshotAI/kimi-cli)** — YAML agent specs → `~/.config/kimi/agents/` - ---- - -### ⚡ Quick Install - -**Step 1 -- Generate integration files:** -```bash -./scripts/convert.sh -# Faster (parallel, output order may vary): ./scripts/convert.sh --parallel -``` - -**Step 2 -- Install (interactive, auto-detects your tools):** -```bash -./scripts/install.sh -# Faster (parallel, output order may vary): ./scripts/install.sh --no-interactive --parallel -``` - -The installer scans your system for installed tools, shows a checkbox UI, and lets you pick exactly what to install: - -``` - +------------------------------------------------+ - | The Agency -- Tool Installer | - +------------------------------------------------+ - - System scan: [*] = detected on this machine - - [x] 1) [*] Claude Code (claude.ai/code) - [x] 2) [*] Copilot (~/.github + ~/.copilot) - [x] 3) [*] Antigravity (~/.gemini/antigravity) - [ ] 4) [ ] Gemini CLI (gemini extension) - [ ] 5) [ ] OpenCode (opencode.ai) - [ ] 6) [ ] OpenClaw (~/.openclaw/agency-agents) - [x] 7) [*] Cursor (.cursor/rules) - [ ] 8) [ ] Aider (CONVENTIONS.md) - [ ] 9) [ ] Windsurf (.windsurfrules) - [ ] 10) [ ] Qwen Code (~/.qwen/agents) - [ ] 11) [ ] Kimi Code (~/.config/kimi/agents) - - [1-11] toggle [a] all [n] none [d] detected - [Enter] install [q] quit -``` - -**Or install a specific tool directly:** -```bash -./scripts/install.sh --tool cursor -./scripts/install.sh --tool opencode -./scripts/install.sh --tool openclaw -./scripts/install.sh --tool antigravity -``` - -**Non-interactive (CI/scripts):** -```bash -./scripts/install.sh --no-interactive --tool all -``` - -**Faster runs (parallel)** — On multi-core machines, use `--parallel` so each tool is processed in parallel. Output order across tools is non-deterministic. Works with both interactive and non-interactive install: e.g. `./scripts/install.sh --interactive --parallel` (pick tools, then install in parallel) or `./scripts/install.sh --no-interactive --parallel`. Job count defaults to `nproc` (Linux), `sysctl -n hw.ncpu` (macOS), or 4; override with `--jobs N`. - -```bash -./scripts/convert.sh --parallel # convert all tools in parallel -./scripts/convert.sh --parallel --jobs 8 # cap parallel jobs -./scripts/install.sh --no-interactive --parallel # install all detected tools in parallel -./scripts/install.sh --interactive --parallel # pick tools, then install in parallel -./scripts/install.sh --no-interactive --parallel --jobs 4 -``` - ---- - -### Tool-Specific Instructions - -
-Claude Code - -Agents are copied directly from the repo into `~/.claude/agents/` -- no conversion needed. - -```bash -./scripts/install.sh --tool claude-code -``` - -Then activate in Claude Code: -``` -Use the Frontend Developer agent to review this component. -``` - -See [integrations/claude-code/README.md](integrations/claude-code/README.md) for details. -
- -
-GitHub Copilot - -Agents are copied directly from the repo into `~/.github/agents/` and `~/.copilot/agents/` -- no conversion needed. - -```bash -./scripts/install.sh --tool copilot -``` - -Then activate in GitHub Copilot: -``` -Use the Frontend Developer agent to review this component. -``` - -See [integrations/github-copilot/README.md](integrations/github-copilot/README.md) for details. -
- -
-Antigravity (Gemini) - -Each agent becomes a skill in `~/.gemini/antigravity/skills/agency-/`. - -```bash -./scripts/install.sh --tool antigravity -``` - -Activate in Gemini with Antigravity: -``` -@agency-frontend-developer review this React component -``` - -See [integrations/antigravity/README.md](integrations/antigravity/README.md) for details. -
- -
-Gemini CLI - -Installs as a Gemini CLI extension with one skill per agent plus a manifest. -On a fresh clone, generate the Gemini extension files before running the installer. - -```bash -./scripts/convert.sh --tool gemini-cli -./scripts/install.sh --tool gemini-cli -``` - -See [integrations/gemini-cli/README.md](integrations/gemini-cli/README.md) for details. -
- -
-OpenCode - -Agents are placed in `.opencode/agents/` in your project root (project-scoped). - -```bash -cd /your/project -/path/to/agency-agents/scripts/install.sh --tool opencode -``` - -Or install globally: -```bash -mkdir -p ~/.config/opencode/agents -cp integrations/opencode/agents/*.md ~/.config/opencode/agents/ -``` - -Activate in OpenCode: -``` -@backend-architect design this API. -``` - -See [integrations/opencode/README.md](integrations/opencode/README.md) for details. -
- -
-Cursor - -Each agent becomes a `.mdc` rule file in `.cursor/rules/` of your project. - -```bash -cd /your/project -/path/to/agency-agents/scripts/install.sh --tool cursor -``` - -Rules are auto-applied when Cursor detects them in the project. Reference them explicitly: -``` -Use the @security-engineer rules to review this code. -``` - -See [integrations/cursor/README.md](integrations/cursor/README.md) for details. -
- -
-Aider - -All agents are compiled into a single `CONVENTIONS.md` file that Aider reads automatically. - -```bash -cd /your/project -/path/to/agency-agents/scripts/install.sh --tool aider -``` - -Then reference agents in your Aider session: -``` -Use the Frontend Developer agent to refactor this component. -``` - -See [integrations/aider/README.md](integrations/aider/README.md) for details. -
- -
-Windsurf - -All agents are compiled into `.windsurfrules` in your project root. - -```bash -cd /your/project -/path/to/agency-agents/scripts/install.sh --tool windsurf -``` - -Reference agents in Windsurf's Cascade: -``` -Use the Reality Checker agent to verify this is production ready. -``` - -See [integrations/windsurf/README.md](integrations/windsurf/README.md) for details. -
- -
-OpenClaw - -Each agent becomes a workspace with `SOUL.md`, `AGENTS.md`, and `IDENTITY.md` in `~/.openclaw/agency-agents/`. - -```bash -./scripts/convert.sh --tool openclaw -./scripts/install.sh --tool openclaw -``` - -If the `openclaw` CLI is available, the installer registers each workspace automatically. -Run `openclaw gateway restart` after installation so the new agents are activated. - -See [integrations/openclaw/README.md](integrations/openclaw/README.md) for details. - -
- -
-Qwen Code - -SubAgents are installed to `.qwen/agents/` in your project root (project-scoped). - -```bash -# Convert and install (run from your project root) -cd /your/project -./scripts/convert.sh --tool qwen -./scripts/install.sh --tool qwen -``` - -**Usage in Qwen Code:** -- Reference by name: `Use the frontend-developer agent to review this component` -- Or let Qwen auto-delegate based on task context -- Manage via `/agents` command in interactive mode - -> 📚 [Qwen SubAgents Docs](https://qwenlm.github.io/qwen-code-docs/en/users/features/sub-agents/) - -
- -
-Kimi Code - -Agents are converted to Kimi Code CLI format (YAML + system prompt) and installed to `~/.config/kimi/agents/`. - -```bash -# Convert and install -./scripts/convert.sh --tool kimi -./scripts/install.sh --tool kimi -``` - -**Usage with Kimi Code:** -```bash -# Use an agent -kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml - -# In a project -kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml \ - --work-dir /your/project \ - "Review this React component" -``` - -See [integrations/kimi/README.md](integrations/kimi/README.md) for details. - -
- ---- - -### Regenerating After Changes - -When you add new agents or edit existing ones, regenerate all integration files: - -```bash -./scripts/convert.sh # regenerate all (serial) -./scripts/convert.sh --parallel # regenerate all in parallel (faster) -./scripts/convert.sh --tool cursor # regenerate just one tool -``` - ---- - -## 🗺️ Roadmap - -- [ ] Interactive agent selector web tool -- [x] Multi-agent workflow examples -- see [examples/](examples/) -- [x] Multi-tool integration scripts (Claude Code, GitHub Copilot, Antigravity, Gemini CLI, OpenCode, OpenClaw, Cursor, Aider, Windsurf, Qwen Code, Kimi Code) -- [ ] Video tutorials on agent design -- [ ] Community agent marketplace -- [ ] Agent "personality quiz" for project matching -- [ ] "Agent of the Week" showcase series - ---- - -## 🌐 Community Translations & Localizations - -Community-maintained translations and regional adaptations. These are independently maintained -- see each repo for coverage and version compatibility. - -| Language | Maintainer | Link | Notes | -|----------|-----------|------|-------| -| 🇨🇳 简体中文 (zh-CN) | [@jnMetaCode](https://github.com/jnMetaCode) | [agency-agents-zh](https://github.com/jnMetaCode/agency-agents-zh) | 141 translated agents + 46 China-market originals | -| 🇨🇳 简体中文 (zh-CN) | [@dsclca12](https://github.com/dsclca12) | [agent-teams](https://github.com/dsclca12/agent-teams) | Independent translation with Bilibili, WeChat, Xiaohongshu localization | - -Want to add a translation? Open an issue and we'll link it here. - ---- - -## 🔗 Related Resources - -- [awesome-openclaw-agents](https://github.com/mergisi/awesome-openclaw-agents) — Community-maintained OpenClaw agent collection (derived from this repo) - ---- - -## 📜 License - -MIT License - Use freely, commercially or personally. Attribution appreciated but not required. - ---- - -## 🙏 Acknowledgments - -What started as a Reddit thread about AI agent specialization has grown into something remarkable — **147 agents across 12 divisions**, supported by a community of contributors from around the world. Every agent in this repo exists because someone cared enough to write it, test it, and share it. - -To everyone who has opened a PR, filed an issue, started a Discussion, or simply tried an agent and told us what worked — thank you. You're the reason The Agency keeps getting better. - ---- - -## 💬 Community - -- **GitHub Discussions**: [Share your success stories](https://github.com/msitarzewski/agency-agents/discussions) -- **Issues**: [Report bugs or request features](https://github.com/msitarzewski/agency-agents/issues) -- **Reddit**: Join the conversation on r/ClaudeAI -- **Twitter/X**: Share with #TheAgency - ---- - -## 🚀 Get Started - -1. **Browse** the agents above and find specialists for your needs -2. **Copy** the agents to `~/.claude/agents/` for Claude Code integration -3. **Activate** agents by referencing them in your Claude conversations -4. **Customize** agent personalities and workflows for your specific needs -5. **Share** your results and contribute back to the community - ---- - -
- -**🎭 The Agency: Your AI Dream Team Awaits 🎭** - -[⭐ Star this repo](https://github.com/msitarzewski/agency-agents) • [🍴 Fork it](https://github.com/msitarzewski/agency-agents/fork) • [🐛 Report an issue](https://github.com/msitarzewski/agency-agents/issues) • [❤️ Sponsor](https://github.com/sponsors/msitarzewski) - -Made with ❤️ by the community, for the community - -
diff --git a/raw/Agent/agency-agents/specialized/zk-steward.md b/raw/Agent/agency-agents/specialized/zk-steward.md index 6a56bb63..52f6a3c2 100644 --- a/raw/Agent/agency-agents/specialized/zk-steward.md +++ b/raw/Agent/agency-agents/specialized/zk-steward.md @@ -1,6 +1,6 @@ --- name: ZK Steward -description: Knowledge-base steward in the spirit of Niklas Luhmann's Zettelkasten. Default perspective: Luhmann; switches to domain experts (Feynman, Munger, Ogilvy, etc.) by task. Enforces atomic notes, connectivity, and validation loops. Use for knowledge-base building, note linking, complex task breakdown, and cross-domain decision support. +description: Knowledge-base steward in the spirit of Niklas Luhmann's Zettelkasten. Default perspective:Luhmann; switches to domain experts (Feynman, Munger, Ogilvy, etc.) by task. Enforces atomic notes, connectivity, and validation loops. Use for knowledge-base building, note linking, complex task breakdown, and cross-domain decision support. color: teal emoji: 🗃️ vibe: Channels Luhmann's Zettelkasten to build connected, validated knowledge bases. diff --git a/wiki/concepts/AIOps.md b/wiki/concepts/AIOps.md new file mode 100644 index 00000000..61f9db4e --- /dev/null +++ b/wiki/concepts/AIOps.md @@ -0,0 +1,55 @@ +--- +title: AIOps +tags: + - ai + - devops + - it-operations +created: 2026-04-22 +--- + +# AIOps + +## Definition + +AIOps (Artificial Intelligence for IT Operations) is the application of artificial intelligence and machine learning to IT operations. It automates the detection, diagnosis, and resolution of operational issues in cloud environments. + +## Purpose + +AIOps enables: +- **Proactive issue detection** — Identifying problems before they impact users +- **Intelligent alerting** — Reducing noise and focusing on actionable alerts +- **Automated root cause analysis** — Accelerating incident resolution +- **Predictive analytics** — Forecasting capacity needs and potential failures + +## Relationship with Cloud Service Delivery + +AIOps is a natural extension of the [[Cloud Service Delivery]] operational model, specifically supporting: +- [[Performance & Availability Monitoring]] +- [[Incident Management]] +- [[Problem Management]] +- [[Change Management]] + +## Related Concepts + +- [[Cloud Service Delivery]] +- [[Cloud DevOps Maturity Model]] +- [[Observability]] +- [[Incident Management]] + +## Related Sources + +- [[what-i-know-about-cloud-service-delivery-1]] + +## AIOps Capabilities + +```python +# Typical AIOps capabilities +aiops_capabilities = [ + "Anomaly Detection", # Identify unusual patterns + "Root Cause Analysis", # Automatic diagnosis + "Predictive Maintenance", # Forecast failures + "Smart Alerting", # Reduce alert fatigue + "Automated Remediation", # Self-healing systems + "Capacity Optimization" # Resource optimization +] +``` diff --git a/wiki/concepts/AgilePractices.md b/wiki/concepts/AgilePractices.md new file mode 100644 index 00000000..a6aeb3a5 --- /dev/null +++ b/wiki/concepts/AgilePractices.md @@ -0,0 +1,34 @@ +--- +title: "Agile Practices" +type: concept +tags: [agile, scrum, kanban, devops] +sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin] +last_updated: 2026-04-22 +--- + +## Summary +Agile Practices are iterative development methodologies (Scrum, Kanban) that emphasize continuous delivery, customer collaboration, and adaptability. In the DevOps context, Agile and DevOps are symbiotic — Agile focuses on iterative development while DevOps extends agility to operations, together enabling end-to-end speed and quality. Agile frameworks provide the delivery cadence while DevOps provides the operational excellence to sustain it. + +## Key Frameworks + +### Scrum +- Structured sprints with defined timeboxes +- Roles: Product Owner, Scrum Master, Development Team +- Ceremonies: Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective + +### Kanban +- Continuous flow model (no fixed sprints) +- Visual board with WIP limits +- Focus on throughput and cycle time + +## Agile + DevOps Integration +- **CI/CD as Agile Accelerators**: Automating testing and deployment shrinks feedback cycles from weeks to minutes +- **Value Stream Mapping**: Lean technique to identify and eliminate waste in Agile/DevOps workflows +- **Shift-Left**: Moving operations concerns (security, performance) into Agile sprints + +## Connections +- [[DevOps Culture]] — Agile and DevOps are symbiotic; DevOps extends Agile to operations +- [[CI/CD Pipeline]] — CI/CD accelerates Agile feedback cycles +- [[Value Stream Mapping]] — Lean technique for Agile/DevOps workflow optimization +- [[Shift-Left Testing]] — Agile practice of moving testing earlier in the lifecycle +- [[Project State Management]] — [[Event Sourcing]] as an alternative to Kanban-style collaboration (see Conflict Area in overview.md) diff --git a/wiki/concepts/Availability.md b/wiki/concepts/Availability.md new file mode 100644 index 00000000..7fadec81 --- /dev/null +++ b/wiki/concepts/Availability.md @@ -0,0 +1,71 @@ +# Availability + +## Definition +Availability is the time a system remains operational and accessible to users. It is typically expressed as a percentage of uptime over a defined period (e.g., monthly or yearly). + +The DevOps Maturity Model explicitly lists Availability as one of the key metrics for measuring DevOps maturity. + +## Availability SLAs + +Common availability targets: + +| Availability | Downtime/Year | Downtime/Month | Downtime/Week | +|-------------|---------------|----------------|---------------| +| 99% | 3.65 days | 7.31 hours | 1.68 hours | +| 99.9% | 8.76 hours | 43.83 minutes | 10.08 minutes | +| 99.99% | 52.60 minutes | 4.38 minutes | 1.01 minutes | +| 99.999% | 5.26 minutes | 26.30 seconds | 6.05 seconds | + +## Across DevOps Maturity Levels + +| Maturity | Availability Capability | +|----------|----------------------| +| Phase 1 | Poor — reactive monitoring, siloed teams, manual processes cause frequent outages | +| Phase 2 | Improving — essential monitoring detects issues, but manual intervention required | +| Phase 3 | Better — automated infrastructure reduces human errors, faster recovery | +| Phase 4 | High — continuous monitoring for early detection, root cause analysis capability | +| Phase 5 | Max uptime — no interruptions to customer experience, rapid data-driven decisions | + +## Key Practices for High Availability + +### Architecture +- Redundancy at every layer +- Load balancing +- Geographic distribution +- Graceful degradation +- Circuit breakers + +### Operations +- Continuous monitoring +- Automated failover +- Disaster recovery planning +- Regular maintenance windows +- Capacity planning + +### Development +- Robust error handling +- Idempotent operations +- Transaction management +- Feature flags for rapid rollback +- Chaos engineering + +## Relationship with Other Metrics + +| Metric | Relationship with Availability | +|--------|-------------------------------| +| **MTTD** | Faster detection = shorter outage = higher availability | +| **MTTR** | Faster recovery = shorter outage = higher availability | +| **Error Budget** | Availability target defines the error budget | +| **Change Failure Rate** | Fewer failed deployments = fewer outages = higher availability | +| **Scalability** | Better scalability prevents availability degradation under load | + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/High-Availability]] +- [[concepts/MTTR]] +- [[concepts/Error-Budget]] +- [[concepts/Scalability]] +- [[concepts/Disaster-Recovery]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/CI-CD-Pipeline.md b/wiki/concepts/CI-CD-Pipeline.md new file mode 100644 index 00000000..d331af76 --- /dev/null +++ b/wiki/concepts/CI-CD-Pipeline.md @@ -0,0 +1,61 @@ +# CI/CD Pipeline + +## Definition +CI/CD (Continuous Integration/Continuous Delivery/Deployment) pipelines automate the process of building, testing, and deploying software changes. + +## Components + +### Continuous Integration (CI) +- Automated builds on code commits +- Automated testing (unit, integration, e2e) +- Code quality checks and linting +- Artifact generation + +### Continuous Delivery (CD) +- Automated deployment to staging environments +- Manual approval gates for production +- Configuration management + +### Continuous Deployment +- Fully automated deployment to production +- Feature flags for gradual rollout +- Automated rollback capabilities + +## Tools +- **CI/CD Platforms**: Jenkins, GitLab CI, GitHub Actions, CircleCI, ArgoCD +- **Build Tools**: Maven, Gradle, npm, Docker +- **Testing**: JUnit, PyTest, Selenium, Playwright + +## Best Practices +1. Keep the pipeline fast (under 10 minutes) +2. Fail fast — run fastest tests first +3. Use meaningful commit messages and branch names +4. Implement proper caching strategies +5. Store build artifacts securely +6. Enable parallel test execution + +## CI/CD Pipeline Across DevOps Maturity Levels + +| Maturity | Pipeline Maturity | +|----------|------------------| +| Phase 1 | No CI/CD — manual builds, manual testing, milestone-based releases | +| Phase 2 | Basic version control, some automation for risk reduction, unit/integration/E2E tests | +| Phase 3 | Automated infrastructure provisioning, security scans in CI, more frequent deployments | +| Phase 4 | Continuous integration pipeline, immutable infrastructure managed through pipelines, performance testing | +| Phase 5 | Zero human intervention, real-time data-driven decisions, multiple daily deployments | + +## Sources +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/DevSecOps]] +- [[concepts/Continuous-Integration]] +- [[concepts/Continuous-Deployment]] +- [[concepts/Change-Failure-Rate]] + +## Ingested +- Date: 2026-04-21 +- Date: 2026-04-24 (updated with maturity level progression) diff --git a/wiki/concepts/CICDPipeline.md b/wiki/concepts/CICDPipeline.md new file mode 100644 index 00000000..7382f18d --- /dev/null +++ b/wiki/concepts/CICDPipeline.md @@ -0,0 +1,43 @@ +--- +title: "CI/CD Pipeline" +type: concept +tags: [devops, cicd, automation, continuous-delivery] +sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin] +last_updated: 2026-04-22 +--- + +## Summary +CI/CD (Continuous Integration / Continuous Delivery) Pipelines automate the entire software delivery process — from code commit through testing, integration, and deployment. In DevOps, CI/CD is a foundational automation enabler that shrinks feedback cycles from weeks to minutes. Key tools include Jenkins, GitLab CI, and GitHub Actions. + +## Key Concepts + +### Continuous Integration (CI) +- Developers merge code changes frequently (multiple times daily) +- Automated builds and tests run on every commit +- Catches integration bugs early + +### Continuous Delivery (CD) +- Code changes are automatically prepared for release +- Deployment to staging/production is a manual decision +- Ensures software is always in a deployable state + +### Continuous Deployment +- Every change that passes tests is automatically deployed to production +- Full automation of the release process + +## Key Tools +- **Jenkins** — Open-source automation server with extensive plugin ecosystem +- **GitLab CI** — Integrated CI/CD within GitLab +- **GitHub Actions** — CI/CD built into GitHub + +## In the DevOps Context +CI/CD pipelines are described as "Agile Accelerators" that automate testing and deployment to shrink feedback cycles. They enable teams to: +- Ship features faster with confidence +- Reduce deployment risk through automated testing +- Enable frequent, low-risk releases + +## Connections +- [[DevOps Culture]] — CI/CD is an automation pillar of DevOps +- [[Infrastructure as Code (IaC)]] — Complementary automation practice +- [[DevSecOps]] — Security tools integrated into CI/CD pipelines +- [[GitOps]] — GitOps extends CI/CD with Git-as-source-of-truth diff --git a/wiki/concepts/Change-Failure-Rate.md b/wiki/concepts/Change-Failure-Rate.md new file mode 100644 index 00000000..b8ed4089 --- /dev/null +++ b/wiki/concepts/Change-Failure-Rate.md @@ -0,0 +1,83 @@ +# Change Failure Rate + +## Definition +Change Failure Rate (CFR) is the percentage of deployments that cause failures in production — such as service outages, degraded performance, or incidents requiring hotfixes, rollbacks, or patches. + +Change Failure Rate is one of the four core **DORA metrics** used to measure DevOps performance. + +## Why Change Failure Rate Matters + +A low change failure rate indicates: +- High confidence in the deployment process +- Robust testing and quality assurance +- Effective risk management +- Mature operational practices + +A high change failure rate means: +- Frequent production incidents +- Unstable deployments +- Low team confidence +- Customer impact + +## Across DevOps Maturity Levels + +| Maturity | Change Failure Rate Characteristic | +|----------|-----------------------------------| +| Phase 1 | High — manual processes, no automated testing, siloed teams, security only at release | +| Phase 2 | Improving — unit, integration, and end-to-end tests implemented, but security separate | +| Phase 3 | Lower — automated infrastructure, security scans integrated throughout development | +| Phase 4 | Significantly reduced — performance/load testing, immutable infrastructure, dependency vulnerability management | +| Phase 5 | 0-15% (elite) — zero human intervention, real-time data decisions, high-level security integration prevents non-compliant code | + +## Elite Performance Benchmark (DORA) +- **Elite performers**: 0-15% change failure rate +- **High performers**: 16-30% change failure rate +- **Medium performers**: 16-30% change failure rate +- **Low performers**: 31-100% change failure rate + +## Types of Failed Changes +- Production outages +- Service degradations +- Data corruption +- Security vulnerabilities introduced +- Performance regressions +- Failed rollbacks + +## How to Reduce Change Failure Rate + +### Technical Practices +- Comprehensive test automation (unit, integration, E2E) +- Feature flags for gradual rollouts +- Canary deployments +- Blue-green deployments +- Automated rollback mechanisms +- Chaos engineering to find weaknesses before production + +### Process Improvements +- Code review requirements +- Security scanning in CI/CD pipeline +- Staging environment parity with production +- Small batch sizes to limit blast radius +- Dependency management and vulnerability scanning + +### Cultural Factors +- Blameless post-mortems +- Learning from failures +- Psychological safety to report issues +- Shared ownership of reliability + +## Relationship with Other DORA Metrics +- **Deployment Frequency**: Higher frequency with lower CFR indicates elite performance +- **Lead Time**: Shorter lead times with maintained/low CFR = high performance +- **MTTR**: Lower CFR means fewer incidents, contributing to lower overall MTTR + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/DORA-Metrics]] +- [[concepts/Continuous-Deployment]] +- [[concepts/DevOps-Maturity]] +- [[concepts/Error-Budget]] +- [[concepts/Rollback-Rate]] diff --git a/wiki/concepts/Cloud-Adoption-Strategy.md b/wiki/concepts/Cloud-Adoption-Strategy.md new file mode 100644 index 00000000..47fd6662 --- /dev/null +++ b/wiki/concepts/Cloud-Adoption-Strategy.md @@ -0,0 +1,77 @@ +--- +title: Cloud Adoption Strategy +source: https://www.bacancytechnology.com/blog/cloud-maturity-model +tags: [Cloud, Strategy, Transformation, Cloud-Maturity] +--- + +# Cloud Adoption Strategy + +## Overview + +A **Cloud Adoption Strategy** is a comprehensive plan that guides organizations through the process of transitioning their workloads, applications, and infrastructure to cloud environments. The Cloud Maturity Model (CMM) provides a structured framework for developing and executing this strategy. + +## Key Elements + +### 1. Setting Cloud Adoption Objectives + +Before adopting cloud services, organizations should: + +- **Clarify Motivations** — Focus on cloud economics and Total Cost of Ownership (TCO) to understand how cost savings and efficiency drive adoption +- **Determine Business Goals** — Align technical strategies with business objectives to ensure cloud adoption meets organizational needs +- **Develop a Business Case** — Create a strong business case to secure support from internal teams, including finance and management + +### 2. Identifying Current Maturity Level + +Understanding your current cloud maturity level (0-5) allows for: +- Tailored objectives based on current state +- More effective cloud adoption strategy +- Right balance between cloud-native services and hybrid architecture + +### 3. Selecting the Right Maturity Model + +Various models are available: +- **OACA Cloud Maturity Model** — General framework, provider-neutral +- **AWS Cloud Adoption Framework** — AWS-specific best practices +- **Azure Cloud Adoption Framework** — Microsoft Azure guidance +- **Google Cloud Adoption Framework** — Google Cloud transition guide +- **Cloud Security Maturity Model (CSMM)** — Security-specific assessment + +### 4. Following Governance and Compliance + +Establish: +- Framework defining roles, responsibilities, and decision-making +- Comprehensive policies (security, access controls, data protection, cost management, incident response) +- Alignment with industry regulations (HIPAA, PCI-DSS) + +### 5. Security and Risk Management + +- Encryption and access controls +- Regular backups and monitoring +- Frequent risk assessments +- Security awareness training + +## Relationship with Cloud Maturity Model + +The CMM serves as both a diagnostic tool and a roadmap: +- **Diagnostic** — Assess current state across people, processes, and technology +- **Roadmap** — Guide progression through 5 maturity levels +- **Benchmarking** — Compare progress against industry standards + +## Best Practices + +1. Avoid skipping maturity levels — sustainable transformation requires incremental progress +2. Focus on long-term sustainability over rapid technological change +3. Selectively adopt Level 5 elements that bring clear business benefits +4. Establish clear KPIs for cloud utilization +5. Invest in education and training programs + +## Related Concepts + +- [[Cloud-Maturity-Model]] +- [[Multi-Cloud-Strategy]] +- [[Cloud-Native]] +- [[FinOps]] + +## Sources + +- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] diff --git a/wiki/concepts/Cloud-DevOps-Maturity-Model.md b/wiki/concepts/Cloud-DevOps-Maturity-Model.md new file mode 100644 index 00000000..e72cf928 --- /dev/null +++ b/wiki/concepts/Cloud-DevOps-Maturity-Model.md @@ -0,0 +1,47 @@ +--- +title: Cloud DevOps Maturity Model +tags: + - cloud + - devops + - maturity +created: 2026-04-22 +--- + +# Cloud DevOps Maturity Model + +## Overview + +The Cloud DevOps Maturity Model is a framework for evaluating and advancing an organization's cloud DevOps capabilities. It assesses how well teams have adopted DevOps practices in cloud environments across multiple dimensions. + +## Related Concepts + +- [[Cloud Service Delivery]] — The broader context of cloud operations +- [[DevOps Maturity]] — General DevOps maturity assessment +- [[DORA Metrics]] — DevOps Research and Assessment metrics +- [[Cloud Maturity Levels]] — General cloud maturity assessment + +## Related Sources + +- [[what-i-know-about-cloud-service-delivery-1]] +- [[cloud-devop-maturity-guideline]] + +## Key Dimensions + +While the source document mentions this as a concept to be explored, typical Cloud DevOps Maturity dimensions include: + +1. **Automation** — Infrastructure provisioning, deployment, testing automation +2. **Collaboration** — Cross-functional team alignment +3. **Monitoring & Observability** — Cloud-native monitoring solutions +4. **Security Integration (DevSecOps)** — Security embedded in the pipeline +5. **Incident Response** — Automated response and recovery +6. **Continuous Improvement** — Feedback loops and optimization + +## Maturity Indicators + +| Level | Characteristics | +|-------|-----------------| +| Level 1 | Ad-hoc cloud usage, manual processes | +| Level 2 | Basic automation, some monitoring | +| Level 3 | IaC adoption, CI/CD pipelines | +| Level 4 | Advanced automation, proactive monitoring | +| Level 5 | Self-healing systems, AI-driven optimization | diff --git a/wiki/concepts/Cloud-Maturity-Levels.md b/wiki/concepts/Cloud-Maturity-Levels.md new file mode 100644 index 00000000..2ad7947b --- /dev/null +++ b/wiki/concepts/Cloud-Maturity-Levels.md @@ -0,0 +1,90 @@ +--- +title: Cloud Maturity Levels (0-5) +source: https://www.bacancytechnology.com/blog/cloud-maturity-model +tags: [Cloud, Maturity, Levels, Assessment, Transformation] +--- + +# Cloud Maturity Levels (0-5) + +## Overview + +The Cloud Maturity Model defines **5 maturity levels** (Level 0-5) that represent stages of organizational cloud adoption capability. These levels provide a structured assessment framework for evaluating current state and planning progression. + +## The Six Maturity Levels + +### Level 0: Legacy (No Cloud Readiness) +- Company doesn't use the cloud at all +- Relies solely on outdated systems +- No plans to adopt cloud services +- Starting new projects is slow and difficult +- Often due to strict regulations (high security or data requirements) rather than lack of readiness + +### Level 1: Initial Readiness (Ad hoc) +- Company has assessed software and services for cloud integration +- Some initial experience with cloud services +- Possibly migrating a few systems +- Still operates primarily on legacy and non-virtualized systems +- Cloud mainly used for SaaS or specific business unit needs +- No clear overall strategy + +**Key Challenges:** Limited cloud knowledge, minimal leadership support, absence of clear strategy, undefined processes + +### Level 2: Repeatable, Opportunistic +- Established IT and procurement procedures for cloud services +- Decided who can subscribe and how +- Processes are defined and repeatable +- Cloud services used extensively +- Approach isn't yet fully systematic and clearly defined + +**Key Challenges:** Cost control concerns, lack of documented policies, over-reliance on manual tasks, limited cloud usage visibility + +### Level 3: Systematic and Documented +- Implemented process or outsourced service to manage cloud subscriptions +- Monitor existing services systematically +- Operations are more efficient and systematic +- Documented practices and compliance in place +- Includes documented cloud management processes and updated operational policies + +**Key Challenges:** Ensuring consistency, staff training, effective environment management, workload optimization + +### Level 4: Measured +- Cloud-native applications used extensively in daily operations +- Widely adopted across organization +- Utilizes private, public, and hybrid cloud platforms +- Often partially reached — some capabilities may still be at levels 2 or 3 +- Transparent governance model to manage and measure cloud operations +- Measuring end-to-end process performance and data usage + +**Key Challenge:** Need for governance model when deploying cloud services quickly + +### Level 5: Optimized (Highest Level) +- Open and interoperable cloud environment +- Actively developed using metrics and data +- Processes are optimized +- Decisions are data-driven +- Adeptly use various cloud platforms +- Flexibly move workloads between platforms + +**Reality Check:** Often more aspirational than real. Companies usually lag in optimizing processes and fully leveraging data. Can be overinvestment if extensive hybrid cloud solutions are optional. + +## Common Anti-Pattern: Skipping Levels + +> "Often, businesses try to skip levels 2 and 3, aiming directly from level 0 or 1 to level 4 using technology solutions. While rapid technological change may seem attractive, ensuring long-term sustainability is crucial." + +## Key Insights + +1. **Incremental Progress** — Sustainable cloud maturity requires incremental advancement through each level +2. **Partial Maturity is Normal** — Organizations often partially reach level 4, with some capabilities still at levels 2 or 3 +3. **Not All Levels Are Necessary** — Selectively adopting Level 5 elements that bring clear business benefits may be more practical than full Level 5 achievement +4. **Governance is Critical** — A transparent governance model becomes essential from Level 4 onwards + +## Related Concepts + +- [[Cloud-Maturity-Model]] +- [[Cloud-Adoption-Strategy]] +- [[Cloud-Native]] +- [[DevOps-Maturity]] + +## Sources + +- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] diff --git a/wiki/concepts/Cloud-Native.md b/wiki/concepts/Cloud-Native.md new file mode 100644 index 00000000..0b218218 --- /dev/null +++ b/wiki/concepts/Cloud-Native.md @@ -0,0 +1,35 @@ +# Cloud-Native + +## Definition +Cloud-native is an approach to building and running applications that fully exploits the advantages of cloud computing delivery model. + +## Core Characteristics +- **Microservices Architecture**: Applications built as small, independently deployable services +- **Containers**: Lightweight, portable packaging for applications +- **Dynamic Orchestration**: Automated management of containers (e.g., Kubernetes) +- **API-Based Communication**: Services communicate via lightweight APIs +- **DevOps Practices**: Continuous integration and delivery + +## Key Technologies +- **Containers**: Docker, containerd, Podman +- **Orchestration**: Kubernetes, Amazon EKS, Azure AKS, Google GKE +- **Service Mesh**: Istio, Linkerd, Consul Connect +- **Serverless**: AWS Lambda, Azure Functions, Google Cloud Functions + +## Benefits +- Scalability and elasticity +- Resilience and fault isolation +- Faster deployment cycles +- Resource efficiency +- Portability across cloud providers + +## Sources +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Infrastructure-as-Code]] + +## Ingested +- Date: 2026-04-21 diff --git a/wiki/concepts/Cloud-Service-Delivery.md b/wiki/concepts/Cloud-Service-Delivery.md new file mode 100644 index 00000000..639b072f --- /dev/null +++ b/wiki/concepts/Cloud-Service-Delivery.md @@ -0,0 +1,76 @@ +--- +title: Cloud Service Delivery +tags: + - cloud + - devops + - it-operations +created: 2026-04-22 +--- + +# Cloud Service Delivery + +## Definition + +Cloud Service Delivery encompasses **the entire lifecycle of making cloud services operational, available, secure, performant, and valuable to end-users and customers.** + +**In essence, Cloud Service Delivery is the bridge between the raw capabilities of cloud technology (IaaS, PaaS, SaaS) and the reliable, secure, performant, and cost-effective services that businesses and users actually consume.** + +## The Bridge Concept + +``` +┌─────────────────────────────────────────────────────────────────┐ +│ Cloud Service Delivery │ +│ (The Bridge) │ +│ │ +│ Raw Cloud Capabilities ──────► Business Value for End Users │ +│ (IaaS, PaaS, SaaS) (Reliable, Secure, Performant) │ +└─────────────────────────────────────────────────────────────────┘ +``` + +## 12 Operational Domains + +1. **Service Provisioning & Deployment** — Setting up cloud infrastructure, automating deployments, configuring services, managing resource allocation and scaling +2. **Infrastructure Management** — Monitoring health/performance/capacity, patching, managing physical data center aspects, ensuring HA and DR +3. **Platform Management (PaaS)** — Managing middleware, databases, development tools, runtime environments, platform scalability/security/performance +4. **Application Operations & Management** — Monitoring app performance, deploying updates, managing configuration and secrets, ensuring scalability and resilience +5. **Security & Compliance Management** — Implementing security controls (firewalls, IDS/IPS, encryption, IAM), vulnerability scanning, incident response, regulatory compliance +6. **Performance & Availability Monitoring** — 24/7 monitoring, SLA/SLO tracking, proactive detection, incident response +7. **Incident & Problem Management** — Responding to alerts, troubleshooting, incident management, problem management (root cause analysis) +8. **Change & Configuration Management** — Change control, Infrastructure as Code (IaC), testing and rollback plans +9. **Cost Management & Optimization** — Monitoring consumption, eliminating waste, right-sizing, reserved instances/savings plans +10. **Customer Onboarding & Support** — User setup, documentation, helpdesk/service desk, billing inquiries +11. **Service Governance & Lifecycle Management** — Service catalogs, SLAs, service lifecycle, continuous improvement, vendor management +12. **Backup, Recovery & Disaster Management** — Backup strategies, restore testing, DR plans, failover/failback procedures + +## Cloud Service Delivery Team Roles + +- **Cloud Infrastructure Engineer** +- **Cloud Operation Engineer (DevOps/SRE)** +- **Cloud Security Specialists** +- **Cloud Support Engineer** +- **Cloud FinOps Engineer** + +## Related Concepts + +- [[Cloud DevOps Maturity Model]] — Maturity framework for evaluating cloud DevOps capabilities +- [[AIOps]] — Artificial Intelligence for IT Operations +- [[SLA]] / [[SLO]] — Service Level Agreements/Objectives +- [[FinOps]] — Cloud financial management +- [[DevOps]] — Development and Operations integration +- [[SRE]] — Site Reliability Engineering +- [[ITSM]] — IT Service Management + +## Related Sources + +- [[what-i-know-about-cloud-service-delivery-1]] + +## Best Practices + +| Domain | Best Practice | +|--------|---------------| +| Infrastructure Monitoring | AWS CloudWatch as data source in Grafana | +| Security | Cloud Application WAF management, IP whitelist to tenant level | +| Availability | APM/BPM, New Relic, AWS CloudWatch Synthetic, Health Page | +| Uptime | SLA 99.9% vs 99.99% ([uptime.is](https://uptime.is/)) | +| Alerting | Grafana Alerting with different severity levels | +| Change Management | Planned Change vs Emergency Change | diff --git a/wiki/concepts/Continuous-Deployment.md b/wiki/concepts/Continuous-Deployment.md new file mode 100644 index 00000000..c31816f8 --- /dev/null +++ b/wiki/concepts/Continuous-Deployment.md @@ -0,0 +1,49 @@ +# Continuous Deployment + +## Definition +Continuous Deployment (CD) is a DevOps practice where code changes that pass all automated tests are automatically deployed to production environments without manual intervention. + +## Key Characteristics + +### Across DevOps Maturity Levels +| Maturity | CD Practice Level | +|----------|-------------------| +| Phase 1 | Manual deployments, milestone-based releases, no automation | +| Phase 2 | Automation used to reduce release risks, but still requires manual triggers | +| Phase 3 | Automated infrastructure provisioning, more frequent deployments possible | +| Phase 4 | Continuous integration pipeline enables tangible business benefits; infrastructure and code managed through pipelines | +| Phase 5 | Multiple deployments per day with high certainty and minimal risk; zero human intervention for code changes passing through the pipeline | + +### Core CD Elements +- Automated deployment pipelines +- Zero human intervention after code commit +- High confidence in automation quality +- Fast rollback capabilities +- Progressive delivery strategies (canary, blue-green) +- Real-time monitoring post-deployment + +## Relationship with Continuous Integration + +CD builds on CI. The full CI/CD pipeline: +1. **CI** — Every code change triggers automated builds and tests +2. **CD** — Changes passing CI are automatically deployed + +At Phase 5 maturity, the CI/CD pipeline achieves **continuous deployment** where code flows from commit to production automatically. + +## Business Impact +- Faster time-to-market +- Reduced release risk through smaller, incremental changes +- Rapid feedback from production users +- Higher team productivity +- Competitive advantage through rapid iteration + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Continuous-Integration]] +- [[concepts/DevOps-Maturity]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/Error-Budget]] diff --git a/wiki/concepts/Continuous-Integration.md b/wiki/concepts/Continuous-Integration.md new file mode 100644 index 00000000..fd3cd90b --- /dev/null +++ b/wiki/concepts/Continuous-Integration.md @@ -0,0 +1,51 @@ +# Continuous Integration + +## Definition +Continuous Integration (CI) is a DevOps practice where developers frequently merge their code changes into a shared repository, triggering automated builds and tests to detect integration issues early. + +## Key Characteristics + +### Across DevOps Maturity Levels +| Maturity | CI Practice Level | +|----------|-------------------| +| Phase 1 | None — manual integration, siloed development | +| Phase 2 | Introduction — version control for code and configurations | +| Phase 3 | Automated builds and tests integrated into the development process | +| Phase 4 | CI pipeline with automated quality gates, performance and load testing | +| Phase 5 | Zero-touch CI pipeline with real-time data for decision making | + +### Core CI Elements +- Automated builds triggered on every code commit +- Automated unit, integration, and end-to-end tests +- Static code analysis and security scans +- Fast, reliable build pipelines +- Immediate feedback to developers + +## Role in DevOps Maturity + +CI is a foundational DevOps practice. Organizations cannot advance to higher DevOps maturity without robust CI. At Phase 3+, CI is combined with continuous delivery (CD) to form CI/CD pipelines. + +Key progression: +1. **Phase 2**: Version control introduction, superficial automation +2. **Phase 3**: Most builds automated, security scans in the pipeline +3. **Phase 4**: Immutable infrastructure managed through CI pipelines +4. **Phase 5**: Zero human intervention — all code changes pass through automated pipeline + +## Metrics +- Build success rate +- Build frequency +- Mean time to build +- Code coverage percentage +- Test pass rate +- Time to first failure detection + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Continuous-Deployment]] +- [[concepts/DevOps-Maturity]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/DevSecOps]] diff --git a/wiki/concepts/Cost-Optimization.md b/wiki/concepts/Cost-Optimization.md new file mode 100644 index 00000000..1f48e35b --- /dev/null +++ b/wiki/concepts/Cost-Optimization.md @@ -0,0 +1,60 @@ +--- +title: Cost Optimization +tags: [Cloud, FinOps, Finance] +--- + +# Cost Optimization + +## Overview + +**Cost Optimization**（成本优化）指通过策略、流程和技术手段最大化云投资回报的过程。FinOps 是云成本优化的核心方法论，多云策略通过竞争性定价和资源调配进一步增强成本控制能力。 + +## Key Strategies + +### 1. Right-Sizing (合理规格) +根据实际使用需求选择合适规格的资源，避免过度配置： +- 定期审查资源利用率 +- 使用监控数据识别过度配置实例 +- 自动推荐合理规格调整 + +### 2. Reserved Capacity (预留容量) +通过预留实例获取显著折扣（通常 30-70%）： +- 分析稳定工作负载模式 +- 评估 1 年/3 年预留承诺 +- 平衡灵活性与折扣 + +### 3. Spot/Preemptible Instances (竞价实例) +利用空闲容量获得大幅折扣（通常 70-90%）： +- 适用于容错工作负载（批处理、CI/CD） +- 实施中断处理机制 +- 混合使用 Spot 和 On-Demand + +### 4. Multi-Cloud Cost Arbitrage (多云成本套利) +利用不同提供商的定价差异优化成本： +- 不同提供商在不同服务上有价格优势 +- 工作负载分配到最具成本效益的提供商 +- 动态调度成本敏感工作负载 + +### 5. FinOps Practices +- **Chargeback/Showback**: 透明化云成本归属 +- **Continuous Optimization**: 持续监控和优化 +- **Unit Economics**: 按业务单位追踪云成本效率 + +## Multi-Cloud ROI Statistics + +| Metric | Value | Source | +|--------|-------|--------| +| 多云优化后运营成本降低 | 30% | Forrester | +| 78% 企业使用 3+ 公有云 | 78% | Virtana | +| 86% 企业计划采用多云 | 86% | New Horizons | + +## Related Concepts + +- [[FinOps]] +- [[Multi-Cloud Strategy]] +- [[ROI]] +- [[Scalability]] + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/concepts/DORA-Metrics.md b/wiki/concepts/DORA-Metrics.md new file mode 100644 index 00000000..56b14b3e --- /dev/null +++ b/wiki/concepts/DORA-Metrics.md @@ -0,0 +1,53 @@ +# DORA Metrics + +## Definition +DORA (DevOps Research and Assessment) metrics are four key performance indicators established by the DevOps Research and Assessment team to measure and benchmark DevOps performance. + +## The Four Keys + +| Metric | Description | Elite Performance | +|--------|-------------|------------------| +| **Deployment Frequency** | How often code is deployed to production | On-demand (multiple deploys per day) | +| **Lead Time for Changes** | Time from code commit to production | Less than one hour | +| **Change Failure Rate** | Percentage of deployments causing failures | 0-15% | +| **Mean Time to Recovery (MTTR)** | Time to restore service after a failure | Less than one hour | + +## Usage in DevOps Maturity Assessment +DORA metrics are a core component of DevOps maturity evaluation, providing quantifiable measures of an organization's DevOps performance. High-performing organizations typically deploy on-demand, have short lead times, low change failure rates, and rapid recovery times. + +## Extended Metrics from DevOps Maturity Model + +Beyond the four core DORA metrics, the DevOps Maturity Model (Bacancy) identifies additional operational metrics: + +| Metric | Description | +|--------|-------------| +| **Time-To-Market** | Period from initial concept to product launch | +| **Code Deployment Success Rate** | Proportion of successful deployments | +| **Rollback Rate** | Proportion of deployments that are reverted | +| **Error Budget** | Permissible rate of errors and failures in production | +| **Availability** | Time the system remains operational and accessible | +| **Scalability** | System's ability to manage increased load | +| **Time-in-stage** | Average duration to complete each development phase | +| **Code Review Feedback Loop Time** | Time to receive and act on code review feedback | + +## Sources +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Lead-Time]] +- [[concepts/Time-to-Market]] +- [[concepts/Change-Failure-Rate]] +- [[concepts/MTTR]] +- [[concepts/MTTD]] +- [[concepts/MTTA]] +- [[concepts/Error-Budget]] +- [[concepts/Rollback-Rate]] +- [[concepts/Availability]] +- [[concepts/Scalability]] + +## Ingested +- Date: 2026-04-21 +- Date: 2026-04-24 (added extended metrics) diff --git a/wiki/concepts/Data-Sovereignty.md b/wiki/concepts/Data-Sovereignty.md new file mode 100644 index 00000000..efd95a18 --- /dev/null +++ b/wiki/concepts/Data-Sovereignty.md @@ -0,0 +1,64 @@ +--- +title: Data Sovereignty +tags: [Cloud, Compliance, Legal] +--- + +# Data Sovereignty + +**Data Sovereignty** refers to the legal concept that data is subject to the laws and regulations of the country or region where it is collected, stored, or processed. + +## Overview + +Data sovereignty has become a critical concern in cloud computing as organizations store and process data across multiple geographic locations, often across national borders. + +## Key Regulatory Frameworks + +| Region | Regulation | Key Requirements | +|--------|------------|------------------| +| EU | GDPR | Data must be stored/processed within EU or with adequate safeguards | +| China | PIPL | Critical data must stay in China | +| US | State-specific laws | Varying requirements across 50 states | +| Brazil | LGPD | Similar to GDPR for Brazilian data | +| India | DPDP Act | Data localization for certain categories | + +## Multi-Cloud as Enabler + +[[Multi-Cloud-Strategy]] enables data sovereignty compliance by: + +- Selecting providers with data centers in required regions +- Distributing data across compliant geographic locations +- Matching provider certifications to regulatory requirements +- Enabling data residency controls + +## Industry-Specific Requirements + +### Healthcare +- HIPAA (US): Patient data must have proper safeguards +- Regional health data laws may require local storage + +### Finance +- Banking regulations often require data to stay within national borders +- Payment card data (PCI-DSS) has geographic constraints + +### Government +- Classified or sensitive data often requires sovereign infrastructure +- FedRAMP, IL-4/5 requirements in US government context + +## Best Practices + +1. **Map Data Flows** — Understand where data originates, moves, and is stored +2. **Select Compliant Providers** — Verify provider certifications per region +3. **Implement Data Classification** — Identify which data has sovereignty requirements +4. **Use Regional Deployments** — Match infrastructure to data requirements +5. **Monitor Compliance** — Continuous audit of data locations + +## Related Concepts + +- [[Multi-Cloud-Strategy]] — Primary enabler for sovereignty compliance +- [[Cloud-Maturity-Model]] — Level 3+ addresses compliance concerns +- [[Cloud-Security]] — Security controls support sovereignty +- [[Compliance-Auditor]] — Agent specializing in compliance frameworks + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/concepts/DevOps-Maturity.md b/wiki/concepts/DevOps-Maturity.md new file mode 100644 index 00000000..6f71dcc4 --- /dev/null +++ b/wiki/concepts/DevOps-Maturity.md @@ -0,0 +1,71 @@ +# DevOps Maturity + +## Definition +DevOps Maturity refers to the degree to which an organization has adopted and integrated DevOps practices, ranging from initial ad-hoc processes to highly optimized, automated, and collaborative workflows. + +## Key Dimensions + +### 1. Automation +- CI/CD pipelines +- Infrastructure as Code (IaC) +- Test automation +- Deployment automation + +### 2. Collaboration & Culture +- Cross-team collaboration between development, operations, and security +- Breaking down organizational silos +- Shared goals and responsibilities + +### 3. Monitoring & Observability +- Continuous monitoring +- Centralized logging +- Swift issue detection and resolution + +### 4. Security Integration (DevSecOps) +- Security automated into the DevOps lifecycle +- Continuous compliance +- Proactive vulnerability management + +## Maturity Models +- **CMMI** (Capability Maturity Model Integration) +- **DORA Metrics**: Deployment Frequency, Lead Time for Changes, Change Failure Rate, MTTR + +## Measuring Maturity +- **Quantitative KPIs**: Deployment frequency, lead times, system uptime, incident resolution times +- **Qualitative indicators**: Employee collaboration, goal alignment, feedback loops between teams + +## Five Maturity Stages (Phase 1–5) + +| Stage | Name | Key Characteristics | +|-------|------|---------------------| +| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release | +| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation | +| Phase 3 | Automated and Defined | Standardized processes, automated infrastructure, security integrated into development | +| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management | +| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention | + +## Sources +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/DevSecOps]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/Cloud-Native]] +- [[concepts/Continuous-Integration]] +- [[concepts/Continuous-Deployment]] +- [[concepts/Lead-Time]] +- [[concepts/Time-to-Market]] +- [[concepts/Change-Failure-Rate]] +- [[concepts/MTTR]] +- [[concepts/MTTD]] +- [[concepts/MTTA]] +- [[concepts/Error-Budget]] +- [[concepts/Rollback-Rate]] +- [[concepts/Availability]] +- [[concepts/Scalability]] + +## Ingested +- Date: 2026-04-21 +- Date: 2026-04-24 (updated with Phase 1-5 details and metrics) diff --git a/wiki/concepts/DevOpsCulture.md b/wiki/concepts/DevOpsCulture.md new file mode 100644 index 00000000..8ad59b85 --- /dev/null +++ b/wiki/concepts/DevOpsCulture.md @@ -0,0 +1,58 @@ +--- +title: "DevOps Culture" +type: concept +tags: [devops, culture, collaboration, transformation] +sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin, devops-maturity-model-from-traditional-it-to-advanced-devops] +last_updated: 2026-04-22 +--- + +## Summary +DevOps Culture is the foundational mindset shift that bridges Development and Operations teams to break down organizational silos, accelerate software delivery, and drive continuous innovation. It emphasizes collaboration over isolation, shared ownership of the software lifecycle, and customer-centricity. DevOps culture is not merely about tools or automation — it is fundamentally a cultural revolution prioritizing collaboration, continuous learning, and feedback loops. + +## Four Foundational Pillars + +### 1. Collaboration Over Silos +Traditional IT structures pit developers (focused on rapid feature delivery) against operations (prioritizing stability). DevOps dismantles these silos through cross-functional teams sharing ownership of the entire software lifecycle. + +**Strategies:** +- **Shared Goals**: Align teams around common KPIs (deployment frequency, MTTR) +- **Cross-Training**: Developers learn infrastructure; operations staff engage in coding +- **Tools for Transparency**: Slack, Microsoft Teams, Atlassian Jira for real-time communication + +### 2. Automation as an Enabler +Automation eliminates manual toil, reduces errors, and accelerates feedback loops. + +**Key Areas:** +- CI/CD Pipelines (Jenkins, GitLab CI, GitHub Actions) +- Infrastructure as Code (Terraform, AWS CloudFormation) +- Monitoring & Observability (Prometheus, Grafana, Datadog) + +### 3. Continuous Improvement (Kaizen) +Iterative learning through: +- **Blameless Post-Mortems**: Dissect failures without finger-pointing +- **Metrics-Driven Bottleneck Identification**: Lead time, deployment success rate +- **Chaos Engineering**: Proactive system resilience testing + +### 4. Customer-Centricity +Every release solves real user problems through: +- **Feature Flagging**: Incremental rollout with user insights +- **A/B Testing**: Data-driven experience optimization + +## Transformation Playbook + +1. **Leadership Buy-In**: Executives champion collaboration and allocate resources +2. **Upskilling Teams**: Certifications (AWS DevOps, Kubernetes), internal Guilds/CoEs +3. **Start Small, Scale Fast**: Pilot projects demonstrate quick wins +4. **Overcoming Resistance**: Address fear of job loss; celebrate wins + +## Connections +- [[DevOps Culture and Transformation Source]] — Primary source document +- [[CI/CD Pipeline]] — Automation enabler +- [[Infrastructure as Code (IaC)]] — Automation pillar +- [[DevSecOps]] — Shift-Left security integration +- [[GitOps]] — Future trend +- [[Agile Practices]] — Complementary methodology +- [[Continuous Improvement (Kaizen)]] — Japanese philosophy applied to DevOps + +## Contradictions +- **Kanban vs Event Sourcing**: [[Project State Management]] emphasizes auto-tracking via event sourcing; traditional DevOps culture relies on Kanban-style visual collaboration and shared team boards. See overview.md Conflict Area #1. diff --git a/wiki/concepts/DevSecOps.md b/wiki/concepts/DevSecOps.md new file mode 100644 index 00000000..20d5990c --- /dev/null +++ b/wiki/concepts/DevSecOps.md @@ -0,0 +1,49 @@ +# DevSecOps + +## Definition +DevSecOps integrates security practices into the DevOps process, embedding security throughout the entire software development lifecycle rather than treating it as a separate phase. + +## Key Principles +- **Shift Left**: Integrate security early in the development process +- **Automation**: Security checks automated in CI/CD pipelines +- **Continuous Compliance**: Ongoing security validation and compliance monitoring +- **Proactive Vulnerability Management**: Early detection and remediation of security issues + +## Core Practices +- Static Application Security Testing (SAST) +- Dynamic Application Security Testing (DAST) +- Software Composition Analysis (SCA) +- Container security scanning +- Infrastructure as Code security validation +- Secret management and rotation + +## Tools +- SAST: SonarQube, Checkmarx, Semgrep +- Container scanning: Trivy, Clair, Snyk +- Secret management: HashiCorp Vault, AWS Secrets Manager + +## Security Progression Across DevOps Maturity Levels + +| Maturity | Security Integration Level | +|----------|--------------------------| +| Phase 1 | Security involvement only weeks before release, minimal compliance scans | +| Phase 2 | Security operates separately from the rest of the team | +| Phase 3 | Security involved in design, architecture, and operations discussions; scans integrated throughout development | +| Phase 4 | Dependency vulnerability management; continuous security monitoring across the team | +| Phase 5 | Prevent insecure/non-compliant code from reaching production; high-level security integration | + +## Sources +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/what-is-devsecops-best-practices-benefits-and-tools.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/DORA-Metrics]] +- [[concepts/Change-Failure-Rate]] + +## Ingested +- Date: 2026-04-21 +- Date: 2026-04-24 (updated with maturity level progression) diff --git a/wiki/concepts/Error-Budget.md b/wiki/concepts/Error-Budget.md new file mode 100644 index 00000000..67a81673 --- /dev/null +++ b/wiki/concepts/Error-Budget.md @@ -0,0 +1,79 @@ +# Error Budget + +## Definition +Error Budget is the permissible rate of errors and failures that a system can tolerate within a defined period without violating its reliability targets. It represents the "budget" of allowed failures before reliability SLAs are breached. + +Error Budget = 100% - (Actual Reliability Target) + +Example: If your target is 99.9% uptime, your error budget is 0.1% downtime per month. + +## Role in DevOps Maturity + +The DevOps Maturity Model explicitly lists Error Budget as one of the key metrics for measuring DevOps maturity. + +### Error Budget Across Maturity Levels +| Maturity | Error Budget Usage | +|----------|-------------------| +| Phase 1 | No error budget concept — reactive to failures as they occur | +| Phase 2 | Awareness growing — teams begin to understand the cost of failures | +| Phase 3 | Error budgets not explicitly managed — standardization helps but not measured | +| Phase 4 | Error budgets tracked — continuous monitoring enables measurement | +| Phase 5 | Error budgets actively used to drive deployment decisions — balancing innovation vs reliability | + +## How Error Budgets Work + +### The Concept +If your system achieves: +- **99.9% uptime**: 8.76 hours of downtime allowed per year (43.8 minutes per month) +- **99.99% uptime**: 52.6 minutes of downtime allowed per year (4.38 minutes per month) + +The "error budget" is the allowed bad events — once depleted, deployment velocity must slow down until reliability improves. + +### Error Budget Policy Example +- If error budget is >50% remaining: Deploy freely (encourage experimentation) +- If error budget is 25-50%: Proceed with caution, require additional testing +- If error budget is <25%: Pause non-critical deployments until budget recovers +- If error budget is exhausted: Stop all deployments, focus on reliability + +## Error Budget and SLOs + +| Concept | Role | +|---------|------| +| **SLO (Service Level Objective)** | The target reliability level (e.g., 99.9%) | +| **Error Budget** | The allowable failure budget derived from the SLO | +| **SLI (Service Level Indicator)** | The actual reliability measured | + +Error Budgets operationalize SLOs by creating concrete incentives for balancing innovation and reliability. + +## Business Impact + +### Benefits of Error Budget Thinking +1. **Incentivizes reliability**: Teams are motivated to maintain system health +2. **Enables calculated risk-taking**: Clear budget allows confident experimentation +3. **Prevents over-engineering**: Don't build for 99.999% when 99.9% is the target +4. **Aligns business and engineering**: Both understand the reliability-investment trade-off + +### Risks Without Error Budgets +- Over-investment in reliability beyond business needs +- Under-investment leading to frequent customer-facing failures +- Conflicting priorities between feature delivery and reliability +- No clear signal for when to slow down + +## Error Budget vs Change Failure Rate + +| Metric | Measures | +|--------|----------| +| **Error Budget** | Total allowable failures over a time period | +| **Change Failure Rate** | Percentage of deployments causing failures | + +These metrics work together: Low CFR preserves error budget; depleted error budget signals need to improve CFR. + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/SLO]] +- [[concepts/Change-Failure-Rate]] +- [[concepts/DORA-Metrics]] +- [[concepts/High-Availability]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/GitOps.md b/wiki/concepts/GitOps.md new file mode 100644 index 00000000..0c8a0ae6 --- /dev/null +++ b/wiki/concepts/GitOps.md @@ -0,0 +1,28 @@ +--- +title: "GitOps" +type: concept +tags: [devops, gitops, infrastructure, git] +sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin] +last_updated: 2026-04-22 +--- + +## Summary +GitOps is a DevOps methodology that uses Git as the single source of truth for managing infrastructure and application deployments. All desired state is stored in Git repositories, and automated tools (like ArgoCD or Flux) continuously reconcile the actual cluster state with the desired state defined in Git. It is identified as a key future trend in DevOps for managing both infrastructure and deployments declaratively. + +## Key Concepts + +### Core Principles +1. **The entire system described declaratively** — All infrastructure and application configurations are stored as code +2. **The canonical desired state in Git** — Git is the source of truth; any change goes through Git workflow +3. **Approved changes automatically pulled into the system** — Automated agents detect drift and reconcile + +### Tools +- **ArgoCD** — Kubernetes-native GitOps controller +- **Flux** — GitOps toolkit for Kubernetes +- **Atlantis** — Terraform GitOps automation (mentioned in CTP topics) + +## Connections +- [[DevOps Culture]] — GitOps is an operational pattern emerging from DevOps culture +- [[Infrastructure as Code (IaC)]] — GitOps extends IaC with Git-centric workflows +- [[CI/CD Pipeline]] — GitOps can be considered a specialized CI/CD pattern +- [[Continuous Improvement (Kaizen)]] — GitOps enables continuous, auditable improvements diff --git a/wiki/concepts/Infrastructure-as-Code.md b/wiki/concepts/Infrastructure-as-Code.md new file mode 100644 index 00000000..453cd755 --- /dev/null +++ b/wiki/concepts/Infrastructure-as-Code.md @@ -0,0 +1,50 @@ +# Infrastructure as Code (IaC) + +## Definition +Infrastructure as Code is the practice of managing and provisioning infrastructure through machine-readable configuration files rather than manual processes. + +## Key Principles +- **Version Control**: All infrastructure configurations are stored in version control +- **Idempotency**: Running the same configuration produces the same result +- **Automation**: Infrastructure provisioning is automated and repeatable +- **Documentation**: Code serves as documentation + +## Tools +- **Terraform**: Multi-cloud IaC tool using HCL +- **Ansible**: Configuration management and orchestration +- **CloudFormation**: AWS-native infrastructure provisioning +- **Pulumi**: IaC using general-purpose programming languages +- **Terragrunt**: Wrapper for Terraform providing organization + +## Best Practices +1. Use modules for reusable components +2. Separate state management (remote state with locking) +3. Implement proper access controls +4. Use workspaces for environment separation +5. Enable drift detection +6. Implement automated testing for IaC + +## IaC Across DevOps Maturity Levels + +| Maturity | IaC Maturity | +|----------|-------------| +| Phase 1 | Manual infrastructure management, servers managed individually, error-prone and slow | +| Phase 2 | Version control used for environments and configurations, but provisioning still manual | +| Phase 3 | Most infrastructure automated, provisioning repeatable and reliable | +| Phase 4 | Immutable infrastructure — old servers replaced rather than updated, managed through CI/CD pipelines | +| Phase 5 | Full automation, zero human intervention, infrastructure changes flow through automated pipelines | + +## Sources +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/GitOps]] +- [[concepts/Scalability]] +- [[concepts/Cloud-Native]] + +## Ingested +- Date: 2026-04-21 +- Date: 2026-04-24 (updated with maturity level progression) diff --git a/wiki/concepts/Lead-Time.md b/wiki/concepts/Lead-Time.md new file mode 100644 index 00000000..6ed007a5 --- /dev/null +++ b/wiki/concepts/Lead-Time.md @@ -0,0 +1,55 @@ +# Lead Time + +## Definition +Lead Time (specifically Lead Time for Changes) is the interval from when a developer commits code to when that code is successfully deployed to production. It measures the total time from code commitment to customer-facing value delivery. + +## Importance +Lead Time is a critical DORA (DevOps Research and Assessment) metric. Short lead times indicate: +- Efficient development and delivery processes +- High levels of automation +- Reduced risk in deployments +- Faster feedback loops +- Better alignment with business objectives + +## Across DevOps Maturity Levels + +| Maturity | Lead Time Characteristic | +|----------|-------------------------| +| Phase 1 | Long — manual processes, milestone-based releases, siloed teams cause extended lead times | +| Phase 2 | Improving — Agile practices introduced, version control helps, but manual interventions persist | +| Phase 3 | Shorter — automated builds and tests speed up delivery, security integrated earlier | +| Phase 4 | Significantly reduced — CI pipeline and automated processes enable rapid iteration | +| Phase 5 | Less than one hour — elite performance, on-demand deployment capability | + +## Elite Performance Benchmark +According to DORA research: +- **Elite performers**: Less than one hour lead time +- **High performers**: Between one week and one month +- **Medium performers**: Between one month and six months +- **Low performers**: More than six months + +## Components of Lead Time +1. **Coding time** — Time to implement the change +2. **Build time** — Automated compilation and artifact generation +3. **Test time** — Unit, integration, and acceptance tests +4. **Review time** — Code review and approval processes +5. **Deployment time** — Time to deploy through pipeline stages +6. **Queuing time** — Time waiting for resources or approvals + +## How to Improve Lead Time +- Automate the entire build-test-deploy pipeline +- Reduce batch sizes (smaller changes deploy faster) +- Implement robust automated testing to reduce review burden +- Eliminate manual approvals that create bottlenecks +- Use feature flags to decouple deployment from release +- Improve developer tooling and local build times + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/DORA-Metrics]] +- [[concepts/Continuous-Deployment]] +- [[concepts/Time-to-Market]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/MTTA.md b/wiki/concepts/MTTA.md new file mode 100644 index 00000000..fb98f765 --- /dev/null +++ b/wiki/concepts/MTTA.md @@ -0,0 +1,71 @@ +# MTTA (Mean Time to Acknowledge) + +## Definition +MTTA (Mean Time to Acknowledge) is the average time from when a problem is detected to when a team member actively begins working on resolving it. It measures the speed of human response after an alert is triggered. + +MTTA is a component of MTTR, sitting between MTTD and Mean Time to Repair. + +## Why MTTA Matters + +MTTA measures: +- On-call response effectiveness +- Alert severity and clarity +- Incident management process efficiency +- Team availability and readiness + +A short MTTA ensures that once a problem is detected, the recovery process begins promptly. + +## Across DevOps Maturity Levels + +| Maturity | Acknowledgment Capability | +|----------|--------------------------| +| Phase 1 | Long MTTA — unclear ownership, manual processes, reactive responses | +| Phase 2 | Improving — essential monitoring alerts team when issues affect users, ops staff manually intervene | +| Phase 3 | Better process — ops team adopts automation techniques, but monitoring unchanged | +| Phase 4 | Efficient acknowledgment — continuous monitoring with clear escalation paths, root cause analysis starts quickly | +| Phase 5 | Rapid — high collaboration, rapid data-driven decision-making, minimal customer interruptions | + +## Key Factors Affecting MTTA + +### On-Call Practices +- Clear on-call rotations +- Fast escalation policies +- Adequate staffing levels +- Compensation for on-call duty + +### Alert Quality +- Actionable alerts (not noise) +- Clear severity levels +- Sufficient context in alerts +- Pre-configured runbook links + +### Incident Response Process +- Clear ownership and accountability +- Pre-defined roles (incident commander, communications lead) +- Escalation procedures +- Communication channels + +## MTTA as Part of MTTR + +``` +MTTR = MTTD + MTTA + Mean Time to Repair +``` + +All three components must be optimized for minimal MTTR. Even with perfect MTTD (instant detection), a long MTTA will result in poor overall recovery times. + +## How to Improve MTTA +- Implement PagerDuty, Opsgenie, or similar incident management tools +- Create clear escalation policies +- Practice incident response with regular game days +- Improve alert quality to reduce noise and fatigue +- Ensure adequate on-call coverage +- Pre-build runbooks for common incidents + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/MTTR]] +- [[concepts/MTTD]] +- [[concepts/DORA-Metrics]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/MTTD.md b/wiki/concepts/MTTD.md new file mode 100644 index 00000000..b91967b8 --- /dev/null +++ b/wiki/concepts/MTTD.md @@ -0,0 +1,66 @@ +# MTTD (Mean Time to Detect) + +## Definition +MTTD (Mean Time to Detect) is the average time required to identify that a problem or failure has occurred in a system. It measures the effectiveness of monitoring, alerting, and observability practices. + +MTTD is a component of MTTR and represents the first phase of incident response. + +## Why MTTD Matters + +A short MTTD means: +- Failures are caught before they cascade into larger outages +- Customer impact is minimized +- The team can begin recovery faster +- Root cause analysis starts sooner + +Long MTTD means: +- Problems can escalate undetected +- User experience degrades for longer periods +- More customers are affected +- Root cause analysis becomes harder as the incident grows + +## Across DevOps Maturity Levels + +| Maturity | Detection Capability | +|----------|---------------------| +| Phase 1 | Long MTTD — outages reported by users, no proactive monitoring, reactive approach | +| Phase 2 | Better MTTD — essential monitoring tools alert teams as soon as issues affect users | +| Phase 3 | Improved detection — automated monitoring continues, security scans added earlier in pipeline | +| Phase 4 | Continuous monitoring — tracks system health for early problem detection and root cause analysis | +| Phase 5 | Minimal MTTD — max uptime with high collaboration and continuous monitoring, no customer interruptions | + +## Key Practices for Low MTTD + +### Monitoring & Alerting +- Comprehensive application performance monitoring (APM) +- Infrastructure monitoring +- Log aggregation and analysis +- Real-user monitoring (RUM) +- Synthetic monitoring + +### Alerting Best Practices +- Meaningful alert thresholds (avoid alert fatigue) +- Alert routing to appropriate on-call staff +- Clear alert context for rapid triage +- Correlation of related alerts + +### Observability +- Structured logging +- Distributed tracing +- Metrics dashboards +- Error tracking + +## MTTD vs Other Metrics +- **MTTR**: MTTD is a component of MTTR (MTTR = MTTD + MTTA + Mean Time to Repair) +- **Availability**: High availability depends partly on short MTTD +- **Change Failure Rate**: Fewer failures reaching production reduces MTTD pressure + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/MTTR]] +- [[concepts/MTTA]] +- [[concepts/DORA-Metrics]] +- [[concepts/APM]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/MTTR.md b/wiki/concepts/MTTR.md new file mode 100644 index 00000000..0a7b6132 --- /dev/null +++ b/wiki/concepts/MTTR.md @@ -0,0 +1,66 @@ +# MTTR (Mean Time to Recovery) + +## Definition +MTTR (Mean Time to Recovery) is the average time required to recover from a failure — from the moment a failure is detected to the moment service is fully restored to normal operation. + +MTTR is one of the four core **DORA metrics** used to measure DevOps performance. + +## Key Components + +MTTR can be broken down into: +1. **MTTD (Mean Time to Detect)** — Average time to identify a problem +2. **MTTA (Mean Time to Acknowledge)** — Average time to acknowledge and begin addressing a problem +3. **Mean Time to Repair/Restore** — Actual time to fix and restore service +4. **MTTR = MTTD + MTTA + Mean Time to Repair** + +## Across DevOps Maturity Levels + +| Maturity | Detection & Recovery Capability | +|----------|--------------------------------| +| Phase 1 | Long MTTD and MTTR — outages reported by users (reactive), no proactive monitoring | +| Phase 2 | Better MTTD — essential monitoring tools alert teams when issues affect users | +| Phase 3 | Improved — security scans integrated earlier, but monitoring unchanged from Phase 2 | +| Phase 4 | Continuous monitoring tracks system health, enabling early detection and root cause analysis | +| Phase 5 | Max uptime — high collaboration, rapid data-driven decision-making, minimal customer interruptions | + +## MTTD and MTTA + +### MTTD (Mean Time to Detect) +- The average time to identify that a problem has occurred +- Lower is better — faster detection means faster recovery +- Requires: comprehensive monitoring, alerting, and observability + +### MTTA (Mean Time to Acknowledge) +- The average time from detection to someone actively working on the issue +- Includes time to notify on-call staff, triage, and begin investigation +- Requires: clear incident response processes and on-call coverage + +## Elite Performance Benchmark (DORA) +- **Elite performers**: MTTR < 1 hour +- Short MTTR indicates: + - Robust incident detection and alerting + - Clear incident response processes + - Well-practiced on-call procedures + - Effective automation for rollback and recovery + - Good observability and debugging tools + +## How to Reduce MTTR +- Implement comprehensive monitoring and alerting +- Practice chaos engineering and incident simulations +- Automate rollback procedures +- Use feature flags to isolate failures +- Maintain runbooks for common failures +- Foster blameless post-mortem culture +- Use observability tools for faster root cause analysis + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/DORA-Metrics]] +- [[concepts/MTTD]] +- [[concepts/MTTA]] +- [[concepts/Error-Budget]] +- [[concepts/Change-Failure-Rate]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/Multi-Cloud-Strategy.md b/wiki/concepts/Multi-Cloud-Strategy.md new file mode 100644 index 00000000..af661a2c --- /dev/null +++ b/wiki/concepts/Multi-Cloud-Strategy.md @@ -0,0 +1,163 @@ +--- +title: Multi-Cloud Strategy +source: https://www.bacancytechnology.com/blog/cloud-maturity-model +tags: [Cloud, Multi-Cloud, Strategy, Hybrid-Cloud, Cloud-Adoption] +--- + +# Multi-Cloud Strategy + +## Overview + +**Multi-Cloud Strategy** refers to an organization's use of multiple cloud computing services from different providers — combining public, private, and hybrid cloud environments to optimize flexibility, performance, and cost-efficiency. + +## Relationship with Cloud Maturity Model + +The Cloud Maturity Model addresses multi-cloud at multiple levels: + +### Level 2 (Repeatable, Opportunistic) +Organizations at this level consider diverse deployment models (private, hybrid, multi-cloud) to address: +- Security and compliance worries +- Need for flexibility in workload placement + +### Level 4 (Measured) +Companies at Level 4 adeptly use various cloud platforms and flexibly move workloads between them — this represents the **optimized state** of multi-cloud capability. + +### Level 5 (Optimized) +The highest maturity level describes an organization that operates with an open and interoperable cloud environment across multiple providers. + +## Key Benefits of Multi-Cloud + +1. **Avoid Vendor Lock-in** — Freedom to choose best-of-breed services from each provider +2. **Optimize Costs** — Select most cost-effective provider for each workload +3. **Improve Resilience** — Redundancy across providers reduces single-point-of-failure risk +4. **Compliance Flexibility** — Match data residency requirements with appropriate provider/region +5. **Leverage Best Services** — Use unique capabilities from each cloud provider + +## Multi-Cloud vs Related Concepts + +| Concept | Description | +|---------|-------------| +| **Multi-Cloud** | Using multiple cloud services from different providers (can be all public, all private, or mix) | +| **Hybrid Cloud** | Combining private/public clouds with orchestration between them | +| **Poly-Cloud** | Strategic selection of best services from multiple providers | +| **Cross-Cloud** | Moving workloads seamlessly across cloud providers | + +## Types of Cloud Maturity Models for Multi-Cloud + +The Cloud Maturity Model document references: + +| Model | Focus | +|-------|-------| +| **Public Cloud Maturity Model** | Leveraging external cloud services for scalability and cost-efficiency | +| **Private Cloud Maturity Model** | Internal infrastructure for control and compliance | +| **Hybrid Cloud Maturity Model** | Integrating public and private clouds for flexibility | + +## Challenges in Multi-Cloud Adoption + +1. **Complexity Management** — Managing multiple platforms, tools, and interfaces +2. **Data Consistency** — Ensuring data synchronization across providers +3. **Security Coordination** — Unified security policies across diverse environments +4. **Cost Visibility** — Tracking and optimizing spending across providers +5. **Skills Requirements** — Teams need expertise across multiple cloud platforms +6. **Interoperability** — Ensuring seamless integration between providers + +## Best Practices for Multi-Cloud + +1. **Establish Clear Governance** — Define roles, responsibilities, and decision-making across providers +2. **Standardize where Possible** — Use common APIs, formats, and management tools +3. **Implement FinOps** — Cloud financial management across all providers +4. **Develop Cross-Cloud Skills** — Train teams on multiple platforms +5. **Use Cloud-Agnostic Tools** — Employ tools that work across providers (Kubernetes, Terraform, etc.) + +## Related Concepts + +- [[Cloud-Maturity-Model]] +- [[Cloud-Adoption-Strategy]] +- [[Cloud-Native]] +- [[FinOps]] +- [[Hybrid-Cloud]] + +## ROI Maximization Framework + +Based on [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi]]: + +### Quantified Benefits +- **30%** reduction in operations costs after optimizing resources and negotiating favorable prices (Forrester) +- **78%** of businesses have workloads deployed in more than three public clouds for better agility and cost savings +- **86%** of companies intend to adopt multi-cloud approach by end of 2024 + +### ROI Maximization Paths + +1. **Cost Reduction** + - Avoid high single-cloud pricing structures with one-size-fits-all models + - Drive hard bargains for better rates by leveraging multi-vendor competition + - Prevent paying for unnecessary resources through cross-cloud optimization + +2. **Resource Optimization** + - Allocate workloads to best-suited provider per task (e.g., Google Cloud for ML, AWS/Azure for general infra) + +3. **Efficiency Gains** + - Create tailored cloud architecture for specific needs + - Reduce downtime, improve performance + - Faster deployment times, better availability + +4. **Flexibility in Scaling** + - Dynamically allocate resources based on demand + - Expand on one provider during spikes without capacity limits on all providers + - Avoid overpaying for unused capacity + +5. **Better Risk Management** + - Eliminate single-provider dependency + - Other providers step in when one goes down + +## Implementation Roadmap + +Based on [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi]], a 4-step implementation approach: + +### Step 1: Assess Your Needs +- Identify goals: resiliency, cost optimization, or scale +- Budget analysis: initial and ongoing costs +- Resource requirements assessment + +### Step 2: Choose Right Providers +- Align services with needs (AWS for infra, Google Cloud for analytics, Azure for AI) +- Evaluate features, security, compliance, cost, performance + +### Step 3: Integrate and Manage +- Adopt multi-cloud management tools (Kubernetes, Terraform) +- Ensure data interoperability, avoid data silos + +### Step 4: Monitor and Optimize +- Track resource usage (CloudHealth, Datadog) +- Implement cost-saving measures through workload optimization + +## Industry Use Cases + +### E-Commerce +- High availability during peak seasons (Black Friday, Cyber Monday) +- Scale resources across providers for traffic spikes +- Fast customer load times + +### Healthcare +- HIPAA-compliant patient data storage +- Distribute data across compliant cloud platforms +- Reduce costs from single-cloud dependency + +### Finance +- Stringent regulatory requirements compliance +- Use best security features of each provider +- Reduce risk and vendor lock-in for better SLAs and ROI + +## Challenges and Proven Solutions + +| Challenge | Solution | +|-----------|---------| +| Integration Complexity | Kubernetes, Terraform, cloud APIs | +| Security Risks | Centralized IAM, end-to-end encryption | +| Lack of Expertise | Upskilling, hiring experts, managed providers | + +## Sources + +- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] +- [[sources/public-vs-private-vs-hybrid-cloud-differences-explained.md]] +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/concepts/ROI.md b/wiki/concepts/ROI.md new file mode 100644 index 00000000..90171cec --- /dev/null +++ b/wiki/concepts/ROI.md @@ -0,0 +1,55 @@ +--- +title: ROI (Return on Investment) +tags: [Business, Finance, Cloud] +--- + +# ROI (Return on Investment) + +## Overview + +**ROI**（投资回报率）是衡量投资效益的核心财务指标，在云计算领域，多云策略的 ROI 分析是评估云投资成功与否的关键。多云策略通过成本优化、性能提升和风险降低等多个维度影响业务 ROI。 + +## Cloud ROI Calculation + +### Basic Formula +``` +ROI = (Net Benefits / Total Costs) × 100% + = ((Cost Savings + Revenue Gains) - Implementation Costs) / Total Costs × 100% +``` + +### Cloud-Specific ROI Components + +| Category | Benefits | Costs | +|----------|----------|-------| +| **Cost Savings** | 减少基础设施 CapEx、降低运维成本、减少停机损失 | 迁移成本、培训成本 | +| **Revenue Gains** | 更快推向市场、提升客户体验、支持新业务模式 | 持续订阅费用 | +| **Risk Reduction** | 减少单点故障、业务连续性提升 | 安全合规成本 | + +## Multi-Cloud ROI Drivers + +1. **Cost Reduction**: 多云竞争性定价带来 30% 运营成本降低（Forrester） +2. **Resource Optimization**: 工作负载分配到最适合的提供商，提升效率 +3. **Risk Mitigation**: 避免单一供应商故障导致的大规模业务中断 +4. **Scalability Gains**: 弹性扩展能力避免收入损失（旺季无法服务） +5. **Innovation Access**: 利用最新云服务加速产品创新 + +## ROI Timeline + +| Phase | Typical Timeline | Focus | +|-------|-----------------|-------| +| Initial Assessment | 1-3 months | 成本基线、ROI 模型建立 | +| Migration | 3-12 months | 渐进式迁移、持续优化 | +| Optimization | Ongoing | FinOps 实践、持续改进 | +| Full Value | 12-24 months | 实现预期 ROI | + +## Related Concepts + +- [[Cost Optimization]] +- [[Multi-Cloud Strategy]] +- [[FinOps]] +- [[Risk Mitigation]] +- [[Scalability]] + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/concepts/Risk-Mitigation.md b/wiki/concepts/Risk-Mitigation.md new file mode 100644 index 00000000..700f0d87 --- /dev/null +++ b/wiki/concepts/Risk-Mitigation.md @@ -0,0 +1,62 @@ +--- +title: Risk Mitigation +tags: [Cloud, Strategy, Risk-Management] +--- + +# Risk Mitigation + +## Overview + +**Risk Mitigation**（风险缓解）指通过策略、流程和技术手段降低潜在风险对业务影响的过程。在多云环境中，风险缓解是核心驱动力之一——通过跨多个提供商分配工作负载，消除单点故障，提高业务连续性。 + +## Cloud Risk Categories + +### 1. Provider Risks +| Risk | Description | Mitigation | +|------|-------------|------------| +| 服务中断 (Outage) | 单一提供商故障导致全局不可用 | 跨提供商冗余部署 | +| 价格变动 | 提供商大幅涨价影响成本 | 多提供商竞争性定价 | +| 服务终止 | 提供商停止服务 | 保持迁移能力 | +| 合规变化 | 提供商合规认证失效 | 多提供商合规组合 | + +### 2. Security Risks +| Risk | Description | Mitigation | +|------|-------------|------------| +| 数据泄露 | 安全漏洞导致数据外泄 | 多层安全策略 | +| DDoS 攻击 | 大规模网络攻击 | CDN + 多区域部署 | +| 内部威胁 | 员工不当操作 | 最小权限 + 审计 | + +### 3. Operational Risks +| Risk | Description | Mitigation | +|------|-------------|------------| +| 技能缺口 | 团队技能单一 | 跨平台培训 | +| 复杂性 | 多云管理复杂度 | 统一管理工具 | + +## Multi-Cloud Risk Mitigation Framework + +1. **Workload Distribution**: 关键工作负载跨 2-3 个提供商部署 +2. **Data Replication**: 跨提供商实时数据复制 +3. **Automated Failover**: 故障自动切换到备用提供商 +4. **Disaster Recovery (DR)**: 多云 DR 架构确保业务连续性 +5. **Contractual Protections**: SLA 条款和退出条款保护 + +## Risk Metrics + +| Metric | Description | Target | +|--------|-------------|--------| +| RTO (Recovery Time Objective) | 恢复时间目标 | < 4 hours | +| RPO (Recovery Point Objective) | 数据恢复点目标 | < 1 hour | +| SLA Uptime | 服务可用性 | > 99.9% | +| Mean Time to Recovery | 平均恢复时间 | < 30 minutes | + +## Related Concepts + +- [[High Availability]] +- [[Disaster Recovery]] +- [[Multi-Cloud Strategy]] +- [[Cloud Security]] +- [[Incident Management]] + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/concepts/Rollback-Rate.md b/wiki/concepts/Rollback-Rate.md new file mode 100644 index 00000000..05f76bd4 --- /dev/null +++ b/wiki/concepts/Rollback-Rate.md @@ -0,0 +1,74 @@ +# Rollback Rate + +## Definition +Rollback Rate is the proportion of deployments that are reverted (rolled back) to a previous stable version after being deployed to production. It measures how often deployments fail to the point where reverting becomes necessary. + +The DevOps Maturity Model explicitly lists Rollback Rate as one of the metrics for measuring DevOps maturity. + +## Why Rollback Rate Matters + +A high rollback rate indicates: +- Deployment quality issues +- Insufficient testing before deployment +- Gap between staging and production environments +- Unstable or risky deployment processes + +A low rollback rate indicates: +- High confidence in the deployment pipeline +- Comprehensive pre-production testing +- Stable deployment processes + +## Across DevOps Maturity Levels + +| Maturity | Rollback Rate Characteristic | +|----------|------------------------------| +| Phase 1 | High rollback rate — manual deployments, no automated testing, siloed teams, manual infrastructure | +| Phase 2 | Improving — automation reduces some risks, but manual interventions still cause rollbacks | +| Phase 3 | Lower — automated infrastructure and security scans reduce failures before deployment | +| Phase 4 | Reduced — performance testing, immutable infrastructure, dependency vulnerability management | +| Phase 5 | Minimal — zero human intervention, real-time decisions, rollback automation for fast recovery | + +## Relationship with Other Metrics + +### Rollback Rate and Change Failure Rate +- **Change Failure Rate**: All deployments that cause failures (regardless of rollback) +- **Rollback Rate**: Only deployments where the team explicitly chose to roll back + +A high CFR but low Rollback Rate could mean failures were fixed without rollback. A low CFR but high Rollback Rate suggests teams are overly cautious. + +### Rollback Rate and MTTR +- Rollback is often a strategy for reducing MTTR +- Fast rollback mechanisms enable quick recovery +- Organizations with mature CI/CD pipelines have both low rollback rates AND fast rollback capabilities + +## How to Reduce Rollback Rate + +### Technical Strategies +- Comprehensive pre-production testing +- Feature flags for gradual rollouts +- Canary deployments (route small % of traffic to new version) +- Blue-green deployments +- Comprehensive observability to detect issues before users notice +- A/B testing in production + +### Process Improvements +- Small batch deployments to limit blast radius +- Strict deployment criteria (all tests green, no open severity-1 bugs) +- Deployment freeze periods for critical systems +- Change advisory board for high-risk changes + +### Cultural Factors +- Psychological safety to admit when a deployment is failing +- Clear criteria for when to rollback vs fix-forward +- Blameless post-mortems to learn from rollbacks +- On-call engineers empowered to make rollback decisions + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/Change-Failure-Rate]] +- [[concepts/MTTR]] +- [[concepts/DORA-Metrics]] +- [[concepts/Continuous-Deployment]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/Scalability.md b/wiki/concepts/Scalability.md new file mode 100644 index 00000000..01a5b108 --- /dev/null +++ b/wiki/concepts/Scalability.md @@ -0,0 +1,72 @@ +# Scalability + +## Definition +Scalability is a system's ability to handle increased load (users, traffic, data volume) without experiencing performance degradation. The DevOps Maturity Model explicitly lists Scalability as a key metric for measuring DevOps maturity. + +## Types of Scalability + +### Vertical Scaling (Scale-Up) +- Adding more resources (CPU, RAM, storage) to existing servers +- Simpler to implement but has hardware limits +- Often a Phase 1-2 approach + +### Horizontal Scaling (Scale-Out) +- Adding more servers to handle load +- More complex but theoretically unlimited +- Characteristic of Phase 3+ maturity + +### Auto-Scaling +- Automatically adjusting capacity based on demand +- Cloud-native approach enabled by IaC +- Characteristic of Phase 4-5 maturity + +## Across DevOps Maturity Levels + +| Maturity | Scalability Approach | +|----------|---------------------| +| Phase 1 | Manual scaling — servers receive individual attention, unable to respond quickly to load changes | +| Phase 2 | Basic automation — version control for configurations, but manual scaling still required | +| Phase 3 | Automated infrastructure — provisioning becomes repeatable and reliable | +| Phase 4 | Auto-scaling — immutable infrastructure, load testing ensures readiness for production scale | +| Phase 5 | Full elasticity — infrastructure scales automatically, minimal manual effort | + +## Key Scalability Practices in DevOps + +### Infrastructure as Code (IaC) +IaC enables automated and repeatable infrastructure provisioning, which is foundational for scalability. Without IaC, scaling requires manual intervention for each new resource. + +### Containerization and Orchestration +- Docker containers package applications consistently +- Kubernetes or similar orchestrators manage container lifecycles +- Enables horizontal scaling with minimal overhead + +### Cloud-Native Architecture +- Microservices allow independent scaling of components +- Serverless (Lambda, Cloud Functions) scales automatically +- Managed services offload operational burden + +### Load Testing +- Phase 4 maturity requires performance and load testing before production deployment +- Testing ensures systems are ready for production scale +- Identifies bottlenecks before they affect users + +## Scalability and Business Impact + +| Scalability Aspect | Business Impact | +|-------------------|----------------| +| Handle traffic spikes | No lost revenue during peak events | +| Geographic expansion | Support new markets without redesign | +| Data growth | Store and process more data over time | +| Feature expansion | New features don't degrade existing functionality | +| Cost optimization | Scale down during low demand to save costs | + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/Infrastructure-as-Code]] +- [[concepts/Cloud-Native]] +- [[concepts/High-Availability]] +- [[concepts/Continuous-Deployment]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/Time-to-Market.md b/wiki/concepts/Time-to-Market.md new file mode 100644 index 00000000..b1dbfaf1 --- /dev/null +++ b/wiki/concepts/Time-to-Market.md @@ -0,0 +1,63 @@ +# Time-to-Market + +## Definition +Time-to-Market (TTM) is the period from the initial concept or idea to the product's launch and availability to customers. It measures how quickly an organization can translate business ideas into customer value. + +## Role in DevOps Maturity + +Time-to-Market is a key metric for evaluating DevOps maturity. The DevOps Maturity Model explicitly identifies TTM as one of the metrics organizations should track. + +| Maturity | TTM Characteristic | +|----------|-------------------| +| Phase 1 | Very long — waterfall approach, milestone-based releases, reactive to market changes | +| Phase 2 | Shortening — Agile practices, focus on business value, faster feedback | +| Phase 3 | Significantly reduced — automated infrastructure, more frequent deployments | +| Phase 4 | Competitive — MVP approach, tech debt management, rapid iteration | +| Phase 5 | Minimal — multiple deployments per day, rapid market response | + +## Factors Affecting Time-to-Market + +### Development Process +- Agile vs waterfall methodology +- Automation of development, testing, and deployment +- Quality of code review processes +- Batch size of changes + +### Organizational Structure +- Cross-functional team collaboration +- Silos between development, operations, and security +- Decision-making speed +- Cultural alignment + +### Technical Infrastructure +- CI/CD pipeline maturity +- Infrastructure as Code adoption +- Environment provisioning speed +- Test automation coverage + +### Market Conditions +- Competitive landscape +- Customer demand speed +- Regulatory requirements + +## Relationship with Other Metrics +- **Lead Time for Changes** — Sub-component of TTM; measures the technical delivery speed +- **Deployment Frequency** — Higher frequency typically correlates with faster TTM +- **MTTR** — Faster recovery from failures reduces time lost during incidents + +## DevOps Benefits to TTM +- CI/CD pipelines reduce manual handoffs +- Automation eliminates repetitive tasks +- Continuous feedback enables rapid iteration +- Smaller batch sizes enable faster releases +- DevSecOps integrates security without slowing down delivery + +## Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] +- [[sources/cloud-devop-maturity-guideline.md]] + +## Related Concepts +- [[concepts/Lead-Time]] +- [[concepts/DORA-Metrics]] +- [[concepts/Continuous-Deployment]] +- [[concepts/DevOps-Maturity]] diff --git a/wiki/concepts/Vendor-Lock-In.md b/wiki/concepts/Vendor-Lock-In.md new file mode 100644 index 00000000..d5bb7f8a --- /dev/null +++ b/wiki/concepts/Vendor-Lock-In.md @@ -0,0 +1,56 @@ +--- +title: Vendor Lock-In +tags: [Cloud, Risk, Strategy] +--- + +# Vendor Lock-In + +**Vendor Lock-In** refers to the situation where a customer becomes dependent on a single cloud provider for products and services, making it difficult and costly to switch to another provider. + +## Overview + +Vendor lock-in is one of the primary concerns when adopting cloud services. Organizations invest in provider-specific tools, APIs, and infrastructure that may not be portable to other platforms. + +## Why It Happens + +1. **Proprietary APIs** — Provider-specific interfaces that require code changes to migrate +2. **Custom Data Formats** — Formats that only work with that provider's services +3. **Discounting Incentives** — Long-term contracts with committed spending +4. **Skill Development** — Teams trained on specific provider's tools +5. **Integration Dependencies** — Deep coupling with provider's ecosystem + +## Multi-Cloud as Mitigation + +[[Multi-Cloud-Strategy]] directly addresses vendor lock-in by: + +- Distributing workloads across multiple providers +- Using cloud-agnostic tools (Kubernetes, Terraform) +- Standardizing on open APIs and formats +- Negotiating favorable contracts with competition + +## Signs of Lock-In Risk + +- Difficulty estimating migration costs to another provider +- Most applications tightly coupled to single provider's services +- Team has limited skills across multiple cloud platforms +- Long-term committed spending with one provider +- Provider-specific data formats in use + +## Mitigation Strategies + +1. **Adopt Cloud-Agnostic Tools** — Use Kubernetes, Terraform, open-source solutions +2. **Design for Portability** — Abstract provider-specific code into interfaces +3. **Multi-Cloud Architecture** — Distribute critical workloads across providers +4. **Standardize Data Formats** — Use open, portable formats where possible +5. **Develop Cross-Cloud Skills** — Train teams on multiple platforms + +## Related Concepts + +- [[Multi-Cloud-Strategy]] — Primary mitigation strategy +- [[Cloud-Maturity-Model]] — Level 4-5 organizations effectively avoid lock-in +- [[Cloud-Native]] — Portable architectures reduce lock-in +- [[FinOps]] — Helps evaluate cost of lock-in vs. flexibility + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/concepts/cloud-migration.md b/wiki/concepts/cloud-migration.md new file mode 100644 index 00000000..ab5e4c88 --- /dev/null +++ b/wiki/concepts/cloud-migration.md @@ -0,0 +1,41 @@ +--- +title: Cloud Migration +--- + +# Cloud Migration + +**Cloud Migration** is the process of moving data, applications, and other business elements from an on-premises infrastructure to a cloud-based environment, or between cloud environments. + +## Common Misconception + +> **Myth**: Migration to the cloud is too complex and risky. + +> **Reality**: Cloud migration can be smooth with proper planning. + +## Migration Strategies + +1. **Phased Migration**: Incrementally move workloads in stages to minimize risk +2. **Lift-and-Shift (Rehosting)**: Move applications without modifications +3. **Replatforming**: Make minimal changes to leverage cloud capabilities +4. **Refactoring/Re-architecting**: Redesign applications for cloud-native features +5. **Hybrid Cloud**: Keep some workloads on-premises while moving others to the cloud +6. **Multi-Cloud**: Distribute workloads across multiple cloud providers + +## Key Success Factors + +- Comprehensive assessment and planning +- Phased approach to minimize disruption +- Professional cloud migration services +- Robust testing and validation at each stage +- Clear rollback procedures + +## Related Concepts + +- [[Cloud Computing]] +- [[High Availability]] +- [[Disaster Recovery]] +- [[Infrastructure as Code]] + +## Sources + +- [[The Myths and Misconceptions About Cloud Computing (LinkedIn)|the-myths-and-misconceptions-about-cloud-computing-linkedin]] diff --git a/wiki/concepts/cloud-security.md b/wiki/concepts/cloud-security.md new file mode 100644 index 00000000..4c8e98a0 --- /dev/null +++ b/wiki/concepts/cloud-security.md @@ -0,0 +1,44 @@ +--- +title: Cloud Security +--- + +# Cloud Security + +**Cloud Security** encompasses the technologies, policies, controls, and services that protect cloud-based data, applications, and infrastructure from unauthorized access, data breaches, and other cyber threats. + +## Common Misconception + +> **Myth**: Cloud computing is not secure. + +> **Reality**: Cloud security is often more robust than on-premises solutions. + +## Why Cloud Security Often Exceeds On-Premises + +- **Massive Investment**: Leading cloud providers (AWS, Azure, GCP) invest billions annually in security infrastructure +- **Encryption**: Data encrypted at rest and in transit by default +- **Multi-Factor Authentication (MFA)**: Built-in identity and access management +- **Compliance Certifications**: ISO 27001, HIPAA, GDPR, SOC 2, and more +- **Automated Security Updates**: Continuous patching without user intervention +- **24/7 Monitoring**: Dedicated security operations centers monitoring threats round-the-clock +- **Advanced Firewalls**: Managed firewall services with DDoS protection + +## Core Security Components + +| Component | Description | +|-----------|-------------| +| Identity & Access Management (IAM) | Role-based access control, MFA, least privilege | +| Encryption | AES-256 at rest, TLS 1.3 in transit | +| Network Security | VPCs, Security Groups, WAF, DDoS protection | +| Compliance | Automated compliance reporting and auditing | +| Threat Detection | AI/ML-powered anomaly detection and SIEM | + +## Related Concepts + +- [[Cloud Computing]] +- [[High Availability]] +- [[Multi-Cloud Strategy]] +- [[DevSecOps]] + +## Sources + +- [[The Myths and Misconceptions About Cloud Computing (LinkedIn)|the-myths-and-misconceptions-about-cloud-computing-linkedin]] diff --git a/wiki/concepts/high-availability.md b/wiki/concepts/high-availability.md new file mode 100644 index 00000000..16ef61c9 --- /dev/null +++ b/wiki/concepts/high-availability.md @@ -0,0 +1,39 @@ +--- +title: High Availability (Cloud) +--- + +# High Availability (Cloud) + +**High Availability (HA)** in cloud computing refers to systems designed to operate continuously without failure, typically by eliminating single points of failure and distributing workloads across redundant infrastructure. + +## Common Misconception + +> **Myth**: Cloud performance is unreliable. + +> **Reality**: Cloud providers offer high availability and redundancy. + +## Key HA Characteristics in Cloud + +- **Service Level Agreements (SLAs)**: Major cloud providers guarantee uptime exceeding **99.99%** +- **Redundant Infrastructure**: Data and services are replicated across multiple geographic regions and availability zones +- **Automated Failover**: Automatic switching to backup systems when primary systems fail +- **Global Data Center Distribution**: Workloads distributed worldwide for geographic resilience +- **Load Balancing**: Traffic distributed across multiple healthy instances + +## Benefits + +- Minimized downtime and business disruption +- Improved user experience and reliability +- Reduced financial impact of outages +- Better disaster recovery posture + +## Related Concepts + +- [[Cloud Computing]] +- [[Disaster Recovery]] +- [[Cloud Migration]] +- [[Multi-Cloud Strategy]] + +## Sources + +- [[The Myths and Misconceptions About Cloud Computing (LinkedIn)|the-myths-and-misconceptions-about-cloud-computing-linkedin]] diff --git a/wiki/entities/AWS.md b/wiki/entities/AWS.md new file mode 100644 index 00000000..25b11c8c --- /dev/null +++ b/wiki/entities/AWS.md @@ -0,0 +1,40 @@ +--- +title: AWS (Amazon Web Services) +tags: [Cloud, Provider, Public-Cloud] +--- + +# AWS (Amazon Web Services) + +**AWS** is Amazon's cloud computing platform, providing a broad set of infrastructure and application services across 200+ fully featured services. + +## Overview + +AWS is one of the three major public cloud providers (alongside Azure and Google Cloud), offering the most extensive range of services. + +## Key Services Referenced + +| Category | Services | +|----------|----------| +| Compute | EC2, Lambda | +| Storage | S3, EBS | +| Database | RDS, DynamoDB, Aurora | +| AI/ML | SageMaker, Bedrock | +| Analytics | Redshift, Athena | +| Networking | VPC, Route 53, CloudFront | + +## Multi-Cloud Context + +AWS is commonly used alongside Azure and Google Cloud in multi-cloud strategies: +- **General infrastructure** — Often primary compute and storage provider +- **Enterprise integration** — Strong Active Directory and enterprise app ecosystem +- **Market position** — Largest market share among cloud providers + +## Related Concepts + +- [[Multi-Cloud-Strategy]] — AWS as one of multiple providers +- [[Cloud-Native]] — Building on AWS-native services +- [[FinOps]] — Managing AWS costs + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/entities/Azure.md b/wiki/entities/Azure.md new file mode 100644 index 00000000..5c0d3ea2 --- /dev/null +++ b/wiki/entities/Azure.md @@ -0,0 +1,40 @@ +--- +title: Azure (Microsoft Azure) +tags: [Cloud, Provider, Public-Cloud] +--- + +# Azure (Microsoft Azure) + +**Microsoft Azure** is a cloud computing platform operated by Microsoft, providing a broad range of services for application and workload hosting. + +## Overview + +Azure is one of the three major public cloud providers, particularly strong in enterprise environments with Microsoft ecosystem integration. + +## Key Services Referenced + +| Category | Services | +|----------|----------| +| Compute | Virtual Machines, Azure Functions | +| Storage | Blob Storage, Azure Files | +| Database | Azure SQL, Cosmos DB | +| AI/ML | Azure AI, Azure OpenAI Service | +| Analytics | Synapse, Databricks | +| Enterprise | Active Directory, Microsoft 365 integration | + +## Multi-Cloud Context + +Azure is commonly used alongside AWS and Google Cloud in multi-cloud strategies: +- **Enterprise workloads** — Strong Windows Server and SQL Server integration +- **AI services** — Azure OpenAI Service for enterprise AI applications +- **Hybrid cloud** — Deep integration with on-premises Windows environments + +## Related Concepts + +- [[Multi-Cloud-Strategy]] — Azure as one of multiple providers +- [[Cloud-Native]] — Building on Azure-native services +- [[FinOps]] — Managing Azure costs + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/entities/Cloud-Maturity-Model.md b/wiki/entities/Cloud-Maturity-Model.md new file mode 100644 index 00000000..61a00644 --- /dev/null +++ b/wiki/entities/Cloud-Maturity-Model.md @@ -0,0 +1,95 @@ +--- +title: Cloud Maturity Model (CMM) +source: https://www.bacancytechnology.com/blog/cloud-maturity-model +tags: [Cloud, Maturity, Framework, Cloud-Adoption, Enterprise] +--- + +# Cloud Maturity Model (CMM) + +## Overview + +The **Cloud Maturity Model** (CMM) is a structured framework for evaluating an organization's cloud adoption readiness. Developed and described by the Open Alliance for Cloud Adoption (OACA), it provides a systematic approach for organizations of all sizes and experience levels to assess their current cloud state, identify gaps, and plan their cloud transformation journey. + +## Key Definition + +The OACA describes CMM as a framework that: +- Assists organizations in identifying tailored solutions for adopting cloud or hybrid IT environments +- Evaluates organizations' readiness for adopting the cloud +- Helps assess their current use of cloud services +- Sets future goals for developing a cloud migration strategy +- Conducts GAP analysis +- Identifies areas for improving cloud infrastructure based on business objectives + +## The 5 Maturity Levels + +| Level | Name | Description | +|-------|------|-------------| +| **Level 0** | Legacy | No cloud usage, relies solely on outdated systems | +| **Level 1** | Initial Readiness (Ad hoc) | Some cloud experience, primarily for SaaS or specific business units, no clear strategy | +| **Level 2** | Repeatable, Opportunistic | Established procedures, cloud services used extensively, but approach not fully systematic | +| **Level 3** | Systematic and Documented | Documented practices, outsourced/cloud management services, efficient operations | +| **Level 4** | Measured | Transparent governance model, cloud-native applications widely adopted across organization | +| **Level 5** | Optimized | Open, interoperable cloud environment, data-driven decisions, flexible workload placement | + +## Key Components + +### Business Capability Areas +- Finance (CAPEX to OPEX shift) +- Enterprise Strategy +- Organizational Structure +- Culture and Skills +- Governance and Compliance +- Business Processes +- Procurement and Commercial + +### Technical Capability Areas +- IT Architecture +- Applications Modernization +- DevOps +- Security +- IaaS / PaaS / SaaS / STaaS / IPaaS +- Data and Information Services +- Network Infrastructure +- AI and IoT Integration +- APIs + +### Three Core Evaluation Dimensions +1. **People** — Skills, ways of working, training programs +2. **Processes** — Workflow updates, continuous improvement +3. **Technology** — Infrastructure changes, new tech adoption + +## Benefits of Implementing CMM + +1. **Enhanced Strategic Planning** — Focus on high-impact areas +2. **Improved Team Communications** — Shared framework for goals +3. **Enhanced Application Performance** — Smoother cloud apps +4. **Enhanced Security and Performance** — Best practices adherence +5. **Faster Time to Market** — Efficient resource use +6. **Industry Benchmarking** — Compare against sector peers +7. **Cost-Savings** — Efficiency and automation emphasis + +## Related Models and Frameworks + +| Model | Focus | +|-------|-------| +| **CMM 4.8** | IT organization's business/technology functions across cloud domains | +| **Cloud Native Maturity Model** | CNCF ecosystem, scalable applications | +| **Cloud Security Maturity Model (CSMM)** | Cloud security across 12 categories | +| **Software Assurance Maturity Model (SAMM)** | Entire software lifecycle | +| **AWS CAF** | AWS-specific transformation roadmap | +| **Azure CAF** | Microsoft Azure adoption | +| **Google Cloud Adoption Framework** | Google Cloud transition | + +## Related Concepts + +- [[Cloud-Adoption-Strategy]] +- [[Multi-Cloud-Strategy]] +- [[Cloud-Native]] +- [[DevOps-Maturity]] +- [[FinOps]] + +## Sources + +- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] +- [[sources/cloud-operating-model-key-strategies-and-best-practices.md]] +- [[sources/cloud-devop-maturity-guideline.md]] diff --git a/wiki/entities/Cloud-Provider.md b/wiki/entities/Cloud-Provider.md new file mode 100644 index 00000000..e621c21a --- /dev/null +++ b/wiki/entities/Cloud-Provider.md @@ -0,0 +1,40 @@ +--- +title: Cloud Provider +tags: [Cloud, Infrastructure, IaaS] +--- + +# Cloud Provider + +## Overview + +**Cloud Provider** 指提供云计算服务的企业或组织，通过互联网按需提供计算资源、存储、应用和服务。主要云提供商形成了一个竞争激烈的市场，企业可通过多云策略在不同提供商之间分配工作负载以优化性能和成本。 + +## Major Cloud Providers + +| Provider | Full Name | Key Strengths | +|----------|-----------|---------------| +| AWS | Amazon Web Services | 最早、最大生态，计算/存储/AI 最全面 | +| Azure | Microsoft Azure | 企业级集成、Microsoft 365 深度整合、混合云 | +| GCP | Google Cloud Platform | 数据分析、AI/ML、Kubernetes 原生 | +| OCI | Oracle Cloud Infrastructure | 数据库、企业应用、Exadata | +| Alibaba Cloud | 阿里云 | 亚太市场份额、中国市场首选 | +| IBM Cloud | IBM Cloud | 企业 AI、混合云、红帽集成 | + +## Key Concepts + +- **IaaS** (Infrastructure as a Service): 基础架构级云服务（VM、存储、网络） +- **PaaS** (Platform as a Service): 平台级云服务（数据库、开发框架） +- **SaaS** (Software as a Service): 软件级云服务（CRM、ERP、协作工具） +- **多云策略 (Multi-Cloud)**: 同时使用多个云提供商的策略 + +## Related Concepts + +- [[Multi-Cloud Strategy]] +- [[Vendor Lock-In]] +- [[Cloud Migration]] +- [[High Availability]] +- [[Scalability]] + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/entities/DORA-Metrics.md b/wiki/entities/DORA-Metrics.md new file mode 100644 index 00000000..906c5dd4 --- /dev/null +++ b/wiki/entities/DORA-Metrics.md @@ -0,0 +1,23 @@ +# DORA Metrics + +## Source +- [[sources/cloud-devop-maturity-guideline.md]] + +## Summary +The DORA (DevOps Research and Assessment) metrics are four key measures used to assess DevOps performance and maturity: + +1. **Deployment Frequency** — How often code is deployed to production +2. **Lead Time for Changes** — Time from code commit to production deployment +3. **Change Failure Rate** — Percentage of deployments causing failures +4. **Mean Time to Recovery (MTTR)** — Time to restore service after failures + +## Related Sources +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/CI-CD-Pipeline]] + +## Ingested +- Date: 2026-04-21 diff --git a/wiki/entities/DevOps-Maturity-Model.md b/wiki/entities/DevOps-Maturity-Model.md new file mode 100644 index 00000000..44845705 --- /dev/null +++ b/wiki/entities/DevOps-Maturity-Model.md @@ -0,0 +1,60 @@ +# DevOps Maturity Model + +## Source +- [[sources/cloud-devop-maturity-guideline.md]] +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] + +## Summary + +A framework for evaluating an organization's progress in adopting DevOps practices, typically ranging from ad-hoc processes to highly optimized and automated environments. The model defines **five maturity stages**: + +| Stage | Name | Key Characteristics | +|-------|------|---------------------| +| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release | +| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation, unit/integration testing | +| Phase 3 | Automated and Defined | Standardized processes, most infrastructure automated, security integrated into development process | +| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management, continuous security monitoring | +| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention in pipeline | + +## Key Focus Areas + +1. **Culture and Strategy** — Teamwork, transparency, customer-centric mindset +2. **Automation** — AutoDevOps for continuous delivery and deployment +3. **Structure and Process** — Standardized, small-batch, transparent processes +4. **Collaboration and Sharing** — Cohesive teams leveraging diverse skill sets +5. **Technology** — Tool selection aligned with team needs + +## Quality Criteria + +- Assessment criteria (standards for evaluating maturity) +- Five maturity levels +- Core DevOps practices (release management, CI/CD, IaC, security) +- Relevant metrics (deployment frequency, MTTR, change failure rate) +- Cultural guides +- Tools and technologies +- Roles and responsibilities + +## Business Benefits + +- Quicker adjustment to market changes +- Capability to seize new opportunities +- Better scalability via IaC +- Enhanced operational performance +- Faster delivery times +- Improved quality via continuous monitoring and feedback + +## Security Integration (DevSecOps) + +The model emphasizes merging development, operations, and security into a unified process. Security progression: ad-hoc compliance scans → separate security team → security in design/architecture discussions → security updates in product workflow → preventing non-compliant code from production. + +## Related Concepts +- [[concepts/DevOps-Maturity]] +- [[concepts/DORA-Metrics]] +- [[concepts/DevSecOps]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/Continuous-Deployment]] + +## Ingested +- Date: 2026-04-21 (initial) +- Date: 2026-04-24 (updated with Phase 1-5 details) diff --git a/wiki/entities/Google-Cloud.md b/wiki/entities/Google-Cloud.md new file mode 100644 index 00000000..efdde6c3 --- /dev/null +++ b/wiki/entities/Google-Cloud.md @@ -0,0 +1,41 @@ +--- +title: Google Cloud Platform (GCP) +tags: [Cloud, Provider, Public-Cloud] +--- + +# Google Cloud Platform (GCP) + +**Google Cloud Platform (GCP)** is Google's cloud computing platform, providing infrastructure and application services with strengths in AI/ML, data analytics, and container technologies. + +## Overview + +GCP is one of the three major public cloud providers, particularly known for Kubernetes (originated at Google), data analytics, and machine learning capabilities. + +## Key Services Referenced + +| Category | Services | +|----------|----------| +| Compute | Compute Engine, Cloud Functions, GKE | +| Storage | Cloud Storage, Filestore | +| Database | Cloud SQL, BigQuery, Firestore, Spanner | +| AI/ML | Vertex AI, TensorFlow, Gemini | +| Analytics | BigQuery, Dataflow, Looker | +| Networking | VPC, Cloud CDN, Cloud Load Balancing | + +## Multi-Cloud Context + +GCP is commonly used alongside AWS and Azure in multi-cloud strategies: +- **Machine Learning** — Often preferred for ML/AI workloads (Vertex AI, TensorFlow) +- **Data Analytics** — BigQuery for data warehousing and analytics +- **Container-native** — GKE (Google Kubernetes Engine) for container orchestration + +## Related Concepts + +- [[Multi-Cloud-Strategy]] — GCP as one of multiple providers +- [[Cloud-Native]] — Building on GCP-native services +- [[Kubernetes]] — GKE as managed Kubernetes +- [[FinOps]] — Managing GCP costs + +## Sources + +- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]] diff --git a/wiki/entities/HemantSawant.md b/wiki/entities/HemantSawant.md new file mode 100644 index 00000000..414181db --- /dev/null +++ b/wiki/entities/HemantSawant.md @@ -0,0 +1,24 @@ +--- +title: "Hemant Sawant" +type: entity +tags: [devops, author, linkedin] +sources: [devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin] +last_updated: 2026-04-22 +--- + +## Source File +- [[raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md]] + +## Summary +Hemant Sawant is a DevOps practitioner and thought leader who publishes articles on LinkedIn about DevOps culture, organizational transformation, Agile practices, and cloud-native engineering. The ingested article covers a comprehensive DevOps transformation framework including the four foundational pillars, Agile integration strategies, and a strategic transformation playbook. + +## Key Claims +- DevOps transformation requires dismantling silos between Development and Operations through cross-functional teams +- Four foundational pillars: Collaboration, Automation, Continuous Improvement (Kaizen), Customer-Centricity +- Agile and DevOps are symbiotic — DevOps extends Agile agility to operations +- Transformation requires leadership buy-in, upskilling investment, and pilot-driven quick wins + +## Connections +- [[DevOps Culture]] — Primary topic of his writing +- [[DevSecOps]] — Future trend mentioned in his article +- [[GitOps]] — Future trend mentioned in his article diff --git a/wiki/entities/Open-Alliance-for-Cloud-Adoption.md b/wiki/entities/Open-Alliance-for-Cloud-Adoption.md new file mode 100644 index 00000000..6f3b558c --- /dev/null +++ b/wiki/entities/Open-Alliance-for-Cloud-Adoption.md @@ -0,0 +1,30 @@ +--- +title: Open Alliance for Cloud Adoption (OACA) +source: https://www.bacancytechnology.com/blog/cloud-maturity-model +tags: [Cloud, Framework, Organization, Cloud-Adoption] +--- + +# Open Alliance for Cloud Adoption (OACA) + +## Overview + +The **Open Alliance for Cloud Adoption (OACA)** is an organization that defines and promotes the Cloud Maturity Model (CMM) as a framework for enterprise cloud transformation. + +## Role in Cloud Maturity Model + +OACA describes CMM as a framework that: +- Assists organizations in identifying tailored solutions for adopting cloud or hybrid IT environments +- Evaluates organizations' readiness for adopting the cloud +- Helps assess their current use of cloud services +- Sets future goals for developing a cloud migration strategy +- Conducts GAP analysis +- Identifies areas for improving cloud infrastructure based on business objectives + +## Related Concepts + +- [[Cloud-Maturity-Model]] +- [[Cloud-Adoption-Strategy]] + +## Sources + +- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] diff --git a/wiki/entities/cloud-computing.md b/wiki/entities/cloud-computing.md new file mode 100644 index 00000000..cfd0dae3 --- /dev/null +++ b/wiki/entities/cloud-computing.md @@ -0,0 +1,60 @@ +--- +title: Cloud Computing +--- + +# Cloud Computing + +**Cloud Computing** is the delivery of computing services—including servers, storage, databases, networking, software, analytics, and intelligence—over the Internet ("the cloud") to offer faster innovation, flexible resources, and economies of scale. + +## Key Characteristics + +- **On-demand self-service**: Provision resources as needed without human intervention +- **Broad network access**: Access via internet from anywhere on any device +- **Resource pooling**: Multi-tenant model with resources pooled to serve multiple consumers +- **Rapid elasticity**: Scale resources up or down dynamically +- **Measured service**: Pay-as-you-go pricing model + +## Common Misconceptions + +Cloud computing is widely misunderstood. Key myths include: + +1. **Cloud is not secure** — Reality: Major providers invest heavily in security (encryption, MFA, ISO 27001, HIPAA, GDPR compliance) and offer 24/7 monitoring +2. **Cloud is "someone else's computer"** — Reality: Cloud is a vast network of sophisticated data centers with redundancy, auto-failover, and global distribution +3. **Cloud is too expensive** — Reality: Pay-as-you-go, reserved instances, auto-scaling, and serverless models can significantly reduce costs vs. on-premises +4. **You lose control over data** — Reality: Cloud providers offer robust data governance, permissions management, and hybrid/multi-cloud options +5. **Only for large enterprises** — Reality: SMBs and startups benefit greatly from flexible pricing and enterprise-grade technology +6. **Migration is too complex** — Reality: Phased migration, hybrid cloud, and professional services enable smooth transitions +7. **Performance is unreliable** — Reality: Major providers offer SLAs exceeding 99.99% uptime with redundant infrastructure and automated failover + +## Cloud Deployment Models + +- **Public Cloud**: Resources shared across multiple organizations (AWS, Azure, GCP) +- **Private Cloud**: Dedicated to a single organization (on-premises or hosted) +- **Hybrid Cloud**: Combines public and private clouds +- **Multi-Cloud**: Uses multiple public cloud providers simultaneously + +## Related Concepts +## Cloud Providers + +In multi-cloud strategies, organizations typically work with multiple providers: + +- [[AWS]] — Amazon Web Services +- [[Azure]] — Microsoft Azure +- [[Google-Cloud]] — Google Cloud Platform + +## Related Concepts + +- [[Cloud Security]] +- [[Cloud Migration]] +- [[High Availability]] +- [[Multi-Cloud Strategy]] +- [[Vendor-Lock-In]] +- [[Data-Sovereignty]] +- [[FinOps]] +- [[Infrastructure as Code]] +- [[Serverless Computing]] + +## Sources + +- [[The Myths and Misconceptions About Cloud Computing (LinkedIn)|the-myths-and-misconceptions-about-cloud-computing-linkedin]] +- [[How Can a Multi Cloud Strategy Transform Your Business ROI|sources/how-can-a-multi-cloud-strategy-transform-your-business-roi]] diff --git a/wiki/index.md b/wiki/index.md new file mode 100644 index 00000000..ad9a0d55 --- /dev/null +++ b/wiki/index.md @@ -0,0 +1,583 @@ +# Wiki Index + +## Overview +- [Overview](overview.md) — living synthesis + +## Sources +- [2026-04-21] [zk-steward](sources/zk-steward.md) — (expected: wiki/sources/zk-steward.md — source missing) +- [2026-04-21] [实战笔记-本地部署-rsshub-并获取-youtube-订阅](sources/实战笔记-本地部署-rsshub-并获取-youtube-订阅.md) — (expected: wiki/sources/实战笔记-本地部署-rsshub-并获取-youtube-订阅.md — source missing) +- [2026-04-21] [n8n-调用openclaw-agents的工作流架构](sources/n8n-调用openclaw-agents的工作流架构.md) — (expected: wiki/sources/n8n-调用openclaw-agents的工作流架构.md — source missing) +- [2026-04-21] [n8n-docker-配置-telegram-代理-troubleshooting](sources/n8n-docker-配置-telegram-代理-troubleshooting.md) — (expected: wiki/sources/n8n-docker-配置-telegram-代理-troubleshooting.md — source missing) +- [2026-04-20] [n8n调用hermes-agents的工作流架构](sources/n8n调用hermes-agents的工作流架构.md) — (expected: wiki/sources/n8n调用hermes-agents的工作流架构.md — source missing) +- [2026-04-20] [open-webui-hermes-agent](sources/open-webui-hermes-agent.md) — (expected: wiki/sources/open-webui-hermes-agent.md — source missing) +- [2026-04-20] [language-translator](sources/language-translator.md) — (expected: wiki/sources/language-translator.md — source missing) +- [2026-04-20] [loan-officer-assistant](sources/loan-officer-assistant.md) — (expected: wiki/sources/loan-officer-assistant.md — source missing) +- [2026-04-20] [real-estate-buyer-seller](sources/real-estate-buyer-seller.md) — (expected: wiki/sources/real-estate-buyer-seller.md — source missing) +- [2026-04-20] [legal-document-review](sources/legal-document-review.md) — (expected: wiki/sources/legal-document-review.md — source missing) +- [2026-04-20] [sales-outreach](sources/sales-outreach.md) — (expected: wiki/sources/sales-outreach.md — source missing) +- [2026-04-20] [retail-customer-returns](sources/retail-customer-returns.md) — (expected: wiki/sources/retail-customer-returns.md — source missing) +- [2026-04-20] [specialized-chief-of-staff](sources/specialized-chief-of-staff.md) — (expected: wiki/sources/specialized-chief-of-staff.md — source missing) +- [2026-04-20] [hr-onboarding](sources/hr-onboarding.md) — (expected: wiki/sources/hr-onboarding.md — source missing) +- [2026-04-20] [customer-service](sources/customer-service.md) — (expected: wiki/sources/customer-service.md — source missing) +- [2026-04-20] [healthcare-customer-service](sources/healthcare-customer-service.md) — (expected: wiki/sources/healthcare-customer-service.md — source missing) +- [2026-04-20] [legal-billing-time-tracking](sources/legal-billing-time-tracking.md) — (expected: wiki/sources/legal-billing-time-tracking.md — source missing) +- [2026-04-20] [legal-client-intake](sources/legal-client-intake.md) — (expected: wiki/sources/legal-client-intake.md — source missing) +- [2026-04-20] [hospitality-guest-services](sources/hospitality-guest-services.md) — (expected: wiki/sources/hospitality-guest-services.md — source missing) +- [2026-04-20] [security](sources/security.md) — (expected: wiki/sources/security.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [marketing-seo-specialist](sources/marketing-seo-specialist.md) — (expected: wiki/sources/marketing-seo-specialist.md — source missing) +- [2026-04-20] [marketing-agentic-search-optimizer](sources/marketing-agentic-search-optimizer.md) — (expected: wiki/sources/marketing-agentic-search-optimizer.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-04-20] [finance-bookkeeper-controller](sources/finance-bookkeeper-controller.md) — (expected: wiki/sources/finance-bookkeeper-controller.md — source missing) +- [2026-04-20] [finance-fpa-analyst](sources/finance-fpa-analyst.md) — (expected: wiki/sources/finance-fpa-analyst.md — source missing) +- [2026-04-20] [finance-investment-researcher](sources/finance-investment-researcher.md) — (expected: wiki/sources/finance-investment-researcher.md — source missing) +- [2026-04-20] [finance-financial-analyst](sources/finance-financial-analyst.md) — (expected: wiki/sources/finance-financial-analyst.md — source missing) +- [2026-04-20] [finance-tax-strategist](sources/finance-tax-strategist.md) — (expected: wiki/sources/finance-tax-strategist.md — source missing) +- [2026-04-20] [engineering-voice-ai-integration-engineer](sources/engineering-voice-ai-integration-engineer.md) — (expected: wiki/sources/engineering-voice-ai-integration-engineer.md — source missing) +- [2026-04-20] [engineering-codebase-onboarding-engineer](sources/engineering-codebase-onboarding-engineer.md) — (expected: wiki/sources/engineering-codebase-onboarding-engineer.md — source missing) +- [2026-04-20] [engineering-minimal-change-engineer](sources/engineering-minimal-change-engineer.md) — (expected: wiki/sources/engineering-minimal-change-engineer.md — source missing) +- [2026-04-20] [contributing](sources/contributing.md) — (expected: wiki/sources/contributing.md — source missing) +- [2026-04-20] [sre-weekly-issue-513](sources/sre-weekly-issue-513.md) — (expected: wiki/sources/sre-weekly-issue-513.md — source missing) +- [2026-04-20] [llm-wiki](sources/llm-wiki.md) — (expected: wiki/sources/llm-wiki.md — source missing) +- [2026-04-20] [我做了个-skill-让-ai-帮你生成-logo-和图标](sources/我做了个-skill-让-ai-帮你生成-logo-和图标.md) — (expected: wiki/sources/我做了个-skill-让-ai-帮你生成-logo-和图标.md — source missing) +- [2026-04-20] [karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环](sources/karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环.md) — (expected: wiki/sources/karpathy-最新分享-用-llm-搭建个人知识库-告别-rag-的低效循环.md — source missing) +- [2026-04-20] [cloud-operating-model-key-strategies-and-best-practices](sources/cloud-operating-model-key-strategies-and-best-practices.md) — (expected: wiki/sources/cloud-operating-model-key-strategies-and-best-practices.md — source missing) +- [2026-04-19] [public-vs-private-vs-hybrid-cloud-differences-explained](sources/public-vs-private-vs-hybrid-cloud-differences-explained.md) — (expected: wiki/sources/public-vs-private-vs-hybrid-cloud-differences-explained.md — source missing) +- [2026-04-19] [baoyu-skills](sources/baoyu-skills.md) — (expected: wiki/sources/baoyu-skills.md — source missing) +- [2026-04-18] [如何让ai生成风格一致的图片](sources/如何让ai生成风格一致的图片.md) — (expected: wiki/sources/如何让ai生成风格一致的图片.md — source missing) +- [2026-04-18] [last30days-使用指南](sources/last30days-使用指南.md) — (expected: wiki/sources/last30days-使用指南.md — source missing) +- [2026-04-18] [obsidian-必装-skills](sources/obsidian-必装-skills.md) — (expected: wiki/sources/obsidian-必装-skills.md — source missing) +- [2026-04-18] [cloud-learning-master-index](sources/cloud-learning-master-index.md) — (expected: wiki/sources/cloud-learning-master-index.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123-1](sources/public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123-1.md) — (expected: wiki/sources/public-cloud-learning-sessions-tagging-standards-for-all-hyperscalers-20240123-1.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-thor-platform-flows-20241210-160056-meet](sources/public-cloud-learning-sessions-opentext-thor-platform-flows-20241210-160056-meet.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-thor-platform-flows-20241210-160056-meet.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meet](sources/public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meet.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-tagging-standard-v2-20250429-170111-meet.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-product-hub-pht-overview-and-qa-20240806](sources/public-cloud-learning-sessions-opentext-product-hub-pht-overview-and-qa-20240806.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-product-hub-pht-overview-and-qa-20240806.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-github-enterprise-to-gitlab-migration-20](sources/public-cloud-learning-sessions-opentext-github-enterprise-to-gitlab-migration-20.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-github-enterprise-to-gitlab-migration-20.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2](sources/public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-evolving-from-dr-to-recovery-assurance-2.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-aws-end-user-compute-services-20240430-160120-mee](sources/public-cloud-learning-sessions-aws-end-user-compute-services-20240430-160120-mee.md) — (expected: wiki/sources/public-cloud-learning-sessions-aws-end-user-compute-services-20240430-160120-mee.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109](sources/public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109.md) — (expected: wiki/sources/public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109.md — source missing) +- [2026-04-18] [ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation](sources/ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation.md) — (expected: wiki/sources/ctp-topic-65-tracing-the-value-delivered-in-cloud-transformation.md — source missing) +- [2026-04-18] [ctp-topic-6-aws-workspaces-demo](sources/ctp-topic-6-aws-workspaces-demo.md) — (expected: wiki/sources/ctp-topic-6-aws-workspaces-demo.md — source missing) +- [2026-04-18] [ctp-topic-57-product-backlog-managing-demand](sources/ctp-topic-57-product-backlog-managing-demand.md) — (expected: wiki/sources/ctp-topic-57-product-backlog-managing-demand.md — source missing) +- [2026-04-18] [ctp-topic-53-why-bother-with-cloud](sources/ctp-topic-53-why-bother-with-cloud.md) — (expected: wiki/sources/ctp-topic-53-why-bother-with-cloud.md — source missing) +- [2026-04-18] [ctp-topic-41-nfrs-and-error-budgets](sources/ctp-topic-41-nfrs-and-error-budgets.md) — (expected: wiki/sources/ctp-topic-41-nfrs-and-error-budgets.md — source missing) +- [2026-04-18] [ctp-topic-4-using-agile-to-run-the-cloud-transformation-program](sources/ctp-topic-4-using-agile-to-run-the-cloud-transformation-program.md) — (expected: wiki/sources/ctp-topic-4-using-agile-to-run-the-cloud-transformation-program.md — source missing) +- [2026-04-18] [ctp-topic-30-managing-change](sources/ctp-topic-30-managing-change.md) — (expected: wiki/sources/ctp-topic-30-managing-change.md — source missing) +- [2026-04-18] [ctp-topic-23-introduction-to-the-technical-architecture-team-and-function](sources/ctp-topic-23-introduction-to-the-technical-architecture-team-and-function.md) — (expected: wiki/sources/ctp-topic-23-introduction-to-the-technical-architecture-team-and-function.md — source missing) +- [2026-04-18] [ctp-topic-20-program-demand-process-flow-and-poc-onboarding](sources/ctp-topic-20-program-demand-process-flow-and-poc-onboarding.md) — (expected: wiki/sources/ctp-topic-20-program-demand-process-flow-and-poc-onboarding.md — source missing) +- [2026-04-18] [ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security](sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md) — (expected: wiki/sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee](sources/public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-serverless-computing-20240903-160139-mee.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111](sources/public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-generative-ai-prompt-engineering-2024111.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-2-2024091.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091](sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-event-driven-architecture-part-1-2024091.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec](sources/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-ai-use-cases-20241126-160106-meeting-rec.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin](sources/public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin.md) — (expected: wiki/sources/public-cloud-learning-sessions-introduction-to-artificial-intelligence-ai-machin.md — source missing) +- [2026-04-18] [ctp-topic-69-best-practices-for-migrating-on-premises-iod-virtual-machines-to-vm](sources/ctp-topic-69-best-practices-for-migrating-on-premises-iod-virtual-machines-to-vm.md) — (expected: wiki/sources/ctp-topic-69-best-practices-for-migrating-on-premises-iod-virtual-machines-to-vm.md — source missing) +- [2026-04-18] [ctp-topic-61-workload-vpc-provision-with-ipam-automation](sources/ctp-topic-61-workload-vpc-provision-with-ipam-automation.md) — (expected: wiki/sources/ctp-topic-61-workload-vpc-provision-with-ipam-automation.md — source missing) +- [2026-04-18] [ctp-topic-45-automatic-ip-address-allocation-with-ipam](sources/ctp-topic-45-automatic-ip-address-allocation-with-ipam.md) — (expected: wiki/sources/ctp-topic-45-automatic-ip-address-allocation-with-ipam.md — source missing) +- [2026-04-18] [ctp-topic-43-vmware-cloud-on-aws](sources/ctp-topic-43-vmware-cloud-on-aws.md) — (expected: wiki/sources/ctp-topic-43-vmware-cloud-on-aws.md — source missing) +- [2026-04-18] [ctp-topic-36-sendgrid-as-an-email-service](sources/ctp-topic-36-sendgrid-as-an-email-service.md) — (expected: wiki/sources/ctp-topic-36-sendgrid-as-an-email-service.md — source missing) +- [2026-04-18] [ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones](sources/ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones.md) — (expected: wiki/sources/ctp-topic-31-network-segregation-and-secure-access-to-the-new-aws-landing-zones.md — source missing) +- [2026-04-18] [ctp-topic-22-global-dns-service-offerings](sources/ctp-topic-22-global-dns-service-offerings.md) — (expected: wiki/sources/ctp-topic-22-global-dns-service-offerings.md — source missing) +- [2026-04-18] [ctp-topic-19-configuring-dns-within-aws-lzs](sources/ctp-topic-19-configuring-dns-within-aws-lzs.md) — (expected: wiki/sources/ctp-topic-19-configuring-dns-within-aws-lzs.md — source missing) +- [2026-04-18] [ctp-topic-18-wide-area-networking-in-aws-cloud](sources/ctp-topic-18-wide-area-networking-in-aws-cloud.md) — (expected: wiki/sources/ctp-topic-18-wide-area-networking-in-aws-cloud.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me](sources/public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me.md) — (expected: wiki/sources/public-cloud-learning-sessions-opentext-gis-security-policies-20241015-160257-me.md — source missing) +- [2026-04-18] [ctp-topic-62-aws-secrets-manager](sources/ctp-topic-62-aws-secrets-manager.md) — (expected: wiki/sources/ctp-topic-62-aws-secrets-manager.md — source missing) +- [2026-04-18] [ctp-topic-55-aws-firewall-manager](sources/ctp-topic-55-aws-firewall-manager.md) — (expected: wiki/sources/ctp-topic-55-aws-firewall-manager.md — source missing) +- [2026-04-18] [ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management](sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md) — (expected: wiki/sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md — source missing) +- [2026-04-18] [ctp-topic-49-container-lifecycle-hardening-standards](sources/ctp-topic-49-container-lifecycle-hardening-standards.md) — (expected: wiki/sources/ctp-topic-49-container-lifecycle-hardening-standards.md — source missing) +- [2026-04-18] [ctp-topic-37-secrets-certificates-management](sources/ctp-topic-37-secrets-certificates-management.md) — (expected: wiki/sources/ctp-topic-37-secrets-certificates-management.md — source missing) +- [2026-04-18] [ctp-topic-24-micro-focus-product-privacy-framework](sources/ctp-topic-24-micro-focus-product-privacy-framework.md) — (expected: wiki/sources/ctp-topic-24-micro-focus-product-privacy-framework.md — source missing) +- [2026-04-18] [ctp-topic-21-supply-chain-security-in-micro-focus](sources/ctp-topic-21-supply-chain-security-in-micro-focus.md) — (expected: wiki/sources/ctp-topic-21-supply-chain-security-in-micro-focus.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16](sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md) — (expected: wiki/sources/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md — source missing) +- [2026-04-18] [ctp-topic-9-ci-cd-with-gruntwork](sources/ctp-topic-9-ci-cd-with-gruntwork.md) — (expected: wiki/sources/ctp-topic-9-ci-cd-with-gruntwork.md — source missing) +- [2026-04-18] [ctp-topic-56-automated-infrastructure-testing](sources/ctp-topic-56-automated-infrastructure-testing.md) — (expected: wiki/sources/ctp-topic-56-automated-infrastructure-testing.md — source missing) +- [2026-04-18] [ctp-topic-33-an-introduction-to-gitops](sources/ctp-topic-33-an-introduction-to-gitops.md) — (expected: wiki/sources/ctp-topic-33-an-introduction-to-gitops.md — source missing) +- [2026-04-18] [ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments](sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md) — (expected: wiki/sources/ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments.md — source missing) +- [2026-04-18] [ctp-topic-3-deploy-and-maintain-infrastructure](sources/ctp-topic-3-deploy-and-maintain-infrastructure.md) — (expected: wiki/sources/ctp-topic-3-deploy-and-maintain-infrastructure.md — source missing) +- [2026-04-18] [ctp-topic-2-git](sources/ctp-topic-2-git.md) — (expected: wiki/sources/ctp-topic-2-git.md — source missing) +- [2026-04-18] [ctp-topic-15-working-with-renovatebot](sources/ctp-topic-15-working-with-renovatebot.md) — (expected: wiki/sources/ctp-topic-15-working-with-renovatebot.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting](sources/public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting.md) — (expected: wiki/sources/public-cloud-learning-sessions-storage-cost-optimization-20240305-160037-meeting.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco](sources/public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco.md) — (expected: wiki/sources/public-cloud-learning-sessions-reducing-cloud-costs-20250318-170100-meeting-reco.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-budget-control-20240319-160204-meeting-recording](sources/public-cloud-learning-sessions-budget-control-20240319-160204-meeting-recording.md) — (expected: wiki/sources/public-cloud-learning-sessions-budget-control-20240319-160204-meeting-recording.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2](sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md) — (expected: wiki/sources/public-cloud-learning-sessions-best-practices-for-ec2-cost-optimization-in-aws-2.md — source missing) +- [2026-04-18] [ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when](sources/ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when.md) — (expected: wiki/sources/ctp-topic-71-pcgs-guide-to-rightsizing-why-how-when.md — source missing) +- [2026-04-18] [ctp-topic-63-optimise-resource-cost-using-automation](sources/ctp-topic-63-optimise-resource-cost-using-automation.md) — (expected: wiki/sources/ctp-topic-63-optimise-resource-cost-using-automation.md — source missing) +- [2026-04-18] [ctp-topic-27-aws-instance-scheduler](sources/ctp-topic-27-aws-instance-scheduler.md) — (expected: wiki/sources/ctp-topic-27-aws-instance-scheduler.md — source missing) +- [2026-04-18] [ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co](sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md) — (expected: wiki/sources/ctp-topic-13-cloud-finops-micro-focus-policies-best-practices-to-optimize-the-co.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-observability-with-opentelemetry-20240402-160113](sources/public-cloud-learning-sessions-observability-with-opentelemetry-20240402-160113.md) — (expected: wiki/sources/public-cloud-learning-sessions-observability-with-opentelemetry-20240402-160113.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-eks-optimization-part-3-of-3-introduction-to-eks](sources/public-cloud-learning-sessions-eks-optimization-part-3-of-3-introduction-to-eks.md) — (expected: wiki/sources/public-cloud-learning-sessions-eks-optimization-part-3-of-3-introduction-to-eks.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-eks-optimization-part-2-of-3-running-containers-w](sources/public-cloud-learning-sessions-eks-optimization-part-2-of-3-running-containers-w.md) — (expected: wiki/sources/public-cloud-learning-sessions-eks-optimization-part-2-of-3-running-containers-w.md — source missing) +- [2026-04-18] [public-cloud-learning-sessions-eks-optimization-part-1-of-3-compute-optimization](sources/public-cloud-learning-sessions-eks-optimization-part-1-of-3-compute-optimization.md) — (expected: wiki/sources/public-cloud-learning-sessions-eks-optimization-part-1-of-3-compute-optimization.md — source missing) +- [2026-04-18] [ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid](sources/ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid.md) — (expected: wiki/sources/ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid.md — source missing) +- [2026-04-18] [ctp-topic-70-eks-deployment-using-iac](sources/ctp-topic-70-eks-deployment-using-iac.md) — (expected: wiki/sources/ctp-topic-70-eks-deployment-using-iac.md — source missing) +- [2026-04-18] [ctp-topic-67-cloud-native-observability-using-opentelemetry](sources/ctp-topic-67-cloud-native-observability-using-opentelemetry.md) — (expected: wiki/sources/ctp-topic-67-cloud-native-observability-using-opentelemetry.md — source missing) +- [2026-04-18] [ctp-topic-64-scaling-out-with-amazon-eks](sources/ctp-topic-64-scaling-out-with-amazon-eks.md) — (expected: wiki/sources/ctp-topic-64-scaling-out-with-amazon-eks.md — source missing) +- [2026-04-18] [ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana](sources/ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana.md) — (expected: wiki/sources/ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana.md — source missing) +- [2026-04-18] [ctp-topic-59-achieving-reliability-with-amazon-eks](sources/ctp-topic-59-achieving-reliability-with-amazon-eks.md) — (expected: wiki/sources/ctp-topic-59-achieving-reliability-with-amazon-eks.md — source missing) +- [2026-04-18] [ctp-topic-54-esm-saas-log-analytics](sources/ctp-topic-54-esm-saas-log-analytics.md) — (expected: wiki/sources/ctp-topic-54-esm-saas-log-analytics.md — source missing) +- [2026-04-18] [ctp-topic-42-grafana-observability-dashboard](sources/ctp-topic-42-grafana-observability-dashboard.md) — (expected: wiki/sources/ctp-topic-42-grafana-observability-dashboard.md — source missing) +- [2026-04-18] [ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone](sources/ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone.md) — (expected: wiki/sources/ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone.md — source missing) +- [2026-04-18] [ctp-topic-29-cloud-monitoring-saas-lz-accounts](sources/ctp-topic-29-cloud-monitoring-saas-lz-accounts.md) — (expected: wiki/sources/ctp-topic-29-cloud-monitoring-saas-lz-accounts.md — source missing) +- [2026-04-18] [learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording](sources/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md) — (expected: wiki/sources/learning-sessions-ecs-deployment-using-iac-20230808-183322-meeting-recording.md — source missing) +- [2026-04-18] [learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform](sources/learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform.md) — (expected: wiki/sources/learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform.md — source missing) +- [2026-04-18] [learning-sessions-cloud-transformation-programme-20230808-183322-meeting-recordi](sources/learning-sessions-cloud-transformation-programme-20230808-183322-meeting-recordi.md) — (expected: wiki/sources/learning-sessions-cloud-transformation-programme-20230808-183322-meeting-recordi.md — source missing) +- [2026-04-18] [ctp-topic-48-terraform-vs-terragrunt](sources/ctp-topic-48-terraform-vs-terragrunt.md) — (expected: wiki/sources/ctp-topic-48-terraform-vs-terragrunt.md — source missing) +- [2026-04-18] [ctp-topic-16-cross-account-terraform-modules](sources/ctp-topic-16-cross-account-terraform-modules.md) — (expected: wiki/sources/ctp-topic-16-cross-account-terraform-modules.md — source missing) +- [2026-04-18] [ctp-topic-12-using-ses-smtp-service-terraform-module](sources/ctp-topic-12-using-ses-smtp-service-terraform-module.md) — (expected: wiki/sources/ctp-topic-12-using-ses-smtp-service-terraform-module.md — source missing) +- [2026-04-18] [learning-sessions-identity-governance-vsm-replacement-20231128-160326-meeting-re](sources/learning-sessions-identity-governance-vsm-replacement-20231128-160326-meeting-re.md) — (expected: wiki/sources/learning-sessions-identity-governance-vsm-replacement-20231128-160326-meeting-re.md — source missing) +- [2026-04-18] [ctp-topic-5-aws-identity-and-access-management-iam](sources/ctp-topic-5-aws-identity-and-access-management-iam.md) — (expected: wiki/sources/ctp-topic-5-aws-identity-and-access-management-iam.md — source missing) +- [2026-04-18] [ctp-topic-11-ad-integration-and-login-using-ad-accounts](sources/ctp-topic-11-ad-integration-and-login-using-ad-accounts.md) — (expected: wiki/sources/ctp-topic-11-ad-integration-and-login-using-ad-accounts.md — source missing) +- [2026-04-18] [learning-sessions-standard-amis-updates-20231205-160324-meeting-recording-2](sources/learning-sessions-standard-amis-updates-20231205-160324-meeting-recording-2.md) — (expected: wiki/sources/learning-sessions-standard-amis-updates-20231205-160324-meeting-recording-2.md — source missing) +- [2026-04-18] [ctp-topic-73-aws-backup-implementation-of-the-cloud-transformation-program](sources/ctp-topic-73-aws-backup-implementation-of-the-cloud-transformation-program.md) — (expected: wiki/sources/ctp-topic-73-aws-backup-implementation-of-the-cloud-transformation-program.md — source missing) +- [2026-04-18] [ctp-topic-72-implementing-an-enterprise-dr-strategy-using-aws-backup](sources/ctp-topic-72-implementing-an-enterprise-dr-strategy-using-aws-backup.md) — (expected: wiki/sources/ctp-topic-72-implementing-an-enterprise-dr-strategy-using-aws-backup.md — source missing) +- [2026-04-18] [ctp-topic-7-saas-landing-zone-design](sources/ctp-topic-7-saas-landing-zone-design.md) — (expected: wiki/sources/ctp-topic-7-saas-landing-zone-design.md — source missing) +- [2026-04-18] [ctp-topic-68-introduction-to-redshift](sources/ctp-topic-68-introduction-to-redshift.md) — (expected: wiki/sources/ctp-topic-68-introduction-to-redshift.md — source missing) +- [2026-04-18] [ctp-topic-66-exposing-the-differences-between-postgresql-rds-and-aurora](sources/ctp-topic-66-exposing-the-differences-between-postgresql-rds-and-aurora.md) — (expected: wiki/sources/ctp-topic-66-exposing-the-differences-between-postgresql-rds-and-aurora.md — source missing) +- [2026-04-18] [ctp-topic-58-aws-ec2-image-builder](sources/ctp-topic-58-aws-ec2-image-builder.md) — (expected: wiki/sources/ctp-topic-58-aws-ec2-image-builder.md — source missing) +- [2026-04-18] [ctp-topic-51-architecting-with-aws-purpose-built-databases](sources/ctp-topic-51-architecting-with-aws-purpose-built-databases.md) — (expected: wiki/sources/ctp-topic-51-architecting-with-aws-purpose-built-databases.md — source missing) +- [2026-04-18] [ctp-topic-50-ami-roadmap-for-aws-amis](sources/ctp-topic-50-ami-roadmap-for-aws-amis.md) — (expected: wiki/sources/ctp-topic-50-ami-roadmap-for-aws-amis.md — source missing) +- [2026-04-18] [ctp-topic-47-enterprise-architecture-cloud-standards](sources/ctp-topic-47-enterprise-architecture-cloud-standards.md) — (expected: wiki/sources/ctp-topic-47-enterprise-architecture-cloud-standards.md — source missing) +- [2026-04-18] [ctp-topic-46-netapps-on-aws](sources/ctp-topic-46-netapps-on-aws.md) — (expected: wiki/sources/ctp-topic-46-netapps-on-aws.md — source missing) +- [2026-04-18] [ctp-topic-44-aws-backup-in-micro-focus](sources/ctp-topic-44-aws-backup-in-micro-focus.md) — (expected: wiki/sources/ctp-topic-44-aws-backup-in-micro-focus.md — source missing) +- [2026-04-18] [ctp-topic-40-saas-database-architecture-on-aws-cloud](sources/ctp-topic-40-saas-database-architecture-on-aws-cloud.md) — (expected: wiki/sources/ctp-topic-40-saas-database-architecture-on-aws-cloud.md — source missing) +- [2026-04-18] [ctp-topic-35-aws-landing-zone-design-refresher-saas-labs](sources/ctp-topic-35-aws-landing-zone-design-refresher-saas-labs.md) — (expected: wiki/sources/ctp-topic-35-aws-landing-zone-design-refresher-saas-labs.md — source missing) +- [2026-04-18] [ctp-topic-34-azure-landing-zone-architecture-overview](sources/ctp-topic-34-azure-landing-zone-architecture-overview.md) — (expected: wiki/sources/ctp-topic-34-azure-landing-zone-architecture-overview.md — source missing) +- [2026-04-18] [ctp-topic-28-aws-tag-validation-tool](sources/ctp-topic-28-aws-tag-validation-tool.md) — (expected: wiki/sources/ctp-topic-28-aws-tag-validation-tool.md — source missing) +- [2026-04-18] [ctp-topic-26-standard-ami-build-publish-share-processes](sources/ctp-topic-26-standard-ami-build-publish-share-processes.md) — (expected: wiki/sources/ctp-topic-26-standard-ami-build-publish-share-processes.md — source missing) +- [2026-04-18] [ctp-topic-25-labs-landing-zone-overview-itom-teams](sources/ctp-topic-25-labs-landing-zone-overview-itom-teams.md) — (expected: wiki/sources/ctp-topic-25-labs-landing-zone-overview-itom-teams.md — source missing) +- [2026-04-18] [ctp-topic-17-active-directory-services-in-gruntwork-aws-lzs](sources/ctp-topic-17-active-directory-services-in-gruntwork-aws-lzs.md) — (expected: wiki/sources/ctp-topic-17-active-directory-services-in-gruntwork-aws-lzs.md — source missing) +- [2026-04-18] [ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i](sources/ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i.md) — (expected: wiki/sources/ctp-topic-14-octane-hub-on-aws-real-life-experience-moving-production-services-i.md — source missing) +- [2026-04-18] [ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security](sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md) — (expected: wiki/sources/ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security.md — source missing) +- [2026-04-18] [ctp-topic-1-gruntwork-landing-zone-architecture](sources/ctp-topic-1-gruntwork-landing-zone-architecture.md) — (expected: wiki/sources/ctp-topic-1-gruntwork-landing-zone-architecture.md — source missing) +- [2026-04-18] [blogwatcher-daily收藏](sources/blogwatcher-daily收藏.md) — (expected: wiki/sources/blogwatcher-daily收藏.md — source missing) +- [2026-04-18] [mac必装软件清单-2026-04-17](sources/mac必装软件清单-2026-04-17.md) — (expected: wiki/sources/mac必装软件清单-2026-04-17.md — source missing) +- [2026-04-18] [wsl2-启动与网络配置指南](sources/wsl2-启动与网络配置指南.md) — (expected: wiki/sources/wsl2-启动与网络配置指南.md — source missing) +- [2026-04-18] [install-wsl](sources/install-wsl.md) — (expected: wiki/sources/install-wsl.md — source missing) +- [2026-04-18] [fireworks-tech-graph](sources/fireworks-tech-graph.md) — (expected: wiki/sources/fireworks-tech-graph.md — source missing) +- [2026-04-17] [nano-banana-pro-prompting-guide-strategies-1](sources/nano-banana-pro-prompting-guide-strategies-1.md) — (expected: wiki/sources/nano-banana-pro-prompting-guide-strategies-1.md — source missing) +- [2026-04-17] [gog-cli-安装配置指南](sources/gog-cli-安装配置指南.md) — (expected: wiki/sources/gog-cli-安装配置指南.md — source missing) +- [2026-04-17] [可自动化-可扩展-ai增强的电商数据采集与处理系统](sources/可自动化-可扩展-ai增强的电商数据采集与处理系统.md) — (expected: wiki/sources/可自动化-可扩展-ai增强的电商数据采集与处理系统.md — source missing) +- [2026-04-17] [如何传输docker-images-并且在另一个docker安装](sources/如何传输docker-images-并且在另一个docker安装.md) — (expected: wiki/sources/如何传输docker-images-并且在另一个docker安装.md — source missing) +- [2026-04-17] [DevOps Maturity Model From Traditional IT to Advanced DevOps](sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md) +- [2026-04-17] [DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation](sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md) +- [2026-04-17] [todoist-task-manager](sources/todoist-task-manager.md) — (expected: wiki/sources/todoist-task-manager.md — source missing) +- [2026-04-17] [project-state-management](sources/project-state-management.md) — (expected: wiki/sources/project-state-management.md — source missing) +- [2026-04-17] [polymarket-autopilot](sources/polymarket-autopilot.md) — (expected: wiki/sources/polymarket-autopilot.md — source missing) +- [2026-04-17] [ai-memory-tools-two-camps](sources/ai-memory-tools-two-camps.md) — (expected: wiki/sources/ai-memory-tools-two-camps.md — source missing) +- [2026-04-17] [教學-chatgpt-先做知識整理-再讓-canva-gamma-ai-輸出簡報](sources/教學-chatgpt-先做知識整理-再讓-canva-gamma-ai-輸出簡報.md) — (expected: wiki/sources/教學-chatgpt-先做知識整理-再讓-canva-gamma-ai-輸出簡報.md — source missing) +- [2026-04-17] [在-ubuntu-安装-ollama-并运行-qwen2-5‑coder-7b](sources/在-ubuntu-安装-ollama-并运行-qwen2-5‑coder-7b.md) — (expected: wiki/sources/在-ubuntu-安装-ollama-并运行-qwen2-5‑coder-7b.md — source missing) +- [2026-04-17] [codecrafters-iobuild-your-own-x-master-programming-by-recreating-your-favorite-technologies-from-scratch](sources/codecrafters-iobuild-your-own-x-master-programming-by-recreating-your-favorite-technologies-from-scratch.md) — (expected: wiki/sources/codecrafters-iobuild-your-own-x-master-programming-by-recreating-your-favorite-technologies-from-scratch.md — source missing) +- [2026-04-17] [building-your-quartz](sources/building-your-quartz.md) — (expected: wiki/sources/building-your-quartz.md — source missing) +- [2026-04-17] [how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets](sources/how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets.md) — (expected: wiki/sources/how-to-simplify-multi-account-deployments-monitoring-centralized-logs-for-aws-cloudformation-stacksets.md — source missing) +- [2026-04-16] [obsidian-官方-cli-命令全景速查表](sources/obsidian-官方-cli-命令全景速查表.md) — (expected: wiki/sources/obsidian-官方-cli-命令全景速查表.md — source missing) +- [2026-04-16] [obsidian-cli](sources/obsidian-cli.md) — (expected: wiki/sources/obsidian-cli.md — source missing) +- [2026-04-16] [learn-ai-for-free-directly-from-top-companies](sources/learn-ai-for-free-directly-from-top-companies.md) — (expected: wiki/sources/learn-ai-for-free-directly-from-top-companies.md — source missing) +- [2026-04-14] [ubuntu-安装-frp-0-65-0-x86_64-操作笔记](sources/ubuntu-安装-frp-0-65-0-x86_64-操作笔记.md) — (expected: wiki/sources/ubuntu-安装-frp-0-65-0-x86_64-操作笔记.md — source missing) +- [2026-04-14] [养龙虾5天血泪史-我的ai-agent为什么总失忆-openclaw-记忆调试全记录](sources/养龙虾5天血泪史-我的ai-agent为什么总失忆-openclaw-记忆调试全记录.md) — (expected: wiki/sources/养龙虾5天血泪史-我的ai-agent为什么总失忆-openclaw-记忆调试全记录.md — source missing) +- [2026-04-14] [养虾日记5-深夜与苏轼聊ai-他说-被浪打下去还能爬起来的才叫风流](sources/养虾日记5-深夜与苏轼聊ai-他说-被浪打下去还能爬起来的才叫风流.md) — (expected: wiki/sources/养虾日记5-深夜与苏轼聊ai-他说-被浪打下去还能爬起来的才叫风流.md — source missing) +- [2026-04-14] [养虾日记4-一次「context-limit-exceeded」错误排查-我以为是小问题-结果踩了大坑](sources/养虾日记4-一次「context-limit-exceeded」错误排查-我以为是小问题-结果踩了大坑.md) — (expected: wiki/sources/养虾日记4-一次「context-limit-exceeded」错误排查-我以为是小问题-结果踩了大坑.md — source missing) +- [2026-04-14] [养虾日记3-用-obsidian-gitea-为-ai-助手构建持久化笔记系统](sources/养虾日记3-用-obsidian-gitea-为-ai-助手构建持久化笔记系统.md) — (expected: wiki/sources/养虾日记3-用-obsidian-gitea-为-ai-助手构建持久化笔记系统.md — source missing) +- [2026-04-14] [养虾日记2-让agent更懂你-openclaw-self-improving-复盘实战案例分享](sources/养虾日记2-让agent更懂你-openclaw-self-improving-复盘实战案例分享.md) — (expected: wiki/sources/养虾日记2-让agent更懂你-openclaw-self-improving-复盘实战案例分享.md — source missing) +- [2026-04-14] [养虾日记1-我用-openclaw-管了-28-万张照片-一次真实的多设备照片整理实战](sources/养虾日记1-我用-openclaw-管了-28-万张照片-一次真实的多设备照片整理实战.md) — (expected: wiki/sources/养虾日记1-我用-openclaw-管了-28-万张照片-一次真实的多设备照片整理实战.md — source missing) +- [2026-04-14] [不谈技术-普通人该怎么在ai时代赚钱](sources/不谈技术-普通人该怎么在ai时代赚钱.md) — (expected: wiki/sources/不谈技术-普通人该怎么在ai时代赚钱.md — source missing) +- [2026-04-14] [清华出的deepseek使用手册-104页-真的是太厉害了-免费领取](sources/清华出的deepseek使用手册-104页-真的是太厉害了-免费领取.md) — (expected: wiki/sources/清华出的deepseek使用手册-104页-真的是太厉害了-免费领取.md — source missing) +- [2026-04-14] [我的工具集](sources/我的工具集.md) — (expected: wiki/sources/我的工具集.md — source missing) +- [2026-04-14] [开发经验与项目规范整理文档](sources/开发经验与项目规范整理文档.md) — (expected: wiki/sources/开发经验与项目规范整理文档.md — source missing) +- [2026-04-14] [使用claude自动生成n8n工作流的实操教程](sources/使用claude自动生成n8n工作流的实操教程.md) — (expected: wiki/sources/使用claude自动生成n8n工作流的实操教程.md — source missing) +- [2026-04-14] [n8n-claude-通过自然语言自动化工作流](sources/n8n-claude-通过自然语言自动化工作流.md) — (expected: wiki/sources/n8n-claude-通过自然语言自动化工作流.md — source missing) +- [2026-04-14] [n8n-full-tutorial-building-ai-agents-in-2025-for-beginners](sources/n8n-full-tutorial-building-ai-agents-in-2025-for-beginners.md) — (expected: wiki/sources/n8n-full-tutorial-building-ai-agents-in-2025-for-beginners.md — source missing) +- [2026-04-14] [n8n-docker-install-update](sources/n8n-docker-install-update.md) — (expected: wiki/sources/n8n-docker-install-update.md — source missing) +- [2026-04-14] [n8n-configure-telegram-trigger](sources/n8n-configure-telegram-trigger.md) — (expected: wiki/sources/n8n-configure-telegram-trigger.md — source missing) +- [2026-04-14] [如何在项目里安装claude-code-templates-skills](sources/如何在项目里安装claude-code-templates-skills.md) — (expected: wiki/sources/如何在项目里安装claude-code-templates-skills.md — source missing) +- [2026-04-14] [如何在ubuntu上安装opencode并配置vibe-kanban](sources/如何在ubuntu上安装opencode并配置vibe-kanban.md) — (expected: wiki/sources/如何在ubuntu上安装opencode并配置vibe-kanban.md — source missing) +- [2026-04-14] [在ubuntu上安装vibe-kanban](sources/在ubuntu上安装vibe-kanban.md) — (expected: wiki/sources/在ubuntu上安装vibe-kanban.md — source missing) +- [2026-04-14] [vibe-coding经验收集](sources/vibe-coding经验收集.md) — (expected: wiki/sources/vibe-coding经验收集.md — source missing) +- [2026-04-14] [vibe-kanban-opencode-在-ubuntu-server-上安装与管理指南](sources/vibe-kanban-opencode-在-ubuntu-server-上安装与管理指南.md) — (expected: wiki/sources/vibe-kanban-opencode-在-ubuntu-server-上安装与管理指南.md — source missing) +- [2026-04-14] [useful-prompt-lib](sources/useful-prompt-lib.md) — (expected: wiki/sources/useful-prompt-lib.md — source missing) +- [2026-04-14] [trae远程开发部署指南](sources/trae远程开发部署指南.md) — (expected: wiki/sources/trae远程开发部署指南.md — source missing) +- [2026-04-14] [these-6-linux-apps-let-you-monitor-system-resources-in-style](sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md) — (expected: wiki/sources/these-6-linux-apps-let-you-monitor-system-resources-in-style.md — source missing) +- [2026-04-14] [tiktok-pm-python-django-project](sources/tiktok-pm-python-django-project.md) — (expected: wiki/sources/tiktok-pm-python-django-project.md — source missing) +- [2026-04-14] [mcp在cursor中的集成与应用详解](sources/mcp在cursor中的集成与应用详解.md) — (expected: wiki/sources/mcp在cursor中的集成与应用详解.md — source missing) +- [2026-04-14] [how-to-get-youtube-channel-id](sources/how-to-get-youtube-channel-id.md) — (expected: wiki/sources/how-to-get-youtube-channel-id.md — source missing) +- [2026-04-14] [macos-创建与解除-symbolic-link-openclaw-目录映射](sources/macos-创建与解除-symbolic-link-openclaw-目录映射.md) — (expected: wiki/sources/macos-创建与解除-symbolic-link-openclaw-目录映射.md — source missing) +- [2026-04-14] [mac-mini-安装-frp-0-65-0-arm64-操作笔记](sources/mac-mini-安装-frp-0-65-0-arm64-操作笔记.md) — (expected: wiki/sources/mac-mini-安装-frp-0-65-0-arm64-操作笔记.md — source missing) +- [2026-04-14] [家庭网络环境概览_2026-04-03](sources/家庭网络环境概览_2026-04-03.md) — (expected: wiki/sources/家庭网络环境概览_2026-04-03.md — source missing) +- [2026-04-14] [群晖nas科学上网方法](sources/群晖nas科学上网方法.md) — (expected: wiki/sources/群晖nas科学上网方法.md — source missing) +- [2026-04-14] [网件rax50路由器刷梅林固件与科学上网插件安装教程](sources/网件rax50路由器刷梅林固件与科学上网插件安装教程.md) — (expected: wiki/sources/网件rax50路由器刷梅林固件与科学上网插件安装教程.md — source missing) +- [2026-04-14] [用docker安装transmission](sources/用docker安装transmission.md) — (expected: wiki/sources/用docker安装transmission.md — source missing) +- [2026-04-14] [用docker安装it-tools](sources/用docker安装it-tools.md) — (expected: wiki/sources/用docker安装it-tools.md — source missing) +- [2026-04-14] [用docker安装portainer](sources/用docker安装portainer.md) — (expected: wiki/sources/用docker安装portainer.md — source missing) +- [2026-04-14] [用docker安装jellyfin](sources/用docker安装jellyfin.md) — (expected: wiki/sources/用docker安装jellyfin.md — source missing) +- [2026-04-14] [用docker安装homarr](sources/用docker安装homarr.md) — (expected: wiki/sources/用docker安装homarr.md — source missing) +- [2026-04-14] [用docker安装apache-superset](sources/用docker安装apache-superset.md) — (expected: wiki/sources/用docker安装apache-superset.md — source missing) +- [2026-04-14] [用docker中安装navidrome](sources/用docker中安装navidrome.md) — (expected: wiki/sources/用docker中安装navidrome.md — source missing) +- [2026-04-14] [家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox](sources/家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox.md) — (expected: wiki/sources/家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox.md — source missing) +- [2026-04-14] [安装v2rayn](sources/安装v2rayn.md) — (expected: wiki/sources/安装v2rayn.md — source missing) +- [2026-04-14] [安装ubuntu-24-04-2在hp-zbook工作站笔记本上](sources/安装ubuntu-24-04-2在hp-zbook工作站笔记本上.md) — (expected: wiki/sources/安装ubuntu-24-04-2在hp-zbook工作站笔记本上.md — source missing) +- [2026-04-14] [如何用指纹浏览器安全注册并订阅claude-pro会员全攻略](sources/如何用指纹浏览器安全注册并订阅claude-pro会员全攻略.md) — (expected: wiki/sources/如何用指纹浏览器安全注册并订阅claude-pro会员全攻略.md — source missing) +- [2026-04-14] [如何在ubuntu-server安装-docker-docker-compose](sources/如何在ubuntu-server安装-docker-docker-compose.md) — (expected: wiki/sources/如何在ubuntu-server安装-docker-docker-compose.md — source missing) +- [2026-04-14] [如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹](sources/如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹.md) — (expected: wiki/sources/如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹.md — source missing) +- [2026-04-14] [如何判别你的linux-服务器是-x64-也就是-x86_64-还是-arm64](sources/如何判别你的linux-服务器是-x64-也就是-x86_64-还是-arm64.md) — (expected: wiki/sources/如何判别你的linux-服务器是-x64-也就是-x86_64-还是-arm64.md — source missing) +- [2026-04-14] [如何删除旧的废弃的docker-container-volume](sources/如何删除旧的废弃的docker-container-volume.md) — (expected: wiki/sources/如何删除旧的废弃的docker-container-volume.md — source missing) +- [2026-04-14] [在ubuntu上通过vps-内网反向代理实现域名访问内网穿透](sources/在ubuntu上通过vps-内网反向代理实现域名访问内网穿透.md) — (expected: wiki/sources/在ubuntu上通过vps-内网反向代理实现域名访问内网穿透.md — source missing) +- [2026-04-14] [在synology-nas上安装clouddrive2](sources/在synology-nas上安装clouddrive2.md) — (expected: wiki/sources/在synology-nas上安装clouddrive2.md — source missing) +- [2026-04-14] [ubuntu禁用合盖休眠](sources/ubuntu禁用合盖休眠.md) — (expected: wiki/sources/ubuntu禁用合盖休眠.md — source missing) +- [2026-04-14] [ubuntu用rustdesk远程登录出现不能使用wayland登录的错误](sources/ubuntu用rustdesk远程登录出现不能使用wayland登录的错误.md) — (expected: wiki/sources/ubuntu用rustdesk远程登录出现不能使用wayland登录的错误.md — source missing) +- [2026-04-14] [ubuntu服务器通过rsync实现日常增量备份](sources/ubuntu服务器通过rsync实现日常增量备份.md) — (expected: wiki/sources/ubuntu服务器通过rsync实现日常增量备份.md — source missing) +- [2026-04-14] [ubuntu-server科学上网](sources/ubuntu-server科学上网.md) — (expected: wiki/sources/ubuntu-server科学上网.md — source missing) +- [2026-04-14] [ubuntu-24-04-enable-ssh](sources/ubuntu-24-04-enable-ssh.md) — (expected: wiki/sources/ubuntu-24-04-enable-ssh.md — source missing) +- [2026-04-14] [rax50-路由器-更新merlin-clash订阅](sources/rax50-路由器-更新merlin-clash订阅.md) — (expected: wiki/sources/rax50-路由器-更新merlin-clash订阅.md — source missing) +- [2026-04-14] [nodewarden-把-bitwarden-搬上-cloudflare-workers-彻底告别服务器](sources/nodewarden-把-bitwarden-搬上-cloudflare-workers-彻底告别服务器.md) — (expected: wiki/sources/nodewarden-把-bitwarden-搬上-cloudflare-workers-彻底告别服务器.md — source missing) +- [2026-04-14] [mysql-mariadb-数据库详细信息](sources/mysql-mariadb-数据库详细信息.md) — (expected: wiki/sources/mysql-mariadb-数据库详细信息.md — source missing) +- [2026-04-14] [minio-zipline-自托管图床应用安装教程](sources/minio-zipline-自托管图床应用安装教程.md) — (expected: wiki/sources/minio-zipline-自托管图床应用安装教程.md — source missing) +- [2026-04-14] [linux-运维必会的-150-个命令](sources/linux-运维必会的-150-个命令.md) — (expected: wiki/sources/linux-运维必会的-150-个命令.md — source missing) +- [2026-04-14] [clonezilla对ubuntu-server进行全盘镜像备份](sources/clonezilla对ubuntu-server进行全盘镜像备份.md) — (expected: wiki/sources/clonezilla对ubuntu-server进行全盘镜像备份.md — source missing) +- [2026-04-14] [3x-ui-xray-on-bandwagonvps](sources/3x-ui-xray-on-bandwagonvps.md) — (expected: wiki/sources/3x-ui-xray-on-bandwagonvps.md — source missing) +- [2026-04-14] [通过vps-内网反向代理实现域名访问内网穿透](sources/通过vps-内网反向代理实现域名访问内网穿透.md) — (expected: wiki/sources/通过vps-内网反向代理实现域名访问内网穿透.md — source missing) +- [2026-04-14] [mac-mini-服务器配置-防止自动锁屏与睡眠](sources/mac-mini-服务器配置-防止自动锁屏与睡眠.md) — (expected: wiki/sources/mac-mini-服务器配置-防止自动锁屏与睡眠.md — source missing) +- [2026-04-14] [install-apache-superset-in-docker](sources/install-apache-superset-in-docker.md) — (expected: wiki/sources/install-apache-superset-in-docker.md — source missing) +- [2026-04-14] [cursor-2-0初学者使用指南](sources/cursor-2-0初学者使用指南.md) — (expected: wiki/sources/cursor-2-0初学者使用指南.md — source missing) +- [2026-04-14] [what-is-devsecops-best-practices-benefits-and-tools](sources/what-is-devsecops-best-practices-benefits-and-tools.md) — (expected: wiki/sources/what-is-devsecops-best-practices-benefits-and-tools.md — source missing) +- [2026-04-14] [What I Know About Cloud Service Delivery 1](sources/what-i-know-about-cloud-service-delivery-1.md) +- [2026-04-14] [understanding-complete-itsm](sources/understanding-complete-itsm.md) — (expected: wiki/sources/understanding-complete-itsm.md — source missing) +- [2026-04-14] [The Myths and Misconceptions About Cloud Computing | LinkedIn](sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md) +- [2026-04-14] [rto-vs-rpo-key-differences-for-modern-disaster-recovery](sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md) — (expected: wiki/sources/rto-vs-rpo-key-differences-for-modern-disaster-recovery.md — source missing) +- [2026-04-14] [How Can a Multi Cloud Strategy Transform Your Business ROI?](sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md) +- [2026-04-14] [how-agentic-ai-can-help-for-cloud-devops](sources/how-agentic-ai-can-help-for-cloud-devops.md) — (expected: wiki/sources/how-agentic-ai-can-help-for-cloud-devops.md — source missing) +- [2026-04-14] [Cloud Maturity Model - A Detailed Guide For Cloud Adoption](sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md) +- [2026-04-14] [Cloud DevOp Maturity - Guideline](sources/cloud-devop-maturity-guideline.md) +- [2026-04-14] [chinatextbook-41-53-gb-中国小学-初中-高中-大学-pdf-教材](sources/chinatextbook-41-53-gb-中国小学-初中-高中-大学-pdf-教材.md) — (expected: wiki/sources/chinatextbook-41-53-gb-中国小学-初中-高中-大学-pdf-教材.md — source missing) +- [2026-04-14] [obsidian最有必要安装的10款插件是这些](sources/obsidian最有必要安装的10款插件是这些.md) — (expected: wiki/sources/obsidian最有必要安装的10款插件是这些.md — source missing) +- [2026-04-14] [obsidian-高效指南-我常用的插件与实用技巧](sources/obsidian-高效指南-我常用的插件与实用技巧.md) — (expected: wiki/sources/obsidian-高效指南-我常用的插件与实用技巧.md — source missing) +- [2026-04-14] [obsidian-tasks-插件-这可能是最适合懒人的任务管理方式](sources/obsidian-tasks-插件-这可能是最适合懒人的任务管理方式.md) — (expected: wiki/sources/obsidian-tasks-插件-这可能是最适合懒人的任务管理方式.md — source missing) +- [2026-04-14] [dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1](sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md) — (expected: wiki/sources/dataview-让我从“笔记黑洞”里逃出来的-obsidian-神器-1.md — source missing) +- [2026-04-14] [谷歌深夜甩出一份-nano-banana-pro提示词指南-手把手教你生产专业级内容-实战案例-提示词模版](sources/谷歌深夜甩出一份-nano-banana-pro提示词指南-手把手教你生产专业级内容-实战案例-提示词模版.md) — (expected: wiki/sources/谷歌深夜甩出一份-nano-banana-pro提示词指南-手把手教你生产专业级内容-实战案例-提示词模版.md — source missing) +- [2026-04-14] [详细-离线部署大模型-ollama-deepseek-open-webui安装使用方法及常见问题解决-1](sources/详细-离线部署大模型-ollama-deepseek-open-webui安装使用方法及常见问题解决-1.md) — (expected: wiki/sources/详细-离线部署大模型-ollama-deepseek-open-webui安装使用方法及常见问题解决-1.md — source missing) +- [2026-04-14] [系统提示词构建原则](sources/系统提示词构建原则.md) — (expected: wiki/sources/系统提示词构建原则.md — source missing) +- [2026-04-14] [文字生成视频网站推荐](sources/文字生成视频网站推荐.md) — (expected: wiki/sources/文字生成视频网站推荐.md — source missing) +- [2026-04-14] [我用-gemini-3-一口气做了-10-个应用-附教程](sources/我用-gemini-3-一口气做了-10-个应用-附教程.md) — (expected: wiki/sources/我用-gemini-3-一口气做了-10-个应用-附教程.md — source missing) +- [2026-04-14] [如何利用sora接口实现视频自动化生成工作流](sources/如何利用sora接口实现视频自动化生成工作流.md) — (expected: wiki/sources/如何利用sora接口实现视频自动化生成工作流.md — source missing) +- [2026-04-14] [如何写出完美的prompt-提示词](sources/如何写出完美的prompt-提示词.md) — (expected: wiki/sources/如何写出完美的prompt-提示词.md — source missing) +- [2026-04-14] [大模型相关术语和框架总结｜llm-mcp-prompt-rag-vllm-token-数据蒸馏](sources/大模型相关术语和框架总结｜llm-mcp-prompt-rag-vllm-token-数据蒸馏.md) — (expected: wiki/sources/大模型相关术语和框架总结｜llm-mcp-prompt-rag-vllm-token-数据蒸馏.md — source missing) +- [2026-04-14] [固定镜头短视频制作的ai全流程解析](sources/固定镜头短视频制作的ai全流程解析.md) — (expected: wiki/sources/固定镜头短视频制作的ai全流程解析.md — source missing) +- [2026-04-14] [全网最全-nano-banana-2-使用指南-2025年12月更新-1](sources/全网最全-nano-banana-2-使用指南-2025年12月更新-1.md) — (expected: wiki/sources/全网最全-nano-banana-2-使用指南-2025年12月更新-1.md — source missing) +- [2026-04-14] [二创视频必不可少-2025年最热门ai工具推荐合集-ai配音-声音克隆](sources/二创视频必不可少-2025年最热门ai工具推荐合集-ai配音-声音克隆.md) — (expected: wiki/sources/二创视频必不可少-2025年最热门ai工具推荐合集-ai配音-声音克隆.md — source missing) +- [2026-04-14] [不会gemini的产品经理真的要被淘汰了-附保姆级prd生成指南](sources/不会gemini的产品经理真的要被淘汰了-附保姆级prd生成指南.md) — (expected: wiki/sources/不会gemini的产品经理真的要被淘汰了-附保姆级prd生成指南.md — source missing) +- [2026-04-14] [一语点醒梦中人](sources/一语点醒梦中人.md) — (expected: wiki/sources/一语点醒梦中人.md — source missing) +- [2026-04-14] [the-picture-they-paint-of-you](sources/the-picture-they-paint-of-you.md) — (expected: wiki/sources/the-picture-they-paint-of-you.md — source missing) +- [2026-04-14] [rag从入门到精通系列1-基础rag](sources/rag从入门到精通系列1-基础rag.md) — (expected: wiki/sources/rag从入门到精通系列1-基础rag.md — source missing) +- [2026-04-14] [openai-chatgpt-个性化定义](sources/openai-chatgpt-个性化定义.md) — (expected: wiki/sources/openai-chatgpt-个性化定义.md — source missing) +- [2026-04-14] [never-write-another-prompt](sources/never-write-another-prompt.md) — (expected: wiki/sources/never-write-another-prompt.md — source missing) +- [2026-04-14] [nano-banana-提示词框架](sources/nano-banana-提示词框架.md) — (expected: wiki/sources/nano-banana-提示词框架.md — source missing) +- [2026-04-14] [multi-agent-system-reliability](sources/multi-agent-system-reliability.md) — (expected: wiki/sources/multi-agent-system-reliability.md — source missing) +- [2026-04-14] [llms-rag-ai-agent-三个到底什么区别](sources/llms-rag-ai-agent-三个到底什么区别.md) — (expected: wiki/sources/llms-rag-ai-agent-三个到底什么区别.md — source missing) +- [2026-04-14] [if-you-have-multiple-interests-do-not-waste-the-next-2-3-years-如果你有多项兴趣爱好-不要浪费接下来的两三年时间](sources/if-you-have-multiple-interests-do-not-waste-the-next-2-3-years-如果你有多项兴趣爱好-不要浪费接下来的两三年时间.md) — (expected: wiki/sources/if-you-have-multiple-interests-do-not-waste-the-next-2-3-years-如果你有多项兴趣爱好-不要浪费接下来的两三年时间.md — source missing) +- [2026-04-14] [how-to-get-the-rss-feed-for-any-youtube-channel](sources/how-to-get-the-rss-feed-for-any-youtube-channel.md) — (expected: wiki/sources/how-to-get-the-rss-feed-for-any-youtube-channel.md — source missing) +- [2026-04-14] [google-神级生产力工具-所有-github-开源平替都找到了](sources/google-神级生产力工具-所有-github-开源平替都找到了.md) — (expected: wiki/sources/google-神级生产力工具-所有-github-开源平替都找到了.md — source missing) +- [2026-04-14] [github-上-5000-人收藏的-vibe-coding-神级指南](sources/github-上-5000-人收藏的-vibe-coding-神级指南.md) — (expected: wiki/sources/github-上-5000-人收藏的-vibe-coding-神级指南.md — source missing) +- [2026-04-14] [designing-for-agentic-ai](sources/designing-for-agentic-ai.md) — (expected: wiki/sources/designing-for-agentic-ai.md — source missing) +- [2026-04-14] [best-7-news-api-data-feeds-ai-news](sources/best-7-news-api-data-feeds-ai-news.md) — (expected: wiki/sources/best-7-news-api-data-feeds-ai-news.md — source missing) +- [2026-04-14] [ai-解决方案专家培训课程](sources/ai-解决方案专家培训课程.md) — (expected: wiki/sources/ai-解决方案专家培训课程.md — source missing) +- [2026-04-14] [a-formalization-of-recursive-self-optimizing-generative-systems](sources/a-formalization-of-recursive-self-optimizing-generative-systems.md) — (expected: wiki/sources/a-formalization-of-recursive-self-optimizing-generative-systems.md — source missing) +- [2026-04-14] [7-ways-i-use-notebooklm-to-make-my-life-easier](sources/7-ways-i-use-notebooklm-to-make-my-life-easier.md) — (expected: wiki/sources/7-ways-i-use-notebooklm-to-make-my-life-easier.md — source missing) +- [2026-04-14] [3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式](sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式.md) — (expected: wiki/sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式.md — source missing) +- [2026-04-14] [3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式-1](sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式-1.md) — (expected: wiki/sources/3-2-万人收藏的-claude-skills-才是-ai-这条路上最值得研究的一套范式-1.md — source missing) +- [2026-04-14] [2025-年-11-个神级-ai-开源平替-github-杀疯了](sources/2025-年-11-个神级-ai-开源平替-github-杀疯了.md) — (expected: wiki/sources/2025-年-11-个神级-ai-开源平替-github-杀疯了.md — source missing) +- [2026-04-14] [14个免费的ai图生视频工具-用ai让图片动起来-ai视频教程-ai自动化工作流定制服务-ai培训学习平台-黑喵大叔](sources/14个免费的ai图生视频工具-用ai让图片动起来-ai视频教程-ai自动化工作流定制服务-ai培训学习平台-黑喵大叔.md) — (expected: wiki/sources/14个免费的ai图生视频工具-用ai让图片动起来-ai视频教程-ai自动化工作流定制服务-ai培训学习平台-黑喵大叔.md — source missing) +- [2026-04-13] [claude-code调用方法总结](sources/claude-code调用方法总结.md) — (expected: wiki/sources/claude-code调用方法总结.md — source missing) +- [2026-04-09] [x-account-analysis](sources/x-account-analysis.md) — (expected: wiki/sources/x-account-analysis.md — source missing) +- [2026-04-09] [phone-call-notifications](sources/phone-call-notifications.md) — (expected: wiki/sources/phone-call-notifications.md — source missing) +- [2026-04-09] [autonomous-game-dev-pipeline](sources/autonomous-game-dev-pipeline.md) — (expected: wiki/sources/autonomous-game-dev-pipeline.md — source missing) +- [2026-04-09] [arxiv-paper-reader](sources/arxiv-paper-reader.md) — (expected: wiki/sources/arxiv-paper-reader.md — source missing) +- [2026-04-09] [semantic-memory-search](sources/semantic-memory-search.md) — (expected: wiki/sources/semantic-memory-search.md — source missing) +- [2026-04-09] [aionui-cowork-desktop](sources/aionui-cowork-desktop.md) — (expected: wiki/sources/aionui-cowork-desktop.md — source missing) +- [2026-04-09] [family-calendar-household-assistant](sources/family-calendar-household-assistant.md) — (expected: wiki/sources/family-calendar-household-assistant.md — source missing) +- [2026-04-09] [multi-source-tech-news-digest](sources/multi-source-tech-news-digest.md) — (expected: wiki/sources/multi-source-tech-news-digest.md — source missing) +- [2026-04-09] [x-twitter-automation](sources/x-twitter-automation.md) — (expected: wiki/sources/x-twitter-automation.md — source missing) +- [2026-04-09] [knowledge-base-rag](sources/knowledge-base-rag.md) — (expected: wiki/sources/knowledge-base-rag.md — source missing) +- [2026-04-09] [personal-crm](sources/personal-crm.md) — (expected: wiki/sources/personal-crm.md — source missing) +- [2026-04-09] [youtube-content-pipeline](sources/youtube-content-pipeline.md) — (expected: wiki/sources/youtube-content-pipeline.md — source missing) +- [2026-04-09] [overnight-mini-app-builder](sources/overnight-mini-app-builder.md) — (expected: wiki/sources/overnight-mini-app-builder.md — source missing) +- [2026-04-09] [local-crm-framework](sources/local-crm-framework.md) — (expected: wiki/sources/local-crm-framework.md — source missing) +- [2026-04-09] [n8n-workflow-orchestration](sources/n8n-workflow-orchestration.md) — (expected: wiki/sources/n8n-workflow-orchestration.md — source missing) +- [2026-04-09] [multi-channel-customer-service](sources/multi-channel-customer-service.md) — (expected: wiki/sources/multi-channel-customer-service.md — source missing) +- [2026-04-09] [second-brain](sources/second-brain.md) — (expected: wiki/sources/second-brain.md — source missing) +- [2026-04-09] [latex-paper-writing](sources/latex-paper-writing.md) — (expected: wiki/sources/latex-paper-writing.md — source missing) +- [2026-04-09] [habit-tracker-accountability-coach](sources/habit-tracker-accountability-coach.md) — (expected: wiki/sources/habit-tracker-accountability-coach.md — source missing) +- [2026-04-09] [dynamic-dashboard](sources/dynamic-dashboard.md) — (expected: wiki/sources/dynamic-dashboard.md — source missing) +- [2026-04-09] [pre-build-idea-validator](sources/pre-build-idea-validator.md) — (expected: wiki/sources/pre-build-idea-validator.md — source missing) +- [2026-04-09] [autonomous-project-management](sources/autonomous-project-management.md) — (expected: wiki/sources/autonomous-project-management.md — source missing) +- [2026-04-09] [daily-reddit-digest](sources/daily-reddit-digest.md) — (expected: wiki/sources/daily-reddit-digest.md — source missing) +- [2026-04-09] [inbox-declutter](sources/inbox-declutter.md) — (expected: wiki/sources/inbox-declutter.md — source missing) +- [2026-04-09] [custom-morning-brief](sources/custom-morning-brief.md) — (expected: wiki/sources/custom-morning-brief.md — source missing) +- [2026-04-09] [market-research-product-factory](sources/market-research-product-factory.md) — (expected: wiki/sources/market-research-product-factory.md — source missing) +- [2026-04-09] [phone-based-personal-assistant](sources/phone-based-personal-assistant.md) — (expected: wiki/sources/phone-based-personal-assistant.md — source missing) +- [2026-04-09] [event-guest-confirmation](sources/event-guest-confirmation.md) — (expected: wiki/sources/event-guest-confirmation.md — source missing) +- [2026-04-09] [multi-channel-assistant](sources/multi-channel-assistant.md) — (expected: wiki/sources/multi-channel-assistant.md — source missing) +- [2026-04-09] [earnings-tracker](sources/earnings-tracker.md) — (expected: wiki/sources/earnings-tracker.md — source missing) +- [2026-04-09] [multi-agent-team](sources/multi-agent-team.md) — (expected: wiki/sources/multi-agent-team.md — source missing) +- [2026-04-09] [health-symptom-tracker](sources/health-symptom-tracker.md) — (expected: wiki/sources/health-symptom-tracker.md — source missing) +- [2026-04-09] [self-healing-home-server](sources/self-healing-home-server.md) — (expected: wiki/sources/self-healing-home-server.md — source missing) +- [2026-04-09] [content-factory](sources/content-factory.md) — (expected: wiki/sources/content-factory.md — source missing) +- [2026-04-09] [daily-youtube-digest](sources/daily-youtube-digest.md) — (expected: wiki/sources/daily-youtube-digest.md — source missing) +- [2026-04-09] [meeting-notes-action-items](sources/meeting-notes-action-items.md) — (expected: wiki/sources/meeting-notes-action-items.md — source missing) +- [2026-04-09] [podcast-production-pipeline](sources/podcast-production-pipeline.md) — (expected: wiki/sources/podcast-production-pipeline.md — source missing) +- [2026-04-09] [万字保姆级教程-90天跑通一人公司模式-2026-03-29](sources/万字保姆级教程-90天跑通一人公司模式-2026-03-29.md) — (expected: wiki/sources/万字保姆级教程-90天跑通一人公司模式-2026-03-29.md — source missing) +- [2026-04-09] [google-5个agent-skill设计模式-2026-03-19](sources/google-5个agent-skill设计模式-2026-03-19.md) — (expected: wiki/sources/google-5个agent-skill设计模式-2026-03-19.md — source missing) +- [2026-04-09] [万字讲透openclaw-workspace深度解析-2026-03-21](sources/万字讲透openclaw-workspace深度解析-2026-03-21.md) — (expected: wiki/sources/万字讲透openclaw-workspace深度解析-2026-03-21.md — source missing) +- [2026-04-09] [电商如何选品-如何找到爆款-选品策略](sources/电商如何选品-如何找到爆款-选品策略.md) — (expected: wiki/sources/电商如何选品-如何找到爆款-选品策略.md — source missing) +- [2026-04-09] [电商视频prompt](sources/电商视频prompt.md) — (expected: wiki/sources/电商视频prompt.md — source missing) +- [2026-04-09] [tiktok-shop-apache-superset-dashboard设计思路](sources/tiktok-shop-apache-superset-dashboard设计思路.md) — (expected: wiki/sources/tiktok-shop-apache-superset-dashboard设计思路.md — source missing) +- [2026-04-09] [做tk跨境思路不对努力白费](sources/做tk跨境思路不对努力白费.md) — (expected: wiki/sources/做tk跨境思路不对努力白费.md — source missing) +- [2026-04-09] [超达物流定价](sources/超达物流定价.md) — (expected: wiki/sources/超达物流定价.md — source missing) +- [2026-04-09] [tk美国面单授权及操作流程](sources/tk美国面单授权及操作流程.md) — (expected: wiki/sources/tk美国面单授权及操作流程.md — source missing) +- [2026-04-09] [scrapy-playwright-抓取tiktok-shop-data](sources/scrapy-playwright-抓取tiktok-shop-data.md) — (expected: wiki/sources/scrapy-playwright-抓取tiktok-shop-data.md — source missing) +- [2026-03-29] [testing-workflow-optimizer](sources/testing-workflow-optimizer.md) — (expected: wiki/sources/testing-workflow-optimizer.md — source missing) +- [2026-03-29] [testing-tool-evaluator](sources/testing-tool-evaluator.md) — (expected: wiki/sources/testing-tool-evaluator.md — source missing) +- [2026-03-29] [testing-test-results-analyzer](sources/testing-test-results-analyzer.md) — (expected: wiki/sources/testing-test-results-analyzer.md — source missing) +- [2026-03-29] [testing-reality-checker](sources/testing-reality-checker.md) — (expected: wiki/sources/testing-reality-checker.md — source missing) +- [2026-03-29] [testing-performance-benchmarker](sources/testing-performance-benchmarker.md) — (expected: wiki/sources/testing-performance-benchmarker.md — source missing) +- [2026-03-29] [testing-evidence-collector](sources/testing-evidence-collector.md) — (expected: wiki/sources/testing-evidence-collector.md — source missing) +- [2026-03-29] [testing-api-tester](sources/testing-api-tester.md) — (expected: wiki/sources/testing-api-tester.md — source missing) +- [2026-03-29] [testing-accessibility-auditor](sources/testing-accessibility-auditor.md) — (expected: wiki/sources/testing-accessibility-auditor.md — source missing) +- [2026-03-29] [support-support-responder](sources/support-support-responder.md) — (expected: wiki/sources/support-support-responder.md — source missing) +- [2026-03-29] [support-legal-compliance-checker](sources/support-legal-compliance-checker.md) — (expected: wiki/sources/support-legal-compliance-checker.md — source missing) +- [2026-03-29] [support-infrastructure-maintainer](sources/support-infrastructure-maintainer.md) — (expected: wiki/sources/support-infrastructure-maintainer.md — source missing) +- [2026-03-29] [support-finance-tracker](sources/support-finance-tracker.md) — (expected: wiki/sources/support-finance-tracker.md — source missing) +- [2026-03-29] [support-executive-summary-generator](sources/support-executive-summary-generator.md) — (expected: wiki/sources/support-executive-summary-generator.md — source missing) +- [2026-03-29] [support-analytics-reporter](sources/support-analytics-reporter.md) — (expected: wiki/sources/support-analytics-reporter.md — source missing) +- [2026-03-29] [scenario-startup-mvp](sources/scenario-startup-mvp.md) — (expected: wiki/sources/scenario-startup-mvp.md — source missing) +- [2026-03-29] [scenario-marketing-campaign](sources/scenario-marketing-campaign.md) — (expected: wiki/sources/scenario-marketing-campaign.md — source missing) +- [2026-03-29] [scenario-incident-response](sources/scenario-incident-response.md) — (expected: wiki/sources/scenario-incident-response.md — source missing) +- [2026-03-29] [scenario-enterprise-feature](sources/scenario-enterprise-feature.md) — (expected: wiki/sources/scenario-enterprise-feature.md — source missing) +- [2026-03-29] [phase-6-operate](sources/phase-6-operate.md) — (expected: wiki/sources/phase-6-operate.md — source missing) +- [2026-03-29] [phase-5-launch](sources/phase-5-launch.md) — (expected: wiki/sources/phase-5-launch.md — source missing) +- [2026-03-29] [phase-4-hardening](sources/phase-4-hardening.md) — (expected: wiki/sources/phase-4-hardening.md — source missing) +- [2026-03-29] [phase-3-build](sources/phase-3-build.md) — (expected: wiki/sources/phase-3-build.md — source missing) +- [2026-03-29] [phase-2-foundation](sources/phase-2-foundation.md) — (expected: wiki/sources/phase-2-foundation.md — source missing) +- [2026-03-29] [phase-1-strategy](sources/phase-1-strategy.md) — (expected: wiki/sources/phase-1-strategy.md — source missing) +- [2026-03-29] [phase-0-discovery](sources/phase-0-discovery.md) — (expected: wiki/sources/phase-0-discovery.md — source missing) +- [2026-03-29] [nexus-strategy](sources/nexus-strategy.md) — (expected: wiki/sources/nexus-strategy.md — source missing) +- [2026-03-29] [handoff-templates](sources/handoff-templates.md) — (expected: wiki/sources/handoff-templates.md — source missing) +- [2026-03-29] [agent-activation-prompts](sources/agent-activation-prompts.md) — (expected: wiki/sources/agent-activation-prompts.md — source missing) +- [2026-03-29] [quickstart](sources/quickstart.md) — (expected: wiki/sources/quickstart.md — source missing) +- [2026-03-29] [executive-brief](sources/executive-brief.md) — (expected: wiki/sources/executive-brief.md — source missing) +- [2026-03-29] [supply-chain-strategist](sources/supply-chain-strategist.md) — (expected: wiki/sources/supply-chain-strategist.md — source missing) +- [2026-03-29] [study-abroad-advisor](sources/study-abroad-advisor.md) — (expected: wiki/sources/study-abroad-advisor.md — source missing) +- [2026-03-29] [specialized-workflow-architect](sources/specialized-workflow-architect.md) — (expected: wiki/sources/specialized-workflow-architect.md — source missing) +- [2026-03-29] [specialized-model-qa](sources/specialized-model-qa.md) — (expected: wiki/sources/specialized-model-qa.md — source missing) +- [2026-03-29] [specialized-mcp-builder](sources/specialized-mcp-builder.md) — (expected: wiki/sources/specialized-mcp-builder.md — source missing) +- [2026-03-29] [specialized-korean-business-navigator](sources/specialized-korean-business-navigator.md) — (expected: wiki/sources/specialized-korean-business-navigator.md — source missing) +- [2026-03-29] [specialized-french-consulting-market](sources/specialized-french-consulting-market.md) — (expected: wiki/sources/specialized-french-consulting-market.md — source missing) +- [2026-03-29] [specialized-document-generator](sources/specialized-document-generator.md) — (expected: wiki/sources/specialized-document-generator.md — source missing) +- [2026-03-29] [specialized-developer-advocate](sources/specialized-developer-advocate.md) — (expected: wiki/sources/specialized-developer-advocate.md — source missing) +- [2026-03-29] [specialized-cultural-intelligence-strategist](sources/specialized-cultural-intelligence-strategist.md) — (expected: wiki/sources/specialized-cultural-intelligence-strategist.md — source missing) +- [2026-03-29] [specialized-civil-engineer](sources/specialized-civil-engineer.md) — (expected: wiki/sources/specialized-civil-engineer.md — source missing) +- [2026-03-29] [sales-data-extraction-agent](sources/sales-data-extraction-agent.md) — (expected: wiki/sources/sales-data-extraction-agent.md — source missing) +- [2026-03-29] [report-distribution-agent](sources/report-distribution-agent.md) — (expected: wiki/sources/report-distribution-agent.md — source missing) +- [2026-03-29] [recruitment-specialist](sources/recruitment-specialist.md) — (expected: wiki/sources/recruitment-specialist.md — source missing) +- [2026-03-29] [lsp-index-engineer](sources/lsp-index-engineer.md) — (expected: wiki/sources/lsp-index-engineer.md — source missing) +- [2026-03-29] [identity-graph-operator](sources/identity-graph-operator.md) — (expected: wiki/sources/identity-graph-operator.md — source missing) +- [2026-03-29] [healthcare-marketing-compliance](sources/healthcare-marketing-compliance.md) — (expected: wiki/sources/healthcare-marketing-compliance.md — source missing) +- [2026-03-29] [government-digital-presales-consultant](sources/government-digital-presales-consultant.md) — (expected: wiki/sources/government-digital-presales-consultant.md — source missing) +- [2026-03-29] [data-consolidation-agent](sources/data-consolidation-agent.md) — (expected: wiki/sources/data-consolidation-agent.md — source missing) +- [2026-03-29] [corporate-training-designer](sources/corporate-training-designer.md) — (expected: wiki/sources/corporate-training-designer.md — source missing) +- [2026-03-29] [compliance-auditor](sources/compliance-auditor.md) — (expected: wiki/sources/compliance-auditor.md — source missing) +- [2026-03-29] [blockchain-security-auditor](sources/blockchain-security-auditor.md) — (expected: wiki/sources/blockchain-security-auditor.md — source missing) +- [2026-03-29] [automation-governance-architect](sources/automation-governance-architect.md) — (expected: wiki/sources/automation-governance-architect.md — source missing) +- [2026-03-29] [agents-orchestrator](sources/agents-orchestrator.md) — (expected: wiki/sources/agents-orchestrator.md — source missing) +- [2026-03-29] [agentic-identity-trust](sources/agentic-identity-trust.md) — (expected: wiki/sources/agentic-identity-trust.md — source missing) +- [2026-03-29] [accounts-payable-agent](sources/accounts-payable-agent.md) — (expected: wiki/sources/accounts-payable-agent.md — source missing) +- [2026-03-29] [xr-interface-architect](sources/xr-interface-architect.md) — (expected: wiki/sources/xr-interface-architect.md — source missing) +- [2026-03-29] [xr-immersive-developer](sources/xr-immersive-developer.md) — (expected: wiki/sources/xr-immersive-developer.md — source missing) +- [2026-03-29] [xr-cockpit-interaction-specialist](sources/xr-cockpit-interaction-specialist.md) — (expected: wiki/sources/xr-cockpit-interaction-specialist.md — source missing) +- [2026-03-29] [visionos-spatial-engineer](sources/visionos-spatial-engineer.md) — (expected: wiki/sources/visionos-spatial-engineer.md — source missing) +- [2026-03-29] [terminal-integration-specialist](sources/terminal-integration-specialist.md) — (expected: wiki/sources/terminal-integration-specialist.md — source missing) +- [2026-03-29] [macos-spatial-metal-engineer](sources/macos-spatial-metal-engineer.md) — (expected: wiki/sources/macos-spatial-metal-engineer.md — source missing) +- [2026-03-29] [sales-proposal-strategist](sources/sales-proposal-strategist.md) — (expected: wiki/sources/sales-proposal-strategist.md — source missing) +- [2026-03-29] [sales-pipeline-analyst](sources/sales-pipeline-analyst.md) — (expected: wiki/sources/sales-pipeline-analyst.md — source missing) +- [2026-03-29] [sales-outbound-strategist](sources/sales-outbound-strategist.md) — (expected: wiki/sources/sales-outbound-strategist.md — source missing) +- [2026-03-29] [sales-engineer](sources/sales-engineer.md) — (expected: wiki/sources/sales-engineer.md — source missing) +- [2026-03-29] [sales-discovery-coach](sources/sales-discovery-coach.md) — (expected: wiki/sources/sales-discovery-coach.md — source missing) +- [2026-03-29] [sales-deal-strategist](sources/sales-deal-strategist.md) — (expected: wiki/sources/sales-deal-strategist.md — source missing) +- [2026-03-29] [sales-coach](sources/sales-coach.md) — (expected: wiki/sources/sales-coach.md — source missing) +- [2026-03-29] [sales-account-strategist](sources/sales-account-strategist.md) — (expected: wiki/sources/sales-account-strategist.md — source missing) +- [2026-03-29] [project-manager-senior](sources/project-manager-senior.md) — (expected: wiki/sources/project-manager-senior.md — source missing) +- [2026-03-29] [project-management-studio-producer](sources/project-management-studio-producer.md) — (expected: wiki/sources/project-management-studio-producer.md — source missing) +- [2026-03-29] [project-management-studio-operations](sources/project-management-studio-operations.md) — (expected: wiki/sources/project-management-studio-operations.md — source missing) +- [2026-03-29] [project-management-project-shepherd](sources/project-management-project-shepherd.md) — (expected: wiki/sources/project-management-project-shepherd.md — source missing) +- [2026-03-29] [project-management-jira-workflow-steward](sources/project-management-jira-workflow-steward.md) — (expected: wiki/sources/project-management-jira-workflow-steward.md — source missing) +- [2026-03-29] [project-management-experiment-tracker](sources/project-management-experiment-tracker.md) — (expected: wiki/sources/project-management-experiment-tracker.md — source missing) +- [2026-03-29] [product-trend-researcher](sources/product-trend-researcher.md) — (expected: wiki/sources/product-trend-researcher.md — source missing) +- [2026-03-29] [product-sprint-prioritizer](sources/product-sprint-prioritizer.md) — (expected: wiki/sources/product-sprint-prioritizer.md — source missing) +- [2026-03-29] [product-manager](sources/product-manager.md) — (expected: wiki/sources/product-manager.md — source missing) +- [2026-03-29] [product-feedback-synthesizer](sources/product-feedback-synthesizer.md) — (expected: wiki/sources/product-feedback-synthesizer.md — source missing) +- [2026-03-29] [product-behavioral-nudge-engine](sources/product-behavioral-nudge-engine.md) — (expected: wiki/sources/product-behavioral-nudge-engine.md — source missing) +- [2026-03-29] [paid-media-tracking-specialist](sources/paid-media-tracking-specialist.md) — (expected: wiki/sources/paid-media-tracking-specialist.md — source missing) +- [2026-03-29] [paid-media-search-query-analyst](sources/paid-media-search-query-analyst.md) — (expected: wiki/sources/paid-media-search-query-analyst.md — source missing) +- [2026-03-29] [paid-media-programmatic-buyer](sources/paid-media-programmatic-buyer.md) — (expected: wiki/sources/paid-media-programmatic-buyer.md — source missing) +- [2026-03-29] [paid-media-ppc-strategist](sources/paid-media-ppc-strategist.md) — (expected: wiki/sources/paid-media-ppc-strategist.md — source missing) +- [2026-03-29] [paid-media-paid-social-strategist](sources/paid-media-paid-social-strategist.md) — (expected: wiki/sources/paid-media-paid-social-strategist.md — source missing) +- [2026-03-29] [paid-media-creative-strategist](sources/paid-media-creative-strategist.md) — (expected: wiki/sources/paid-media-creative-strategist.md — source missing) +- [2026-03-29] [paid-media-auditor](sources/paid-media-auditor.md) — (expected: wiki/sources/paid-media-auditor.md — source missing) +- [2026-03-29] [marketing-zhihu-strategist](sources/marketing-zhihu-strategist.md) — (expected: wiki/sources/marketing-zhihu-strategist.md — source missing) +- [2026-03-29] [marketing-xiaohongshu-specialist](sources/marketing-xiaohongshu-specialist.md) — (expected: wiki/sources/marketing-xiaohongshu-specialist.md — source missing) +- [2026-03-29] [marketing-weibo-strategist](sources/marketing-weibo-strategist.md) — (expected: wiki/sources/marketing-weibo-strategist.md — source missing) +- [2026-03-29] [marketing-wechat-official-account](sources/marketing-wechat-official-account.md) — (expected: wiki/sources/marketing-wechat-official-account.md — source missing) +- [2026-03-29] [marketing-video-optimization-specialist](sources/marketing-video-optimization-specialist.md) — (expected: wiki/sources/marketing-video-optimization-specialist.md — source missing) +- [2026-03-29] [marketing-twitter-engager](sources/marketing-twitter-engager.md) — (expected: wiki/sources/marketing-twitter-engager.md — source missing) +- [2026-03-29] [marketing-tiktok-strategist](sources/marketing-tiktok-strategist.md) — (expected: wiki/sources/marketing-tiktok-strategist.md — source missing) +- [2026-03-29] [marketing-social-media-strategist](sources/marketing-social-media-strategist.md) — (expected: wiki/sources/marketing-social-media-strategist.md — source missing) +- [2026-03-29] [marketing-short-video-editing-coach](sources/marketing-short-video-editing-coach.md) — (expected: wiki/sources/marketing-short-video-editing-coach.md — source missing) +- [2026-03-29] [marketing-reddit-community-builder](sources/marketing-reddit-community-builder.md) — (expected: wiki/sources/marketing-reddit-community-builder.md — source missing) +- [2026-03-29] [marketing-private-domain-operator](sources/marketing-private-domain-operator.md) — (expected: wiki/sources/marketing-private-domain-operator.md — source missing) +- [2026-03-29] [marketing-podcast-strategist](sources/marketing-podcast-strategist.md) — (expected: wiki/sources/marketing-podcast-strategist.md — source missing) +- [2026-03-29] [marketing-livestream-commerce-coach](sources/marketing-livestream-commerce-coach.md) — (expected: wiki/sources/marketing-livestream-commerce-coach.md — source missing) +- [2026-03-29] [marketing-linkedin-content-creator](sources/marketing-linkedin-content-creator.md) — (expected: wiki/sources/marketing-linkedin-content-creator.md — source missing) +- [2026-03-29] [marketing-kuaishou-strategist](sources/marketing-kuaishou-strategist.md) — (expected: wiki/sources/marketing-kuaishou-strategist.md — source missing) +- [2026-03-29] [marketing-instagram-curator](sources/marketing-instagram-curator.md) — (expected: wiki/sources/marketing-instagram-curator.md — source missing) +- [2026-03-29] [marketing-growth-hacker](sources/marketing-growth-hacker.md) — (expected: wiki/sources/marketing-growth-hacker.md — source missing) +- [2026-03-29] [marketing-douyin-strategist](sources/marketing-douyin-strategist.md) — (expected: wiki/sources/marketing-douyin-strategist.md — source missing) +- [2026-03-29] [marketing-cross-border-ecommerce](sources/marketing-cross-border-ecommerce.md) — (expected: wiki/sources/marketing-cross-border-ecommerce.md — source missing) +- [2026-03-29] [marketing-content-creator](sources/marketing-content-creator.md) — (expected: wiki/sources/marketing-content-creator.md — source missing) +- [2026-03-29] [marketing-china-market-localization-strategist](sources/marketing-china-market-localization-strategist.md) — (expected: wiki/sources/marketing-china-market-localization-strategist.md — source missing) +- [2026-03-29] [marketing-china-ecommerce-operator](sources/marketing-china-ecommerce-operator.md) — (expected: wiki/sources/marketing-china-ecommerce-operator.md — source missing) +- [2026-03-29] [marketing-carousel-growth-engine](sources/marketing-carousel-growth-engine.md) — (expected: wiki/sources/marketing-carousel-growth-engine.md — source missing) +- [2026-03-29] [marketing-book-co-author](sources/marketing-book-co-author.md) — (expected: wiki/sources/marketing-book-co-author.md — source missing) +- [2026-03-29] [marketing-bilibili-content-strategist](sources/marketing-bilibili-content-strategist.md) — (expected: wiki/sources/marketing-bilibili-content-strategist.md — source missing) +- [2026-03-29] [marketing-baidu-seo-specialist](sources/marketing-baidu-seo-specialist.md) — (expected: wiki/sources/marketing-baidu-seo-specialist.md — source missing) +- [2026-03-29] [marketing-app-store-optimizer](sources/marketing-app-store-optimizer.md) — (expected: wiki/sources/marketing-app-store-optimizer.md — source missing) +- [2026-03-29] [marketing-ai-citation-strategist](sources/marketing-ai-citation-strategist.md) — (expected: wiki/sources/marketing-ai-citation-strategist.md — source missing) +- [2026-03-29] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-03-29] [backend-architect-with-memory](sources/backend-architect-with-memory.md) — (expected: wiki/sources/backend-architect-with-memory.md — source missing) +- [2026-03-29] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-03-29] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-03-29] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-03-29] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-03-29] [unreal-world-builder](sources/unreal-world-builder.md) — (expected: wiki/sources/unreal-world-builder.md — source missing) +- [2026-03-29] [unreal-technical-artist](sources/unreal-technical-artist.md) — (expected: wiki/sources/unreal-technical-artist.md — source missing) +- [2026-03-29] [unreal-systems-engineer](sources/unreal-systems-engineer.md) — (expected: wiki/sources/unreal-systems-engineer.md — source missing) +- [2026-03-29] [unreal-multiplayer-architect](sources/unreal-multiplayer-architect.md) — (expected: wiki/sources/unreal-multiplayer-architect.md — source missing) +- [2026-03-29] [unity-shader-graph-artist](sources/unity-shader-graph-artist.md) — (expected: wiki/sources/unity-shader-graph-artist.md — source missing) +- [2026-03-29] [unity-multiplayer-engineer](sources/unity-multiplayer-engineer.md) — (expected: wiki/sources/unity-multiplayer-engineer.md — source missing) +- [2026-03-29] [unity-editor-tool-developer](sources/unity-editor-tool-developer.md) — (expected: wiki/sources/unity-editor-tool-developer.md — source missing) +- [2026-03-29] [unity-architect](sources/unity-architect.md) — (expected: wiki/sources/unity-architect.md — source missing) +- [2026-03-29] [technical-artist](sources/technical-artist.md) — (expected: wiki/sources/technical-artist.md — source missing) +- [2026-03-29] [roblox-systems-scripter](sources/roblox-systems-scripter.md) — (expected: wiki/sources/roblox-systems-scripter.md — source missing) +- [2026-03-29] [roblox-experience-designer](sources/roblox-experience-designer.md) — (expected: wiki/sources/roblox-experience-designer.md — source missing) +- [2026-03-29] [roblox-avatar-creator](sources/roblox-avatar-creator.md) — (expected: wiki/sources/roblox-avatar-creator.md — source missing) +- [2026-03-29] [narrative-designer](sources/narrative-designer.md) — (expected: wiki/sources/narrative-designer.md — source missing) +- [2026-03-29] [level-designer](sources/level-designer.md) — (expected: wiki/sources/level-designer.md — source missing) +- [2026-03-29] [godot-shader-developer](sources/godot-shader-developer.md) — (expected: wiki/sources/godot-shader-developer.md — source missing) +- [2026-03-29] [godot-multiplayer-engineer](sources/godot-multiplayer-engineer.md) — (expected: wiki/sources/godot-multiplayer-engineer.md — source missing) +- [2026-03-29] [godot-gameplay-scripter](sources/godot-gameplay-scripter.md) — (expected: wiki/sources/godot-gameplay-scripter.md — source missing) +- [2026-03-29] [game-designer](sources/game-designer.md) — (expected: wiki/sources/game-designer.md — source missing) +- [2026-03-29] [game-audio-engineer](sources/game-audio-engineer.md) — (expected: wiki/sources/game-audio-engineer.md — source missing) +- [2026-03-29] [blender-addon-engineer](sources/blender-addon-engineer.md) — (expected: wiki/sources/blender-addon-engineer.md — source missing) +- [2026-03-29] [workflow-with-memory](sources/workflow-with-memory.md) — (expected: wiki/sources/workflow-with-memory.md — source missing) +- [2026-03-29] [workflow-startup-mvp](sources/workflow-startup-mvp.md) — (expected: wiki/sources/workflow-startup-mvp.md — source missing) +- [2026-03-29] [workflow-landing-page](sources/workflow-landing-page.md) — (expected: wiki/sources/workflow-landing-page.md — source missing) +- [2026-03-29] [workflow-book-chapter](sources/workflow-book-chapter.md) — (expected: wiki/sources/workflow-book-chapter.md — source missing) +- [2026-03-29] [nexus-spatial-discovery](sources/nexus-spatial-discovery.md) — (expected: wiki/sources/nexus-spatial-discovery.md — source missing) +- [2026-03-29] [readme](sources/readme.md) — (expected: wiki/sources/readme.md — source missing) +- [2026-03-29] [engineering-wechat-mini-program-developer](sources/engineering-wechat-mini-program-developer.md) — (expected: wiki/sources/engineering-wechat-mini-program-developer.md — source missing) +- [2026-03-29] [engineering-threat-detection-engineer](sources/engineering-threat-detection-engineer.md) — (expected: wiki/sources/engineering-threat-detection-engineer.md — source missing) +- [2026-03-29] [engineering-technical-writer](sources/engineering-technical-writer.md) — (expected: wiki/sources/engineering-technical-writer.md — source missing) +- [2026-03-29] [engineering-sre](sources/engineering-sre.md) — (expected: wiki/sources/engineering-sre.md — source missing) +- [2026-03-29] [engineering-solidity-smart-contract-engineer](sources/engineering-solidity-smart-contract-engineer.md) — (expected: wiki/sources/engineering-solidity-smart-contract-engineer.md — source missing) +- [2026-03-29] [engineering-software-architect](sources/engineering-software-architect.md) — (expected: wiki/sources/engineering-software-architect.md — source missing) +- [2026-03-29] [engineering-senior-developer](sources/engineering-senior-developer.md) — (expected: wiki/sources/engineering-senior-developer.md — source missing) +- [2026-03-29] [engineering-security-engineer](sources/engineering-security-engineer.md) — (expected: wiki/sources/engineering-security-engineer.md — source missing) +- [2026-03-29] [engineering-rapid-prototyper](sources/engineering-rapid-prototyper.md) — (expected: wiki/sources/engineering-rapid-prototyper.md — source missing) +- [2026-03-29] [engineering-mobile-app-builder](sources/engineering-mobile-app-builder.md) — (expected: wiki/sources/engineering-mobile-app-builder.md — source missing) +- [2026-03-29] [engineering-incident-response-commander](sources/engineering-incident-response-commander.md) — (expected: wiki/sources/engineering-incident-response-commander.md — source missing) +- [2026-03-29] [engineering-git-workflow-master](sources/engineering-git-workflow-master.md) — (expected: wiki/sources/engineering-git-workflow-master.md — source missing) +- [2026-03-29] [engineering-frontend-developer](sources/engineering-frontend-developer.md) — (expected: wiki/sources/engineering-frontend-developer.md — source missing) +- [2026-03-29] [engineering-filament-optimization-specialist](sources/engineering-filament-optimization-specialist.md) — (expected: wiki/sources/engineering-filament-optimization-specialist.md — source missing) +- [2026-03-29] [engineering-feishu-integration-developer](sources/engineering-feishu-integration-developer.md) — (expected: wiki/sources/engineering-feishu-integration-developer.md — source missing) +- [2026-03-29] [engineering-embedded-firmware-engineer](sources/engineering-embedded-firmware-engineer.md) — (expected: wiki/sources/engineering-embedded-firmware-engineer.md — source missing) +- [2026-03-29] [engineering-email-intelligence-engineer](sources/engineering-email-intelligence-engineer.md) — (expected: wiki/sources/engineering-email-intelligence-engineer.md — source missing) +- [2026-03-29] [engineering-devops-automator](sources/engineering-devops-automator.md) — (expected: wiki/sources/engineering-devops-automator.md — source missing) +- [2026-03-29] [engineering-database-optimizer](sources/engineering-database-optimizer.md) — (expected: wiki/sources/engineering-database-optimizer.md — source missing) +- [2026-03-29] [engineering-data-engineer](sources/engineering-data-engineer.md) — (expected: wiki/sources/engineering-data-engineer.md — source missing) +- [2026-03-29] [engineering-code-reviewer](sources/engineering-code-reviewer.md) — (expected: wiki/sources/engineering-code-reviewer.md — source missing) +- [2026-03-29] [engineering-cms-developer](sources/engineering-cms-developer.md) — (expected: wiki/sources/engineering-cms-developer.md — source missing) +- [2026-03-29] [engineering-backend-architect](sources/engineering-backend-architect.md) — (expected: wiki/sources/engineering-backend-architect.md — source missing) +- [2026-03-29] [engineering-autonomous-optimization-architect](sources/engineering-autonomous-optimization-architect.md) — (expected: wiki/sources/engineering-autonomous-optimization-architect.md — source missing) +- [2026-03-29] [engineering-ai-engineer](sources/engineering-ai-engineer.md) — (expected: wiki/sources/engineering-ai-engineer.md — source missing) +- [2026-03-29] [engineering-ai-data-remediation-engineer](sources/engineering-ai-data-remediation-engineer.md) — (expected: wiki/sources/engineering-ai-data-remediation-engineer.md — source missing) +- [2026-03-29] [design-whimsy-injector](sources/design-whimsy-injector.md) — (expected: wiki/sources/design-whimsy-injector.md — source missing) +- [2026-03-29] [design-visual-storyteller](sources/design-visual-storyteller.md) — (expected: wiki/sources/design-visual-storyteller.md — source missing) +- [2026-03-29] [design-ux-researcher](sources/design-ux-researcher.md) — (expected: wiki/sources/design-ux-researcher.md — source missing) +- [2026-03-29] [design-ux-architect](sources/design-ux-architect.md) — (expected: wiki/sources/design-ux-architect.md — source missing) +- [2026-03-29] [design-ui-designer](sources/design-ui-designer.md) — (expected: wiki/sources/design-ui-designer.md — source missing) +- [2026-03-29] [design-inclusive-visuals-specialist](sources/design-inclusive-visuals-specialist.md) — (expected: wiki/sources/design-inclusive-visuals-specialist.md — source missing) +- [2026-03-29] [design-image-prompt-engineer](sources/design-image-prompt-engineer.md) — (expected: wiki/sources/design-image-prompt-engineer.md — source missing) +- [2026-03-29] [design-brand-guardian](sources/design-brand-guardian.md) — (expected: wiki/sources/design-brand-guardian.md — source missing) +- [2026-03-29] [academic-psychologist](sources/academic-psychologist.md) — (expected: wiki/sources/academic-psychologist.md — source missing) +- [2026-03-29] [academic-narratologist](sources/academic-narratologist.md) — (expected: wiki/sources/academic-narratologist.md — source missing) +- [2026-03-29] [academic-historian](sources/academic-historian.md) — (expected: wiki/sources/academic-historian.md — source missing) +- [2026-03-29] [academic-geographer](sources/academic-geographer.md) — (expected: wiki/sources/academic-geographer.md — source missing) +- [2026-03-29] [academic-anthropologist](sources/academic-anthropologist.md) — (expected: wiki/sources/academic-anthropologist.md — source missing) +- [2026-03-29] [contributing_zh-cn](sources/contributing_zh-cn.md) — (expected: wiki/sources/contributing_zh-cn.md — source missing) +- [2026-03-29] [specialized-salesforce-architect](sources/specialized-salesforce-architect.md) — (expected: wiki/sources/specialized-salesforce-architect.md — source missing) + +## Entities +- [AWS](entities/AWS.md) +- [Azure](entities/Azure.md) +- [cloud-computing](entities/cloud-computing.md) +- [Cloud-Maturity-Model](entities/Cloud-Maturity-Model.md) +- [Cloud-Provider](entities/Cloud-Provider.md) +- [DevOps-Maturity-Model](entities/DevOps-Maturity-Model.md) +- [DORA-Metrics](entities/DORA-Metrics.md) +- [Google-Cloud](entities/Google-Cloud.md) +- [HemantSawant](entities/HemantSawant.md) +- [Open-Alliance-for-Cloud-Adoption](entities/Open-Alliance-for-Cloud-Adoption.md) + +## Concepts +- [AgilePractices](concepts/AgilePractices.md) +- [AIOps](concepts/AIOps.md) +- [Availability](concepts/Availability.md) +- [Change-Failure-Rate](concepts/Change-Failure-Rate.md) +- [CI-CD-Pipeline](concepts/CI-CD-Pipeline.md) +- [CICDPipeline](concepts/CICDPipeline.md) +- [Cloud-Adoption-Strategy](concepts/Cloud-Adoption-Strategy.md) +- [Cloud-DevOps-Maturity-Model](concepts/Cloud-DevOps-Maturity-Model.md) +- [Cloud-Maturity-Levels](concepts/Cloud-Maturity-Levels.md) +- [cloud-migration](concepts/cloud-migration.md) +- [Cloud-Native](concepts/Cloud-Native.md) +- [cloud-security](concepts/cloud-security.md) +- [Cloud-Service-Delivery](concepts/Cloud-Service-Delivery.md) +- [Continuous-Deployment](concepts/Continuous-Deployment.md) +- [Continuous-Integration](concepts/Continuous-Integration.md) +- [Cost-Optimization](concepts/Cost-Optimization.md) +- [Data-Sovereignty](concepts/Data-Sovereignty.md) +- [DevOps-Maturity](concepts/DevOps-Maturity.md) +- [DevOpsCulture](concepts/DevOpsCulture.md) +- [DevSecOps](concepts/DevSecOps.md) +- [DORA-Metrics](concepts/DORA-Metrics.md) +- [Error-Budget](concepts/Error-Budget.md) +- [GitOps](concepts/GitOps.md) +- [high-availability](concepts/high-availability.md) +- [Infrastructure-as-Code](concepts/Infrastructure-as-Code.md) +- [Lead-Time](concepts/Lead-Time.md) +- [MTTA](concepts/MTTA.md) +- [MTTD](concepts/MTTD.md) +- [MTTR](concepts/MTTR.md) +- [Multi-Cloud-Strategy](concepts/Multi-Cloud-Strategy.md) +- [Risk-Mitigation](concepts/Risk-Mitigation.md) +- [ROI](concepts/ROI.md) +- [Rollback-Rate](concepts/Rollback-Rate.md) +- [Scalability](concepts/Scalability.md) +- [Time-to-Market](concepts/Time-to-Market.md) +- [Vendor-Lock-In](concepts/Vendor-Lock-In.md) + +## Syntheses diff --git a/wiki/log.md b/wiki/log.md new file mode 100644 index 00000000..beb60d79 --- /dev/null +++ b/wiki/log.md @@ -0,0 +1,582 @@ +## [2026-04-24] ingest | DevOps Maturity Model From Traditional IT to Advanced DevOps +- Source file: raw/Cloud & DevOps/DevOps Maturity Model From Traditional IT to Advanced DevOps.md +- Status: ✅ 成功摄入 +- Summary: DevOps Maturity Model 五阶段详述（Phase 1-5），涵盖组织、交付、自动化、测试、安全、监控、运营7个维度的演进特征；补充 DevSecOps 集成路径（从发布前扫描到防止不合规代码入生产）；扩展 DORA 指标为15个运维指标（MTTD/MTTA/Time-to-Market/Rollback Rate/Error Budget/Availability/Scalability 等）；识别8大 DevOps 成熟度障碍 +- Concepts created: Continuous-Integration, Continuous-Deployment, Lead-Time, Time-to-Market, MTTR, MTTD, MTTA, Change-Failure-Rate, Error-Budget, Rollback-Rate, Availability, Scalability +- Entities updated: DevOps-Maturity-Model（更新 — 补充 Phase 1-5 详细阶段特征） +- Concepts updated: DevOps-Maturity（补充五阶段表格和15个指标链接）、DORA-Metrics（补充8个扩展运维指标）、DevSecOps（补充安全成熟度演进路径）、CI-CD-Pipeline（补充流水线成熟度演进）、Infrastructure-as-Code（补充 IaC 成熟度演进） +- Source page: wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md +- Notes: Source page 包含完整的 Phase 1-5 详细特征表格；新创建12个 Concept 页面（覆盖 CI/CD、指标、运维等领域）；补充 DevOps 成熟度演进全景图（5阶段 × 7维度）；与已有 DORA-Metrics、DevSecOps、CI-CD-Pipeline 等概念形成交叉链接；扩展 DORA 四指标为15个运维指标体系 +- SLUG: devops-maturity-model-from-traditional-it-to-advanced-devops + +## [2026-04-24] ingest | How Can a Multi Cloud Strategy Transform Your Business ROI +- Source file: raw/Cloud & DevOps/How Can a Multi Cloud Strategy Transform Your Business ROI.md +- Status: ✅ 成功摄入 +- Summary: 多云策略 ROI 转型全面指南，涵盖8大采用理由（避免锁定/韧性/安全/扩展/成本优化/创新/合规/性能优化）、5大业务挑战（风险缓解/成本优化/数据主权/性能/复杂性管理）、ROI 最大化的4个路径（成本降低/资源优化/效率提升/弹性扩展）和电商/医疗/金融3个行业用例 +- Concepts created/updated: Multi-Cloud-Strategy（更新 — 补充 ROI 最大化框架和实施路线图）, Vendor-Lock-In, Data-Sovereignty +- Entities created: AWS, Azure, Google-Cloud +- Source page: wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md +- Notes: 扩展已有 Multi-Cloud-Strategy concept，新增量化数据（30%成本降低、78%采用率）；创建3个云服务商 entity 页面；创建 Vendor-Lock-In 和 Data-Sovereignty 两个新 concept；与 Cloud-Maturity-Model 和 FinOps 形成知识链接 +- SLUG: how-can-a-multi-cloud-strategy-transform-your-business-roi + +## [2026-04-23] ingest | The Myths and Misconceptions About Cloud Computing +- Source file: raw/Cloud & DevOps/The Myths and Misconceptions About Cloud Computing LinkedIn.md +- Status: ✅ 成功摄入 +- Summary: 7个最常见的云计算误解与真相：Myth 1-7分别涉及安全性（云比本地更安全）、本质（远不止"别人的电脑"）、成本（合理管理可节省）、数据控制（混合多云保留控制）、适用性（中小企业同样适用）、迁移复杂度（规划得当可平滑）、性能可靠性（SLA可达99.99%） +- Concepts created: Cloud Security, Cloud Migration, High Availability +- Entities created: Cloud Computing +- Source page: wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md +- Notes: Entity 页面"Cloud Computing"整合了7个Myth对应的关键概念；Concept页面3个（Cloud-Security、Cloud-Migration、High-Availability）均从Myth出发反向建模；与已有DevOps/Cloud DevOps知识体系形成互补（安全、迁移、高可用是云成熟度模型的重要组成） +- SLUG: the-myths-and-misconceptions-about-cloud-computing-linkedin + +## [2026-04-22] ingest | What I Know About Cloud Service Delivery 1 +- Source file: raw/Cloud & DevOps/What I know about Cloud Service Delivery 1.md +- Status: ✅ 成功摄入 +- Summary: Cloud Service Delivery 全面指南，定义云服务交付是 IaaS/PaaS/SaaS 与最终用户实际消费的服务之间的桥梁。涵盖云服务交付团队5种角色（基础设施工程师/运营工程师/DevOps SRE/安全专家/FinOps）和12个运营域（服务供给→灾难恢复）。引入 Cloud DevOps Maturity Model 和 AIOps 概念。关键最佳实践：Grafana+CloudWatch 监控、WAF 管理、SLA 99.9% vs 99.99% 对比、Planned vs Emergency Change 分类。 +- Concepts created: Cloud-Service-Delivery, Cloud-DevOps-Maturity-Model, AIOps, Incident-Management, Change-Management, Disaster-Recovery, WAF, APM +- Source page: wiki/sources/what-i-know-about-cloud-service-delivery-1.md +- Notes: Source page 包含完整12个运营域详解；新创建3个 Concept 页面（Cloud-Service-Delivery、Cloud-DevOps-Maturity-Model、AIOps）；更新 overview.md 补充新概念索引（Cloud Service Delivery、Cloud DevOps Maturity Model、AIOps、SLA、SLO、Incident Management、Change Management、Disaster Recovery、WAF、APM）；与已有 DevOps Maturity、DORA Metrics、FinOps 等概念形成知识链接 +- SLUG: what-i-know-about-cloud-service-delivery-1 + +## [2026-04-22] ingest | Cloud Maturity Model - A Detailed Guide For Cloud Adoption +- Source file: raw/Cloud & DevOps/Cloud Maturity Model A Detailed Guide For Cloud Adoption.md +- Status: ✅ 成功摄入 +- Summary: Cloud Maturity Model (CMM) 综合指南，涵盖 OACA 定义的 CMM 框架、6个业务能力域和18个技术能力域、3大评估维度（People/Processes/Technology）、5个成熟度等级（Level 0-5）及其特征、7大收益、最佳实践（设定目标/识别等级/选模型/治理合规/安全风险管理）以及多种云成熟度模型对比（AWS CAF/Azure CAF/CSMM/SAMM等）。CMM 行业规模预计从2022年7.5亿美元增至2025年15亿美元，60%以上组织正在实施。 +- Concepts created: Cloud-Adoption-Strategy, Cloud-Maturity-Levels, Multi-Cloud-Strategy +- Entities created: Cloud-Maturity-Model, Open-Alliance-for-Cloud-Adoption +- Source page: wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md +- Notes: Source page 包含完整5个成熟度等级详解（含每级挑战表格）；新创建3个 Concept 页面（Cloud-Adoption-Strategy、Cloud-Maturity-Levels、Multi-Cloud-Strategy）；新创建2个 Entity 页面（Cloud-Maturity-Model、Open-Alliance-for-Cloud-Adoption）；更新 overview.md 补充新概念索引；与已有 DevOps-Maturity 和 Cloud-Native 形成知识链接 + +## [2026-04-22] ingest | Contributing to The Agency +- Source file: raw/Agent/agency-agents/CONTRIBUTING.md +- Status: ✅ 成功摄入 +- Summary: The Agency 贡献指南，定义完整贡献体系：Code of Conduct（尊重/包容/协作/专业）、4种贡献方式（创建Agent/改进现有/分享案例/报告问题）、Agent 设计规范（Persona vs Operations 分组、Design Principles、External Services、Qwen兼容性）、PR 边界管理（单文件 vs Discussion）和 Style Guide（具体性/ concreteness/ personality/ practical）。首次系统定义 Agent 文件的两大语义分组：Persona（身份/沟通/规则）与 Operations（使命/交付物/工作流/指标）。 +- Concepts created: Persona vs Operations, Agent Design Principles, Pull Request Process, Style Guide, Code of Conduct, Qwen Code Compatibility +- Entities created: The Agency（更新 — 补充 CONTRIBUTING 规范层） +- Source page: wiki/sources/contributing-to-the-agency.md +- Notes: 贡献指南为 The Agency 项目提供元层规范，与 README 的总览层、Examples 的工作流层共同构成三层文档体系；Persona vs Operations 分组是该文档的核心贡献，首次将 Agent 文件结构化为两个语义维度；Qwen Code Compatibility 说明 convert.sh 脚本自动拆分的分组机制；PR 边界管理强调单文件提交的最小化风险原则 + +## [2026-04-21] ingest | Cloud DevOp Maturity - Guideline +- Source file: raw/Cloud & DevOps/Cloud DevOp Maturity - Guideline.md +- Status: ✅ 成功摄入 +- Summary: 企业级 SaaS 组织云 DevOps 成熟度评估综合指南，涵盖 8 大领域：DevOps 成熟度定义、成熟度模型（CMMI、DORA）、基础支柱（自动化、协作文化、监控可观测性、安全集成 DevSecOps）、工具链技术选型、指标测量、挑战分析、案例研究和成熟度路线图。 +- Concepts created: DevOps Maturity, DORA Metrics, DevSecOps, CI/CD Pipeline, Infrastructure as Code, Cloud-Native +- Entities created: DevOps Maturity Model, DORA Metrics +- Source page: wiki/sources/cloud-devop-maturity-guideline.md +- Notes: Source page 包含完整 8 大领域摘要；新创建 6 个 Concept 页面（DevOps-Maturity、DORA-Metrics、DevSecOps、CI-CD-Pipeline、Infrastructure-as-Code、Cloud-Native）；更新 overview.md 补充新概念索引；DORA Metrics 作为 DevOps 核心评估框架首次独立建档 + +## [2026-04-21] ingest | The Agency: AI Specialists Ready to Transform Your Workflow +- Source file: raw/Agent/agency-agents/README.md +- Status: ✅ 成功摄入 +- Summary: The Agency 是一个在 Reddit 社区发起的开源 AI Agent 精选集合，收录 147 个专业化 AI Agent，横跨 12 个业务分部（Engineering、Design、Paid Media、Sales、Marketing、Product、Project Management、Testing、Support、Spatial Computing、Specialized、Finance），含游戏开发（Unity/Unreal/Godot/Blender/Roblox）和学术研究分部。支持 11 种 AI 工具的多工具集成。 +- Concepts created: Multi-Agent Coordination, Agent Personality, Agent Specialization, Multi-Tool Integration +- Entities created: The Agency (open-source AI agent collection) +- Source page: wiki/sources/agency-agents-readme.md +- Notes: 项目 README 总览页；overview.md 中已大量覆盖各 Agent 条目；source page 记录完整分部架构和 11 种工具集成方式；该文档已被多次摄入（README、examples/integrations 等子文件独立摄入） + +## [2026-04-21] ingest | codecrafters-io/build-your-own-x +- Source file: raw/AI/codecrafters-iobuild-your-own-x Master programming by recreating your favorite technologies from scratch.md +- Status: ✅ 成功摄入 +- Summary: Build Your Own X 是一个 GitHub 精选教程集，通过从零重建你最喜爱的技术来掌握编程。涵盖 25+ 技术领域（OS、Git、Docker、Database、编程语言/编译器、神经网络、Web 浏览器、游戏、AR、BitTorrent、区块链、Bot、CLI工具、模拟器、前端框架、物理引擎、搜索引擎、Shell、模板引擎、文本编辑器、视觉识别、体素引擎），每个领域收录多种语言（Python、C、C++、Go、JavaScript、Rust等）的优质分步教程。核心理念：Richard Feynman 的名言"What I cannot create, I do not understand"。 +- Concepts created: [[Byox]]（已存在，更新为独立 Concept 页面，补充 26 领域和 500+ 精选教程索引） +- Entities created: [[codecrafters-io/build-your-own-x]]（GitHub 知识库实体页面） +- Source page: wiki/sources/codecrafters-iobuild-your-own-x-master-programming-by-recreating-your-favorite-technologies-from-scratch.md +- Notes: Source 页面包含完整 26 技术领域分类索引；Byox Concept 补充精选资源（Crafting Interpreters、Writing an OS in Rust、Browser Engineering、Write yourself a Git 等）；Entity 页面包含技术领域对照表；覆盖 Database/OS/编程语言/Web浏览器/Git/Docker/神经网络等 + +## [2026-04-21] ingest | 如何传输 Docker images 并且在另一个 Docker 安装 +- Source file: raw/Home Office/如何传输Docker images 并且在另一个Docker安装.md +- Status: ✅ 成功摄入 +- Summary: Docker 镜像在不同主机之间的离线传输方法，使用 docker save 和 docker load 命令实现无需 registry 的镜像迁移。典型场景：将工作笔记本上的 Docker 镜像传输到 Synology NAS 的 Docker 环境。核心命令：docker save -o images.tar image_name:tag 和 docker load < images.tar。同时介绍了 docker commit 和 docker export/import 两种替代方法。 +- Concepts created: Docker-Image, Docker-Save, Docker-Load +- Entities updated: Docker（添加 source 引用） +- Source page: wiki/sources/如何传输Docker-images-并且在另一个Docker安装.md +- Notes: Home Office 分类文档；Docker 相关 Concept 页面已创建；与已有 Xiaoya entity 形成知识链接；Docker 镜像离线传输是 NAS 环境中常见需求 +- Entities created: Synology NAS +- Source page: wiki/sources/如何传输Docker-images-并且在另一个Docker安装.md +- Notes: 属于 Home Office 场景的实用运维技能；与现有的 Docker-Daemon-代理 等概念互补 + +## [2026-04-21] ingest | Project State Management System +- Source file: raw/Agent/usecases/project-state-management.md +- Status: ✅ 成功摄入 +- Summary: 事件驱动的项目状态管理系统，通过数据库存储项目状态和历史事件，AI Agent 自然语言交互替代静态 Kanban 看板。核心理念：事件即事实，存储所有状态变更而非最终状态；上下文保留，记录决策、阻碍、关键洞察。关键技术：PostgreSQL/SQLite 项目状态数据库、GitHub CLI 提交追踪、每日 Cron 摘要、Cron Jobs 定时触发。 +- Concepts created: Event Sourcing, 每日站会摘要, Git 集成 +- Entities created: Project State Management +- Source page: wiki/sources/project-state-management.md +- Notes: 与 Kanban 看板存在方法论冲突：事件驱动强调自动追踪和上下文保留，Kanban 强调可视化团队协作；Event Sourcing 作为理论基础首次创建为独立 concept；每日站会摘要通过 Cron 自动生成；Git 集成实现代码变更与项目进度的可追溯性 + +## [2026-04-21] ingest | Marketing Carousel Growth Engine +- Source file: raw/Agent/agency-agents/marketing/marketing-carousel-growth-engine.md +- Status: ✅ 成功摄入 +- Summary: TikTok/Instagram 轮播内容自动生成与发布系统，通过 Playwright 网站分析、Gemini 图片生成、Upload-Post API 发布实现每日自主内容生产。核心理念：6-slide 叙事结构确保转化，数据驱动反馈循环持续优化。关键指标：每日 1 个轮播、20%+ 月均观看增长、5%+ 参与率、90%+ 视觉验证通过率。 +- Concepts created: Carousel Narrative Arc, Analytics Feedback Loop, Visual Coherence Engine, Autonomous QA +- Entities created: Gemini API, Upload-Post API, Playwright +- Source page: wiki/sources/marketing-carousel-growth-engine.md +- Notes: The Agency 营销团队成员；与其他营销 Agent 形成矩阵覆盖（内容创作→平台发布→数据分析→迭代优化）；自主质量保证系统实现零人工干预 + +## [2026-04-21] ingest | Marketing Private Domain Operator +- Source file: raw/Agent/agency-agents/marketing/marketing-private-domain-operator.md +- Status: ✅ 成功摄入 +- Summary: 企业微信（WeCom）私域运营与用户生命周期管理专家智能体，专注 SCRM 系统配置、社群分层运营、用户生命周期自动化和全漏斗转化优化。核心理念：私域本质是建立信任资产，用户留存是因为持续获得超出预期的价值。关键指标：月度好友净增长>15%、社群7天活跃率>35%、新客7天首购转化率>20%、私域用户LTV是公域3倍以上。 +- Concepts created: SCRM, 用户生命周期管理, 私域运营（更新）, 社群分层运营, 用户LTV, SOP自动化 +- Entities created: WeCom（更新） +- Source page: wiki/sources/marketing-private-domain-operator.md +- Notes: The Agency 营销团队成员；与 Marketing Kuaishou Strategist 的私域运营形成互补（WeCom vs 快手）；核心差异：VIP社群转化率12.3% vs 福利群3.1%，证明高价值用户聚焦运营优于泛运营 + +## [2026-04-21] ingest | Marketing Short-Video Editing Coach +- Source file: raw/Agent/agency-agents/marketing/marketing-short-video-editing-coach.md +- Status: ✅ 成功摄入 +- Summary: 短视频剪辑技术教练智能体，覆盖 CapCut Pro、Premiere Pro、DaVinci Resolve、Final Cut Pro 全流程后期制作。核心能力：剪辑思维、构图语言、调色分级、音频工程、运动图形、字幕设计、多平台适配、AI辅助剪辑。核心信条：软件是工具，叙事是灵魂；每帧必有其用。关键指标：完播率 > 品类平均 1.5 倍，剪辑效率模板化后 3 分钟视频 < 45 分钟。 +- Concepts created: 短视频剪辑, 调色分级, 音频工程, 运动图形, 字幕设计, AI辅助剪辑, 卡点, 速度曲线, LUT +- Entities created: CapCut Pro, Adobe Premiere Pro, DaVinci Resolve, Final Cut Pro +- Source page: wiki/sources/marketing-short-video-editing-coach.md +- Notes: The Agency 营销团队成员；剪辑软件决策树：日均短视频效率优先→CapCut Pro、商业项目AE集成→Premiere Pro、严苛调色预算有限→DaVinci Resolve、Mac用户→Final Cut Pro + +## [2026-04-21] ingest | Marketing Social Media Strategist +- Source file: raw/Agent/agency-agents/marketing/marketing-social-media-strategist.md +- Status: ✅ 成功摄入 +- Summary: 跨平台社交媒体策略智能体，专精 LinkedIn、Twitter 及专业社交平台。核心能力：跨平台策略、LinkedIn 运营、Twitter 集成、专业网络社区建设。活动管理、思想领导力开发、分析与归因、内容适配。关键指标：3%+ LinkedIn 参与率、20% 月度覆盖增长、50%+ 内容达标率、30%+ 员工倡导参与率、3x+ 广告回报。 +- Concepts created: Cross-Platform Strategy, Thought Leadership, B2B Social Selling, Employee Advocacy, Social Media Analytics, Content Cascade +- Entities created: Twitter Engager（更新） +- Source page: wiki/sources/marketing-social-media-strategist.md +- Notes: The Agency 营销团队成员；与 Twitter Engager 协作（消息协调、内容适配）；Handoff from Content Creator/Trend Researcher/Brand Guardian；Delivers to Analytics Reporter/Growth Hacker/Sales teams + +## [2026-04-21] ingest | Marketing Kuaishou Strategist +- Source file: raw/Agent/agency-agents/marketing/marketing-kuaishou-strategist.md +- Status: ✅ 成功摄入 +- Summary: 快手营销策略专家智能体，专注下沉市场短视频内容、直播带货运营和社区信任建设。核心差异于抖音：真实 > 精致、均衡分发算法、下沉市场 30-50 岁用户、老铁经济信任体系。关键指标：3%+ 直播转化率、38分钟+ 平均观看时长、15%+ 粉丝团月增长。 +- Concepts created: 老铁经济, 下沉市场, 均衡分发, 私域运营, 粉丝团 +- Entities created: Kuaishou, 老铁, Douyin（更新） +- Source page: wiki/sources/marketing-kuaishou-strategist.md +- Notes: The Agency 营销团队成员；与 Marketing Douyin Strategist 存在平台策略冲突（真实 vs 精致、均衡分发 vs 中心化推荐、下沉市场 vs 一二线城市） + +## [2026-04-21] ingest | Marketing Weibo Strategist +- Source file: raw/Agent/agency-agents/marketing/marketing-weibo-strategist.md +- Status: ✅ 成功摄入 +- Summary: 微博全频谱运营与品牌传播策略专家智能体，专注账号定位、趋势话题运营、Super Topic社区管理、粉丝经济、KOL合作和广告投放。核心信条：微博是公共话语场，核心价值是话语权而非私域流量。病毒传播公式：争议性×低参与门槛×情感共鸣=病毒扩散。 +- Concepts created: Trending Topic Operations, Super Topic Community Management, Sentiment Early Warning System, KOL Partnership Pyramid, Fan Economy Operations, Weibo Blue-V, Fan Tunnel +- Entities created: Sina Weibo +- Source page: wiki/sources/marketing-weibo-strategist.md +- Notes: The Agency 营销团队成员；与其他营销 Agent 形成矩阵覆盖（内容创作→平台运营→社区管理→危机应对） + +## [2026-04-21] ingest | Marketing Video Optimization Specialist +- Source file: raw/Agent/agency-agents/marketing/marketing-video-optimization-specialist.md +- Status: ✅ 成功摄入 +- Summary: YouTube 视频营销算法优化与观众留存率提升专家智能体，专注于 CTR 优化、观众留存分析、SEO 元数据优化、缩略图设计和跨平台内容分发（Shorts、Reels、TikTok）。核心交付物：视频优化审计模板（标题/缩略图/章节/SEO元数据）。关键指标：8%+ CTR、50%+ 3分钟留存率、20% AVD 提升、1%+ 订阅转化率。 +- Concepts created: The Hook, CTR (Click-Through Rate), Audience Retention, Video SEO, Thumbnail Optimization, Chaptering, Cross-Platform Syndication, Initial Velocity, Session Time Maximization +- Entities created: YouTube（更新）, YouTube Studio, YouTube Algorithm, Shorts, Reels, TikTok +- Source page: wiki/sources/marketing-video-optimization-specialist.md +- Notes: The Agency 营销团队成员；与 Marketing Douyin Strategist 存在算法策略差异（YouTube 重留存/观看时长 vs 抖音重完播率/互动率）；视频优化审计模板为标准化交付物 + +## [2026-04-21] ingest | Marketing Instagram Curator +- Source file: raw/Agent/agency-agents/marketing/marketing-instagram-curator.md +- Status: ✅ 成功摄入 +- Summary: Instagram 营销专家智能体，专注于视觉叙事、品牌美学开发和多格式内容优化。核心方法论：四阶段工作流程（品牌美学开发→多格式内容策略→社区建设与电商→性能优化）。目标：3.5%+ 互动率、80%+ Story 完成率、2.5%+ 购物转化率、200+ UGC 月度品牌帖子。 +- Concepts created: Visual Brand Development, Multi-Format Content Strategy, Community Building, Social Commerce, UGC (User-Generated Content), Instagram Shopping Mastery, Engagement Rate Optimization, Hashtag Strategy +- Entities created: Instagram（更新） +- Source page: wiki/sources/marketing-instagram-curator.md +- Notes: The Agency 营销团队成员；与 Marketing Reddit Community Builder 同属社交媒体营销但平台策略不同（Instagram 视觉美学 vs Reddit 价值驱动社区）；与 Brand Guardian 关联（品牌美学开发依赖品牌身份定义） + +## [2026-04-21] ingest | Marketing China E-Commerce Operator +- Source file: raw/Agent/agency-agents/marketing/marketing-china-ecommerce-operator.md +- Status: ✅ 成功摄入 +- Summary: 中国电商多平台运营与营销策略专家智能体，覆盖淘宝、天猫、拼多多、京东、抖音店铺全渠道运营。核心方法论：多平台差异化运营、数据驱动决策、利润保护优先、大促提前45-60天准备。涵盖直播带货、平台广告投放、618/双11大促策划全链路。 +- Concepts created: 直通车, 万相台, 多多搜索, 京速推, 预售, 跨店满减, 私域运营, 直播电商（已有，更新） +- Entities created: 淘宝, 天猫, 拼多多, 京东, 抖音（更新） +- Source page: wiki/sources/marketing-china-ecommerce-operator.md +- Notes: The Agency 营销团队成员；与 Marketing Cross-Border E-Commerce Specialist、Marketing Douyin Strategist 同属营销智能体系列；直播电商 concept 已存在本次更新；6个新建概念覆盖中国电商核心广告工具和促销机制 + +## [2026-04-21] ingest | Marketing Cross-Border E-Commerce Specialist +- Source file: raw/Agent/agency-agents/marketing/marketing-cross-border-ecommerce.md +- Status: ✅ 成功摄入 +- Summary: 全漏斗跨境电商运营策略专家，覆盖 Amazon、Shopee、Lazada、AliExpress、Temu、TikTok Shop 等全球主流平台。核心方法论：平台选品→合规准备→listing优化→广告投放→数据迭代的五步工作流。强调本地化决定 traction、合规决定生存、供应链决定盈利。 +- Concepts created: ACOS (Advertising Cost of Sales), FBA (Fulfillment by Amazon), VAT (Value Added Tax), Listing Optimization, Cross-Border Logistics, Compliance & Certification +- Entities created: Amazon, TikTok Shop（更新 The Agency 成员列表） +- Source page: wiki/sources/Marketing-Cross-Border-Ecommerce-Specialist.md +- Notes: The Agency 营销团队成员；Amazon 和 TikTok Shop 为新建 entity；与 Marketing Douyin Strategist 同属营销领域但面向不同市场；合规认证概念（CE/FCC/FDA/WEEE）与 Legal Compliance Checker 关联 + +## [2026-04-21] ingest | Book Co-Author +- Source file: raw/Agent/agency-agents/marketing/marketing-book-co-author.md +- Status: ✅ 成功摄入 +- Summary: 战略代笔写作智能体，将语音笔记和碎片化思想转化为结构化的第一人称书籍章节。核心方法论：五步工作流（压力测试brief→定义章节意图→第一人称起草→战略修订→交付修订包）+ 版本化管理。强调作者声音保真、禁止陈词滥调、声明溯源、具体胜于抽象。 +- Concepts created: Thought Leadership Book, Ghostwriting, Narrative Architecture, Voice Fidelity, Chapter Blueprint, Versioned Draft +- Entities created: Book Co-Author +- Source page: wiki/sources/marketing-book-co-author.md +- Notes: The Agency 营销团队成员，与 Developer Advocate、Paid Media Ad Creative Strategist 共享工作流模式；Thought Leadership 已存在 concept；The Agency 已存在 entity + +## [2026-04-21] ingest | Marketing Zhihu Strategist +- Source file: raw/Agent/agency-agents/marketing/marketing-zhihu-strategist.md +- Status: ✅ 成功摄入 +- Summary: 知乎营销策略与思想领导力建设智能体，专注于通过真实专业知识分享建立品牌权威，获取精准潜在客户。核心方法论：信誉第一、6阶段工作流（主题定位→问题识别→内容创作→专栏开发→关系建设→绩效优化）。 +- Concepts created: Thought Leadership, Lead Generation Funnel +- Entities created: Zhihu +- Source page: wiki/sources/marketing-zhihu-strategist.md +- Notes: The Agency 营销团队成员，与 Marketing Douyin Strategist 同属营销策略智能体；Thought Leadership 和 Lead Generation Funnel 为新建 concept；Zhihu 为新建 entity + +## [2026-04-21] ingest | Marketing Douyin Strategist +- Source file: raw/Agent/agency-agents/marketing/marketing-douyin-strategist.md +- Status: ✅ 成功摄入 +- Summary: 抖音短视频营销与直播带货策略智能体，专注于推荐算法、病毒视频策划、直播电商运营和内容矩阵策略。核心方法论：算法优先思维（完播率>点赞率>评论率>分享率）、黄金3秒钩子、DOUT+精准投放。 +- Concepts created: 算法优先思维, 黄金3秒钩子, 直播电商, 内容矩阵 +- Entities created: DOU+（抖+）, 千川, Marketing Douyin Strategist +- Source page: wiki/sources/marketing-douyin-strategist.md +- Notes: The Agency 营销团队新成员，与 Healthcare Marketing Compliance Specialist 同属营销合规领域；抖音已存在 entity；内容矩阵 concept 已存在 + +## [2026-04-21] ingest | Multi-Agent Workflow: Startup MVP with Persistent Memory +- Source file: raw/Agent/agency-agents/examples/workflow-with-memory.md +- Status: ✅ 成功摄入 +- Summary: 基于 MCP Memory Server 的多智能体协作工作流，通过 remember/recall/rollback/search 操作实现 agent 间自动上下文存取，解决手动复制粘贴交接、会话超时、多日项目等场景的上下文断裂问题 +- Concepts created: Memory Tagging, Rollback Mechanism +- Entities created: RetroBoard +- Source page: wiki/sources/workflow-with-memory.md +- Notes: 与 workflow-startup-mvp.md 是同一项目（RetroBoard）的两个版本（无 Memory vs 有 Memory）；Sprint Prioritizer、UX Researcher、Backend Architect、Frontend Developer、Growth Hacker、Reality Checker 均已存在 + +## [2026-04-21] ingest | Multi-Agent Workflow: Landing Page Sprint +- Source file: raw/Agent/agency-agents/examples/workflow-landing-page.md +- Status: ✅ 成功摄入 +- Summary: 多智能体协作在一天内完成高转化率 landing page 开发的 sprint 工作流，通过 4 个专业 Agent（Content Creator、UI Designer、Frontend Developer、Growth Hacker）分阶段并行协作实现 +- Concepts created: Multi-Agent Workflow, Parallel Kickoff, Merge Point, Time-boxed +- Entities created: Content Creator, Frontend Developer, FlowSync +- Source page: wiki/sources/multi-agent-workflow-landing-page-sprint.md +- Notes: 与 workflow-startup-mvp 类似，但更聚焦于单日 sprint；Growth Hacker 已存在；UI Designer 已存在于 design-ui-designer.md + +## [2026-04-20] ingest | Academic Historian Agent +- Source file: raw/Agent/agency-agents/academic/academic-historian.md +- Status: ✅ 成功摄入 +- Summary: Academic Historian 是 The Agency 项目中的研究历史学家智能体，具备广泛时间跨度和深厚方法论训练，通过 Annales 学派、微历史、长时段分析等框架验证历史一致性、提供物质文化细节、挑战历史神话 +- Concepts created: Period Authenticity Report, Historical Coherence Check, Material Culture, Longue Durée, Microhistory, Anachronism, Annales School +- Entities created: Academic Historian +- Source page: wiki/sources/academic-historian.md +- Notes: 与 Academic Anthropologist、Academic Geographer 同属世界构建团队；强调时间地点精确性，避免泛化历史描述；挑战欧洲中心主义 + +## [2026-04-20] ingest | Security Policy +- Source file: raw/Agent/agency-agents/SECURITY.md +- Status: ✅ 成功摄入 +- Summary: Security Policy 定义 agency-agents 项目的安全漏洞报告流程（私下报告、响应时间线）和贡献者安全最佳实践（禁止提交密钥/凭证、提示词注入检测） +- Concepts created: 提示词注入, 安全响应时间线 +- Entities created: agency-agents +- Source page: wiki/sources/SECURITY.md +- Notes: Shell 脚本需合并前审查；智能体文件为非可执行提示词定义 + +## [2026-04-20] ingest | Academic Psychologist Agent +- Source file: raw/Agent/agency-agents/academic/academic-psychologist.md +- Status: ✅ 成功摄入 +- Summary: Academic Psychologist 是 The Agency 项目中的临床与研究心理学家人格定义智能体，基于 Big Five、依恋理论、Vaillant 防御机制层级、Karpman 戏剧三角、CBT 认知扭曲识别、社会心理学经典实验等框架提供多理论心理学分析范式 +- Concepts created: Big Five Personality Framework, 依恋理论, Vaillant 防御机制层级, 认知扭曲, 群体思维, 社会认同理论 +- Entities created: Karpman Drama Triangle +- Source page: wiki/sources/academic-psychologist.md +- Notes: 强调文化语境与研究局限性，避免过度诊断；与已有的人格心理学知识体系高度互补 + +## [2026-04-20] ingest | Product Sprint Prioritizer +- Source file: raw/Agent/agency-agents/product/product-sprint-prioritizer.md +- Status: ✅ 成功摄入 +- Summary: Product Sprint Prioritizer 是 The Agency 项目中的产品冲刺优先级智能体，专注于敏捷冲刺规划、功能优先排序和资源分配，通过 RICE、MoSCoW、Kano 等数据驱动框架最大化团队效率 +- Concepts created: RICE Framework, MoSCoW Method, Kano Model, Team Velocity, Sprint Planning, Capacity Planning, Risk Management +- Entities created: The Agency（更新） +- Source page: wiki/sources/product-sprint-prioritizer.md +- Notes: 核心成功指标：90%+ 故事点交付率、4.5/5 干系人满意度、±10% 时间线偏差；与 Product Feedback Synthesizer 有概念重叠（均涉及 RICE/MoSCoW/Kano） + +## [2026-04-20] ingest | Narratologist Agent +- Source file: raw/Agent/agency-agents/academic/academic-narratologist.md +- Status: ✅ 成功摄入 +- Summary: Narratologist 是 The Agency 项目中的叙事理论专家智能体，基于 Propp、Campbell、McKee、Genette、Barthes、Vogler、Todorov 等经典叙事理论框架提供故事结构分析、角色弧线评估和叙事连贯性诊断 +- Concepts created: Propp 叙事形态学, Campbell 英雄之旅, McKee 故事结构, Genette 叙事学, Vogler 作家旅程, Todorov 均衡模型, Barthes 五代码, Character Arc, Story Structure Analysis +- Entities created: The Agency（更新） +- Source page: wiki/sources/academic-narratologist.md +- Notes: 强调 Fabula vs Sjuzhet 区分；每个建议必须基于至少一个命名理论框架；角色弧线必须包含 want/need/lie/transformation 四个检查点 + +## [2026-04-21] ingest | Multi-Agent Workflow: Startup MVP +- Source file: raw/Agent/agency-agents/examples/workflow-startup-mvp.md +- Status: ✅ 成功摄入 +- Summary: 多智能体协作从创意到 MVP 交付的完整工作流程，通过 7 个专业角色（Sprint Prioritizer、UX Researcher、Backend Architect、Frontend Developer、Rapid Prototyper、Growth Hacker、Reality Checker）顺序与并行工作，4 周完成 MVP 开发 +- Concepts created: Sequential Handoffs, Parallel Work, Quality Gates, Context Passing +- Entities created: Sprint Prioritizer, Rapid Prototyper, Growth Hacker, Reality Checker +- Source page: wiki/sources/workflow-startup-mvp.md +- Notes: 关键模式：顺序交接、并行工作、质量门控、上下文传递；Reality Checker 在 Week 2 中点和 Week 4 Launch 前设置质量门控 + +## [2026-04-21] ingest | Testing Tool Evaluator +- Source file: raw/Agent/agency-agents/testing/testing-tool-evaluator.md +- Status: ✅ 成功摄入 +- Summary: Tool Evaluator Agent 是 The Agency 项目中的技术评估与战略工具采纳专家智能体，通过七维度加权评分体系（功能性、可用性、性能、安全性、集成、支持、成本）评估工具，核心成功指标：90% 推荐准确率、85% 采用率、20% 成本降低、25% ROI +- Concepts created: Tool Evaluation Framework, TCO (Total Cost of Ownership), ROI Analysis, Vendor Management +- Entities created: Tool Evaluator Agent +- Source page: wiki/sources/testing-tool-evaluator.md +- Notes: 与 Test Results Analyzer、Evidence Collector、Performance Benchmarker、Reality Checker 共同构成质量保障智能体体系；侧重点为工具选择与供应商评估 + +## [2026-04-20] ingest | Product Trend Researcher +- Source file: raw/Agent/agency-agents/product/product-trend-researcher.md +- Status: ✅ 成功摄入 +- Summary: Product Trend Researcher 是 The Agency 项目中的市场情报与趋势研究专家智能体，专注于新兴趋势识别、竞争分析和机会评估，通过七步趋势识别流程提供可操作的洞察驱动产品策略和创新决策 +- Concepts created: Trend Analysis, Competitive Intelligence, Technology Scouting, TAM/SAM/SOM, Consumer Behavior Analysis, Technology Adoption Curve, Weak Signal Detection, Predictive Modeling +- Entities created: The Agency（更新） +- Source page: wiki/sources/product-trend-researcher.md +- Notes: 6个月预测准确率目标80%+，领先主流采用3-6个月；Market Research概念已增强更新 + +## [2026-04-20] ingest | Product Manager Agent +- Source file: raw/Agent/agency-agents/product/product-manager.md +- Status: ✅ 成功摄入 +- Summary: Product Manager Agent 是 The Agency 项目中的产品经理智能体，定义完整产品生命周期管理框架，涵盖身份设定、核心使命、关键规则、6 阶段工作流程（Discovery → Framing → Definition → Delivery → Launch → Measurement） +- Concepts created: Product Requirements Document (PRD), Opportunity Assessment, Roadmap (Now / Next / Later), RICE评分 (已合并), Go-to-Market Brief, Sprint Health Snapshot, Outcome-Driven Development, Discovery Process +- Entities created: Product Manager Agent +- Source page: wiki/sources/product-manager.md +- Notes: PRD模板、Opportunity Assessment模板、Roadmap模板、GTM Brief模板、Sprint Health模板完整可用；RICE评分已与现有页面合并避免重复 + +## [2026-04-20] ingest | Product Feedback Synthesizer +- Source file: raw/Agent/agency-agents/product/product-feedback-synthesizer.md +- Status: ✅ 成功摄入 +- Summary: Product Feedback Synthesizer 是 The Agency 项目中的用户反馈合成专家智能体，专注于从多渠道收集、分析和合成用户反馈，将定性反馈转化为可量化的产品优先级和战略建议 +- Concepts created: RICE评分, MoSCoW优先级, Kano模型, NPS分析, Voice of Customer, 流失预测, CSAT, CES +- Entities created: Product Feedback Synthesizer, The Agency（更新） +- Source page: wiki/sources/product-feedback-synthesizer.md +- Notes: 核心价值：从 thousand user voices 提炼出 five things to build next，85%合成反馈导致可衡量决策 + +## [2026-04-20] ingest | Automation Governance Architect +- Source file: raw/Agent/agency-agents/specialized/automation-governance-architect.md +- Status: ✅ 成功摄入 +- Summary: Automation Governance Architect 是 The Agency 项目中的自动化治理架构专家智能体，Governance-first 方法评估自动化价值、风险与可维护性，以 n8n 为主要编排工具 +- Concepts created: n8n Workflow Standard, Decision Framework, Verdict Types, Reliability Baseline, Re-Audit Triggers +- Entities created: The Agency（更新） +- Source page: wiki/sources/automation-governance-architect.md +- Notes: 与 ITSM 密切相关，治理原则可应用于更广泛的自动化场景 + +## [2026-04-20] ingest | Data Consolidation Agent +- Source file: raw/Agent/agency-agents/specialized/data-consolidation-agent.md +- Status: ✅ 成功摄入 +- Summary: Data Consolidation Agent 是 The Agency 项目中的销售数据整合智能体，将 Sales Data Extraction Agent 提取的数据聚合为实时仪表盘和报表，提供领地表现汇总、代表排名、管道快照、趋势分析和 Top 5 销售明星 +- Concepts created: Dashboard Report, Territory Report, Attainment Calculation, Trend Analysis +- Entities created: The Agency（更新） +- Source page: wiki/sources/data-consolidation-agent.md +- Notes: 与 Sales Data Extraction Agent 形成上下游关系，前者负责提取，后者负责整合可视化 + +## [2026-04-20] ingest | French Consulting Market Navigator +- Source file: raw/Agent/agency-agents/specialized/specialized-french-consulting-market.md +- Status: ✅ 成功摄入 +- Summary: French Consulting Market Navigator 是法国 ESN/SI 生态系统自由职业导航工具，解析 ESN margin 模型（25-40%）、portage salarial vs micro-entreprise vs SASU 税费结构对比、平台费率矩阵（Malt 10%、collective.work 3-5%）、费率谈判策略和季节性市场动态 +- Concepts created: TJM Brut, ESN Margin, Seasonal Calendar +- Entities created: Malt, collective.work, Portage Salarial, Micro-Entrepreneur, ESN Tier Classification, The Agency（更新） +- Source page: wiki/sources/French-Consulting-Market-Navigator.md +- Notes: 发现与常见观点冲突：微型企业净收入高于 portage salarial，但缺失社保福利（失业保险、退休金、mutuelle），338 EUR/day 差距是社会保护的成本 + +## [2026-04-20] ingest | Blockchain Security Auditor +- Source file: raw/Agent/agency-agents/specialized/blockchain-security-auditor.md +- Status: ✅ 成功摄入 +- Summary: Blockchain Security Auditor 是 The Agency 项目中的智能合约安全审计专家智能体，专注于 DeFi 协议漏洞检测、形式化验证和综合审计报告撰写，涵盖重入攻击、预言机操纵、闪电贷攻击等主要漏洞类型 +- Concepts created: Reentrancy, Oracle Manipulation, Flash Loan Attack, Checks-Effects-Interactions, Formal Verification, Static Analysis, Invariant Verification +- Entities created: Slither, Mythril, Echidna, OpenZeppelin, Foundry, Chainlink, The Agency（更新） +- Source page: wiki/sources/blockchain-security-auditor.md +- Notes: 未发现与现有 wiki 内容的冲突 + +## [2026-04-20] ingest | Study Abroad Advisor +- Source file: raw/Agent/agency-agents/specialized/study-abroad-advisor.md +- Status: ✅ 成功摄入 +- Summary: Study Abroad Advisor 是 The Agency 项目中的留学规划专家智能体，为中国学生提供全流程留学申请策略指导，覆盖美、英、加、澳、欧、港、新等主要留学目的地，涵盖选校策略、文书指导、背景提升、考试规划和签证准备 +- Concepts created: 多国联申策略, 三档选校法, 留学文书策略, 背景提升规划, 标化考试规划, 签证申请准备, 留学申请时间线 +- Entities created: The Agency（更新） +- Source page: wiki/sources/study-abroad-advisor.md +- Notes: + +## [2026-04-20] ingest | Report Distribution Agent +- Source file: raw/Agent/agency-agents/specialized/report-distribution-agent.md +- Status: ✅ 成功摄入 +- Summary: Report Distribution Agent 自动化将整合后的销售报表按领地分发给对应销售代表与管理者，支持每日/每周定时分发与手动触发，并记录完整的分发审计轨迹以满足合规需求 +- Concepts created/updated: Territory Report (linked), Distribution Schedules +- Entities created/updated: STGCRM (new) +- Source page: wiki/sources/report-distribution-agent.md +- Notes: 与 Data Consolidation Agent 形成上游/下游关系，负责格式化、发送与审计 + +## [2026-04-20] ingest | Supply Chain Strategist +- Source file: raw/Agent/agency-agents/specialized/supply-chain-strategist.md +- Status: ✅ 成功摄入 +- Summary: Supply Chain Strategist 是 The Agency 项目中的供应链策略专家智能体，根植于中国制造业生态，专注于供应商管理、战略采购、质量控制与供应链数字化，帮助企业建立高效、有韧性、可持续的供应链 +- Concepts created: Kraljic Matrix, TCO（全成本所有权）, EOQ（经济订货量）, 供应商绩效考核, ABC 分类法 +- Entities created: The Agency（更新） +- Source page: wiki/sources/supply-chain-strategist.md +- Notes: + +## [2026-04-20] ingest | Korean Business Navigator +- Source file: raw/Agent/agency-agents/specialized/specialized-korean-business-navigator.md +- Status: ✅ 成功摄入 +- Summary: Korean Business Navigator 是韩国商务文化导航智能体，帮助外国专业人士理解품够决策流程、人际关系动态和沟通规范，核心概念包括품의（共识审批，6-16周决策周期）、Nunchi（눈치）阅读术、KakaoTalk商务礼仪、韩国企业职级体系和关系生命周期（소개→신뢰→계약） +- Concepts created: 품의（共识审批）, Nunchi（눈치）, KakaoTalk商务沟通, 关系生命周期 +- Entities created: +- Source page: wiki/sources/specialized-korean-business-navigator.md +- Notes: 无冲突 +- Source file: raw/Agent/agency-agents/specialized/sales-data-extraction-agent.md +- Status: ✅ 成功摄入 +- Summary: Sales Data Extraction Agent 是 The Agency 项目中的专业化 AI 智能体，专注于监控 Excel 文件目录并提取关键销售指标（MTD、YTD、Year End），通过文件系统监视器实时检测文件，灵活映射列名，数据通过 PostgreSQL 事务持久化并维护完整审计追踪 +- Concepts updated: Audit Trail（关联 Sales Data Extraction Agent）, 数据管道 Data Pipeline（关联 Sales Data Extraction Agent） +- Entities created: The Agency（更新） +- Source page: wiki/sources/sales-data-extraction-agent.md +- Notes: 未发现与现有 wiki 内容的冲突 + +## [2026-04-20] ingest | MCP Builder Agent +- Source file: raw/Agent/agency-agents/specialized/specialized-mcp-builder.md +- Status: ✅ 成功摄入 +- Summary: MCP Builder 是 The Agency 中的 MCP 服务器构建专家，强调以 Agent 为中心的接口设计、类型化参数验证、结构化输出与多传输方式支持 +- Concepts created: MCP工具接口设计, Zod参数验证, Pydantic参数验证, MCP传输协议 +- Entities created: MCP Builder, The Agency（更新） +- Source page: wiki/sources/specialized-mcp-builder.md +- Notes: + +## [2026-04-20] ingest | Compliance Auditor +- Source file: raw/Agent/agency-agents/specialized/compliance-auditor.md +- Status: ✅ 成功摄入 +- Summary: 技术合规审计专家智能体，专注于 SOC 2、ISO 27001、HIPAA 和 PCI-DSS 认证流程，从准备评估到证据收集再到持续合规 +- Concepts created: Audit Readiness, Gap Assessment, Controls Implementation, Evidence Collection, Continuous Compliance +- Entities created: Compliance Auditor, The Agency（更新） +- Source page: wiki/sources/compliance-auditor.md +- Notes: + +## [2026-04-20] ingest | Model QA Specialist +- Source file: raw/Agent/agency-agents/specialized/specialized-model-qa.md +- Status: ✅ 成功摄入 +- Summary: 独立模型 QA 专家智能体，对机器学习和统计模型进行端到端审计，覆盖文档治理、数据重建、特征分析、模型复制、校准测试、可解释性分析和公平性审计 +- Concepts created: Population Stability Index (PSI)、SHAP Analysis、Calibration Testing、Discrimination Metrics、Partial Dependence Plots、Fairness Audit、Model Audit +- Entities created: Model QA Specialist +- Source page: wiki/sources/model-qa-specialist.md +- Notes: + +## [2026-04-20] ingest | Corporate Training Designer +- Source file: raw/Agent/agency-agents/specialized/corporate-training-designer.md +- Status: ✅ 成功摄入 +- Summary: 企业培训系统架构与课程开发专家智能体，覆盖培训需求分析、课程体系设计、教学方法论（ADDIE/SAM/Bloom's/Kirkpatrick）、企业内部培训师培养（TTT）、新员工 90 天计划、领导力发展、合规培训 +- Concepts created: ADDIE 模型、SAM 模型、Bloom's Taxonomy、Kirkpatrick 四级评估模型、混合学习、 Kolb 体验式学习、TTT、HIPO 计划、360 度反馈、行动学习、翻转课堂、建构主义学习理论、Gamification、新员工培训 90 天计划 +- Entities created: DingTalk Learning、WeCom Learning、Feishu Knowledge Base、UMU Interactive Learning Platform、Yunxuetang、KoolSchool +- Source page: wiki/sources/corporate-training-designer.md +- Notes: + +## [2026-04-20] ingest | Healthcare Marketing Compliance Specialist +- Source file: raw/Agent/agency-agents/specialized/healthcare-marketing-compliance.md +- Status: ✅ 成功摄入 +- Summary: Healthcare Marketing Compliance Specialist defines a China-focused compliance role spanning medical advertising, internet healthcare, medical aesthetics, supplements, privacy, and academic detailing +- Concepts created: Healthcare Marketing Compliance, Medical Advertising Compliance, Health Supplement Marketing, Internet Healthcare Compliance, Medical Aesthetics Compliance, Patient Privacy Protection, Academic Detailing Compliance +- Entities created: Healthcare Marketing Compliance Specialist +- Source page: wiki/sources/healthcare-marketing-compliance.md +- Notes: + +## [2026-04-20] ingest | LLM Wiki +- Source file: raw/Agent/LLM Wiki.md +- Status: ✅ 成功摄入 +- Summary: LLM Wiki 描述了一个由 LLM 持续编译和维护的持久化 wiki 模式，让知识从一次性检索转变为可累积、可追溯、可维护的长期资产 +- Concepts created: LLM Wiki +- Entities created: — +- Source page: wiki/sources/LLM-Wiki.md +- Notes: + +## [2026-04-20] ingest | Document Generator +- Source file: raw/Agent/agency-agents/specialized/specialized-document-generator.md +- Status: ✅ 成功摄入 +- Summary: Document Generator 是 The Agency 体系中的程序化文档创建智能体，专注于通过代码、模板与样式系统生成 PDF、PPTX、XLSX 与 DOCX +- Concepts created: Document Generation +- Entities created: Document Generator, The Agency（更新） +- Source page: wiki/sources/specialized-document-generator.md +- Notes: + +## [2026-04-20] ingest | Identity Graph Operator +- Source file: raw/Agent/agency-agents/specialized/identity-graph-operator.md +- Status: ✅ 成功摄入 +- Summary: Identity Graph Operator 负责多智能体系统中的共享身份图与实体归一化，确保不同 agent 面对同一现实世界实体时得到同一 canonical identity，并保留合并/拆分的审计与回滚能力 +- Concepts created: Identity Governance +- Entities created: Identity Graph Operator, The Agency（更新） +- Source page: wiki/sources/identity-graph-operator.md +- Notes: + +## [2026-04-20] ingest | Recruitment Specialist +- Source file: raw/Agent/agency-agents/specialized/recruitment-specialist.md +- Status: ✅ 成功摄入 +- Summary: Recruitment Specialist 是 The Agency 体系中的招聘运营与人才获取专家，覆盖中国主流招聘平台、结构化面试、劳动法合规、候选人体验与 onboarding +- Concepts created: Recruitment Operations, Talent Assessment, Labor Law Compliance, Candidate Experience, Employer Brand, ATS, Onboarding +- Entities created: Recruitment Specialist, The Agency（更新) +- Source page: wiki/sources/recruitment-specialist.md +- Notes: + +## [2026-04-20] ingest | Civil Engineer +- Source file: raw/Agent/agency-agents/specialized/specialized-civil-engineer.md +- Status: ✅ 成功摄入 +- Summary: Civil Engineer 是一位严谨的土木/结构工程智能体，强调在多国标准下输出安全、经济、可施工的设计，并同时检查 ULS 与 SLS +- Concepts created: Global Standards Coverage +- Entities created: Civil Engineer, The Agency（更新） +- Source page: wiki/sources/specialized-civil-engineer.md +- Notes: + +## [2026-04-20] ingest | Experiment Tracker +- Source file: raw/Agent/agency-agents/project-management/project-management-experiment-tracker.md +- Status: ✅ 成功摄入 +- Summary: Experiment Tracker 是一位专注于实验设计、执行跟踪和数据驱动决策的项目管理智能体，覆盖 A/B 测试、假设验证、样本量计算、随机分配、风险监控与回滚 +- Concepts created: A/B Testing, Hypothesis Testing, Statistical Significance, Power Analysis, Randomization +- Entities created: Experiment Tracker, Project Shepherd（更新） +- Source page: wiki/sources/project-management-experiment-tracker.md +- Notes: + +## [2026-04-20] ingest | Studio Operations +- Source file: raw/Agent/agency-agents/project-management/project-management-studio-operations.md +- Status: ✅ 成功摄入 +- Summary: The Agency 项目中的 Studio Operations Agent，负责日常工作室运营、流程优化和资源协调，强调标准化、资源管理和持续改进 +- Concepts created: Process Optimization, Resource Allocation, Operational Excellence, Cross-Functional Leadership +- Entities created: Studio Operations, The Agency（更新） +- Source page: wiki/sources/project-management-studio-operations.md +- Notes: + +## [2026-04-20] ingest | Workflow Architect +- Source file: raw/Agent/agency-agents/specialized/specialized-workflow-architect.md +- Status: ✅ 成功摄入 +- Summary: Workflow Architect 是 The Agency 体系中的工作流设计专家智能体，负责把系统行为拆解为完整流程树，覆盖分支、失败模式、恢复路径与交接契约 +- Concepts created: Workflow Architecture +- Entities created: Workflow Architect, The Agency（更新） +- Source page: wiki/sources/specialized-workflow-architect.md +- Notes: + +## [2026-04-20] ingest | Government Digital Presales Consultant +- Source file: raw/Agent/agency-agents/specialized/government-digital-presales-consultant.md +- Status: ✅ 成功摄入 +- Summary: Government Digital Presales Consultant 是面向中国政府数字化转型市场的售前专家，覆盖政策解读、方案设计、招投标、POC 验证与合规适配 +- Concepts created: Digital Government, Smart City, Government Procurement, Dengbao, Miping, Xinchuang +- Entities created: Government Digital Presales Consultant +- Source page: wiki/sources/government-digital-presales-consultant.md +- Notes: + +## [2026-04-20] ingest | Cultural Intelligence Strategist +- Source file: raw/Agent/agency-agents/specialized/specialized-cultural-intelligence-strategist.md +- Status: ✅ 成功摄入 +- Summary: Cultural Intelligence Strategist 检测产品、提示词和工作流中的 invisible exclusion，并推动 global-first、文化谦逊与上下文语义审查 +- Concepts created: Cultural Intelligence, Invisible Exclusion, Global-First Architecture, Contextual Semiotics, Cultural Humility +- Entities created: Cultural Intelligence Strategist +- Source page: wiki/sources/specialized-cultural-intelligence-strategist.md +- Notes: + +## [2026-04-20] ingest | LSP/Index Engineer +- Source file: raw/Agent/agency-agents/specialized/lsp-index-engineer.md +- Status: ✅ 成功摄入 +- Summary: LSP/Index Engineer 智能体，专注于 LSP 客户端编排和语义索引工程，构建统一代码智能系统，支持 <500ms 定义/引用查询和 100k+ 符号规模 +- Concepts created: LSP (Language Server Protocol)、LSP Client Orchestration、Semantic Index、LSIF (Language Server Index Format)、Incremental Updates、Graph Construction Pipeline +- Entities created: graphd、TypeScript Language Server、Intelephense、gopls、rust-analyzer、pyright +- Source page: wiki/sources/lsp-index-engineer.md +- Notes: + +## [2026-04-20] ingest | Salesforce Architect +- Source file: raw/Agent/agency-agents/specialized/specialized-salesforce-architect.md +- Status: ✅ 成功摄入 +- Summary: Salesforce Architect 是 The Agency 体系中的 CRM 架构专家智能体，专注于 Salesforce 配置、APEX 开发、Flow 自动化和 Salesforce DX 全生命周期管理 +- Concepts created: Salesforce DX, APEX, Flow Automation, CRM Architecture +- Entities created: Salesforce, The Agency（更新） +- Source page: wiki/sources/specialized-salesforce-architect.md +- Notes: + +## [2026-04-22] ingest | DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation +- Source file: raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md +- Status: ✅ 成功摄入 +- Summary: LinkedIn 文章（Hemant Sawant）系统阐述 DevOps 文化转型框架：四大支柱（协作、自动化、持续改进、客户中心）、Agile 实践整合（Scrum/Kanban/Shift-Left/价值流映射）、转型策略（领导层支持/团队赋能/小规模试点/克服阻力）、未来趋势（AI/ML、GitOps、无服务器 DevOps、边缘计算 DevOps、DevSecOps） +- Concepts created: DevOps Culture, CI/CD Pipeline, DevSecOps, GitOps, Agile Practices +- Entities created: Hemant Sawant（LinkedIn 作者） +- Source page: wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md +- Notes: 文档补充了 wiki 中 Cloud Transformation & DevOps 主题下的文化层；与已有的 CTP（Cloud Transformation Programme）材料互补；与 Project State Management 的 Event Sourcing vs Kanban 冲突保持不变（已记录于 Conflict Area） + +## [2026-04-24] ingest | How Can a Multi-Cloud Strategy Transform Your Business ROI +- Source file: raw/Cloud & DevOps/How Can a Multi Cloud Strategy Transform Your Business ROI.md +- Status: ✅ 成功摄入 +- Summary: 多云策略全面指南，涵盖：定义与误区（多云≠备份、≠必然复杂）、企业采用8大原因（避免锁定/增强韧性/提升安全/可扩展/成本优化/创新/合规/性能）、关键业务挑战（风险缓解/成本优化/数据主权/性能/复杂性管理）、ROI最大化5路径（成本降低/资源优化/效率提升/弹性伸缩/风险管理）、电商/医疗/金融行业真实用例、4步实施指南（评估需求→选择提供商→集成管理→监控优化） +- Concepts created: Vendor-Lock-In, Data-Sovereignty, Scalability, Cost-Optimization, ROI, Risk-Mitigation +- Entities created: Cloud-Provider +- Source page: wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md +- Notes: Source page 包含完整12个章节；新创建6个 Concept 页面（Vendor-Lock-In、Data-Sovereignty、Scalability、Cost-Optimization、ROI、Risk-Mitigation）；新创建1个 Entity 页面（Cloud-Provider）；更新 overview.md 补充新概念索引；Multi-Cloud-Strategy 概念页面已存在，本次补充来源引用；与已有 DevOps/Cloud DevOps 知识体系高度互补（成本/风险/合规是云成熟度模型的重要组成部分） + +## [2026-04-23] \ No newline at end of file diff --git a/wiki/overview.md b/wiki/overview.md new file mode 100644 index 00000000..79213296 --- /dev/null +++ b/wiki/overview.md @@ -0,0 +1,63 @@ +# Overview + +This wiki is a living synthesis of curated sources spanning AI agents, cloud infrastructure, DevOps, productivity tools, and home server automation. + +## Major Themes + +### Multi-Agent AI Systems +The wiki covers two major multi-agent frameworks: **The Agency** (agency-agents) and **OpenClaw**. The Agency provides 147 specialized agents across 12 business divisions (Engineering, Design, Finance, Game Dev, Marketing, Paid Media, Product, Project Management, Testing, Support, Spatial Computing, Specialized). OpenClaw focuses on autonomous agents with persistent memory and workflow orchestration via n8n. + +Key concepts: [[Agent Personality]], [[Agent Specialization]], [[Multi-Agent Coordination]], [[Multi-Tool Integration]], [[MCP Tool Interface Design]], [[Workflow Architecture]] + +### Cloud Transformation & DevOps +Cloud Transformation Programme (CTP) materials cover AWS landing zones, EKS, Terraform, GitOps, FinOps, observability, security, and enterprise architecture. Key themes: 3 Lines of Defence framework, ITSM, container hardening, backup & DR strategies. DevOps culture focuses on four pillars: Collaboration, Automation (CI/CD, IaC), Continuous Improvement (Kaizen), and Customer-Centricity. Agile practices (Scrum, Kanban) are symbiotic with DevOps. Emerging trends: DevSecOps, GitOps, Serverless DevOps, AI/ML-driven automation, and Edge Computing DevOps. + +Key concepts: [[Landing Zone Architecture]], [[GitOps]], [[FinOps]], [[Event Sourcing]], [[Container Lifecycle Hardening]], [[AWS Backup]], [[ITSM]], [[Error Budgets]], [[Multi-Cloud Strategy]], [[Multi-Cloud-ROI]], [[DevOps Culture]], [[CI/CD Pipeline]], [[DevSecOps]], [[Agile Practices]], [[DevOps Maturity]], [[DORA Metrics]], [[Infrastructure as Code]], [[Cloud-Native]], [[Cloud Maturity Levels]], [[Cloud Adoption Strategy]], [[Cloud Service Delivery]], [[Cloud DevOps Maturity Model]], [[AIOps]], [[SLA]], [[SLO]], [[Incident Management]], [[Change Management]], [[Disaster Recovery]], [[WAF]], [[APM]], [[Cloud Security]], [[Cloud Migration]], [[High Availability]], [[Vendor-Lock-In]], [[Data-Sovereignty]], [[Continuous Integration]], [[Continuous Deployment]], [[Lead Time]], [[Time-to-Market]], [[MTTR]], [[MTTD]], [[MTTA]], [[Change Failure Rate]], [[Error Budget]], [[Rollback Rate]], [[Availability]], [[Scalability]] + +### Home Server Automation +Home office setup guides cover Docker deployments, RSSHub, FRP reverse proxy, Synology NAS, network monitoring (Prometheus/Grafana), media servers (Jellyfin, Navidrome), and scientific internet access. + +Key concepts: [[Docker-Image]], [[Docker-Save]], [[Docker-Load]], [[RSSHub]], [[内网穿透]], [[Prometheus]] + +### AI Tools & Prompt Engineering +Covers Claude Code, OpenCode, Cursor, Gemini CLI, Vibe Coding, RAG, multi-agent workflows, NotebookLM, Nano Banana prompting, and video generation tools. + +Key concepts: [[RAG从入门到精通系列]], [[Agent Personality Design]], [[Vibe Coding]], [[LLM Wiki]], [[多智能体系统可靠性]] + +### Productivity & Knowledge Management +Obsidian plugins, blogwatcher RSS monitoring, Quartz static site generation, project management systems, and personal CRM frameworks. + +Key concepts: [[Obsidian Tasks]], [[Dataview]], [[Event Sourcing]], [[Second Brain]], [[Personal CRM]] + +## Source Distribution + +| Category | Count | Key Sources | +|----------|-------|-------------| +| The Agency Agents | 147+ agents | README, CONTRIBUTING, 12 divisions | +| CTP Topics | 73 topics | AWS, Azure, FinOps, Security | +| Learning Sessions | 30+ sessions | OpenText, AWS, EKS, Cloud FinOps | +| Home Office | 60+ docs | Docker, NAS, Network, Monitoring | +| AI & Productivity | 80+ docs | Claude, OpenClaw, Obsidian, Prompting | +| Marketing Agents | 30+ agents | Cross-platform, China E-commerce | + +## Key Entities + +- [[The Agency]] — open-source AI agent collection (147 agents, 12 divisions) +- [[agency-agents]] — GitHub repository +- [[OpenClaw]] — multi-agent framework with memory +- [[n8n]] — workflow automation +- [[Quartz]] — static site generator for wikis +- [[RSSHub]] — open-source RSS aggregator +- [[Synology NAS]] — network-attached storage +- [[Claude Code]] — Anthropic CLI agent +- [[OpenCode]] — Vibe Coding CLI agent + +## Conflict Areas + +1. **Kanban vs Event Sourcing**: Kanban emphasizes visual team collaboration; Event Sourcing emphasizes auto-tracking and context preservation. [[Project State Management]] vs traditional PM tools. + +2. **Kuaishou vs Douyin**: Kuaishou emphasizes authenticity and balanced algorithm; Douyin emphasizes polished content and central recommendation. Same country, opposite platform strategies. + +3. **Micro-Enterprise vs Portage Salarial**: Micro-enterprise yields higher net income but lacks social protections; Portage Salarial costs more but includes unemployment insurance, pension, mutuelle. Financial trade-off vs social safety net. + +4. **CI/CD Build Output**: SECURITY.md says build output is always closed; GitHub Actions best practice says certain generated files should be committed for reproducibility. Reproducibility vs cleanliness tension. diff --git a/wiki/sources/cloud-devop-maturity-guideline.md b/wiki/sources/cloud-devop-maturity-guideline.md new file mode 100644 index 00000000..278ef4c0 --- /dev/null +++ b/wiki/sources/cloud-devop-maturity-guideline.md @@ -0,0 +1,73 @@ +# Cloud DevOp Maturity - Guideline + +## Source File +- [[raw/Cloud & DevOps/Cloud DevOp Maturity - Guideline.md]] + +## Metadata +- **title**: Cloud DevOp Maturity - Guideline +- **author**: shenwei +- **published**: +- **created**: +- **tags**: [] + +## Summary + +A comprehensive guideline for evaluating cloud DevOps maturity in enterprise-level SaaS organizations. The document outlines 8 key areas: definition of maturity, maturity models (CMMI, DORA), foundational pillars (Automation, Collaboration, Monitoring, Security), tooling choices, measurement metrics, challenges, case studies, and a roadmap for achieving higher maturity levels. + +## Key Topics Covered + +### 1. Definition of Cloud DevOps Maturity +- DevOps maturity encompasses automation, collaboration between development and operations, speed of delivery, and reliability +- Business case: reducing time-to-market, improving operational efficiency, enhancing product reliability + +### 2. Key Maturity Models +- **CMMI** (Capability Maturity Model Integration) +- **DORA** (DevOps Research & Assessment) metrics: + - Deployment frequency + - Lead time for changes + - Change failure rate + - Mean Time to Recovery (MTTR) + +### 3. Foundational Pillars +- **Automation**: CI/CD pipelines, IaC, test automation +- **Collaboration and Culture**: Cross-team collaboration, breaking down silos +- **Monitoring and Observability**: Continuous monitoring, logging, swift issue resolution +- **Security Integration (DevSecOps)**: Security automated into DevOps lifecycle + +### 4. Tooling and Technology +- DevOps Toolchain: CI/CD, IaC (Terraform, Ansible), Containerization (Kubernetes, Docker) +- Monitoring: Prometheus, Grafana +- Cloud-native practices: microservices, serverless + +### 5. Metrics for Measuring Maturity +- **KPIs**: Deployment frequency, lead times, system uptime, incident resolution times +- **Qualitative measures**: Employee collaboration, goal alignment, feedback loops + +### 6. Challenges +- Resistance to change +- Scaling DevOps globally +- Regulatory and compliance constraints + +### 7. Roadmap +- Conduct DevOps maturity assessment +- Build a DevOps Center of Excellence +- Implement phased improvements (starting with CI/CD and automation) +- Ongoing iteration and continuous improvement + +## Related Sources +- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]] — Traditional IT to Advanced DevOps maturity model +- [[sources/cloud-operating-model-key-strategies-and-best-practices.md]] — Cloud operating model strategies +- [[sources/what-is-devsecops-best-practices-benefits-and-tools.md]] — DevSecOps practices and tools +- [[sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md]] — Cloud maturity model guide +- [[sources/how-agentic-ai-can-help-for-cloud-devops.md]] — AI for Cloud DevOps + +## Concepts Extracted +- [[concepts/DevOps-Maturity]] +- [[concepts/DORA-Metrics]] +- [[concepts/DevSecOps]] +- [[concepts/CI-CD-Pipeline]] +- [[concepts/Infrastructure-as-Code]] +- [[concepts/Cloud-Native]] + +## Ingested +- Date: 2026-04-21 diff --git a/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md b/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md new file mode 100644 index 00000000..d94414ff --- /dev/null +++ b/wiki/sources/cloud-maturity-model-a-detailed-guide-for-cloud-adoption.md @@ -0,0 +1,63 @@ +--- +title: Cloud Maturity Model - A Detailed Guide For Cloud Adoption +source: https://www.bacancytechnology.com/blog/cloud-maturity-model +author: shenwei +published: 2024-07-08 +created: 2025-02-28 +description: Explore the Cloud Maturity Model (CMM) with key components, benefits, and stages, and optimize processes with best practices for successful cloud adoption. +tags: [Cloud, Cloud Adoption, Maturity Model, CMM, CMM 4.8, Cloud Native, CSMM, SAMM, AWS CAF, Azure CAF, GCP CAF] +link: +--- + +## Source File +- [[raw/Cloud & DevOps/Cloud Maturity Model A Detailed Guide For Cloud Adoption.md]] + +## Summary + +本文档系统性介绍了 **Cloud Maturity Model (CMM)** 云成熟度模型，包含以下核心内容： + +- **5个成熟度阶段**：从 Level 0（无云就绪）到 Level 5（优化级），覆盖企业云转型的完整路径 +- **关键组成要素**：从业务（财务、战略、组织、文化、治理、合规、采购等）和技术（架构、应用、DevOps、安全、IaaS/PaaS/SaaS、AI/IoT等）两个维度评估 +- **三大评估维度**：People（人员）、Processes（流程）、Technology（技术） +- **7大收益**：战略规划增强、团队协作提升、应用性能提升、安全性增强、上市时间缩短、行业对标、成本节约 +- **最佳实践**：设定云采用目标、识别当前成熟度级别、选择合适的成熟度模型、遵循治理与合规、安全与风险管理 +- **主流云成熟度模型对比**：CMM 4.8、Cloud Native Maturity Model、CSMM、SAMM、AWS CAF、Azure CAF、Google Cloud CAF + +## Key Takeaways + +- Forrester 预测全球云成熟度模型行业到 2025 年将达 15 亿美元 +- Gartner 指出超过 60% 的组织正在积极实施云成熟度模型 +- 成熟度模型不是追求完全上云，而是找到适合组织需求的平衡点 +- Level 5 是目标但往往更具理想性，建议选择性采纳带来明确业务价值的要素 +- 跨越低级别（如管理和流程定义）可能导致后续挑战和不必要的成本 + +## Key Entities + +- [[Cloud Maturity Model]] — 主体框架 +- [[Cloud Native Maturity Model]] — 云原生成熟度模型 +- [[Cloud Security Maturity Model]] — 云安全成熟度模型 +- [[Software Assurance Maturity Model]] — 软件保障成熟度模型（SAMM） +- [[AWS Cloud Adoption Framework]] — AWS 云采用框架 +- [[Azure Cloud Adoption Framework]] — Azure 云采用框架 +- [[Google Cloud Adoption Framework]] — Google Cloud 云采用框架 +- [[Open Alliance for Cloud Adoption]] — OACA 云采用联盟 +- [[Cloud Maturity Levels]] — 成熟度5级模型 +- [[Cloud Adoption Strategy]] — 云采用策略 + +## Concepts + +- [[Cloud Adoption]] — 云采用 +- [[Cloud Migration]] — 云迁移 +- [[Cloud Governance]] — 云治理 +- [[Cloud Security]] — 云安全 +- [[FinOps]] — 云财务管理 +- [[Cloud-Native]] — 云原生 +- [[Cloud Cost Optimization]] — 云成本优化 +- [[Multi-Cloud Strategy]] — 多云策略 +- [[Hybrid Cloud]] — 混合云 +- [[People-Process-Technology]] — 人-流程-技术三维评估 +- [[Cloud Center of Excellence]] — 云卓越中心（CCoE） +- [[GAP Analysis]] — 差距分析 +- [[Cloud Compliance]] — 云合规 +- [[CAPEX vs OPEX]] — 资本支出vs运营支出 +- [[TCO (Total Cost of Ownership)]] — 总拥有成本 diff --git a/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md b/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md new file mode 100644 index 00000000..f2625f44 --- /dev/null +++ b/wiki/sources/devops-culture-and-transformation-fostering-collaboration-agile-practices-and-innovation-linkedin.md @@ -0,0 +1,63 @@ +--- +title: "DevOps Culture and Transformation: Fostering Collaboration, Agile Practices, and Innovation" +type: source +tags: [devops, agile, cloud, transformation] +date: 2026-04-17 +source_file: raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md +--- + +## Source File +- [[raw/Cloud & DevOps/DevOps Culture and Transformation Fostering Collaboration, Agile Practices, and Innovation LinkedIn.md]] + +## Summary +This LinkedIn article by Hemant Sawant provides a comprehensive guide to DevOps culture and organizational transformation. It covers the four foundational pillars of DevOps (collaboration, automation, continuous improvement, and customer-centricity), how to integrate Agile practices, and a strategic playbook for driving DevOps transformation at scale. The article also outlines future trends including AI/ML in DevOps, GitOps, Serverless DevOps, and Edge Computing DevOps. + +## Key Claims + +### DevOps Pillars +- DevOps dismantles silos between Development and Operations through cross-functional teams that share ownership of the entire software lifecycle +- Automation eliminates manual toil, reduces errors, and accelerates feedback loops — covering CI/CD, IaC, and monitoring/observability +- Continuous Improvement (Kaizen) requires blameless post-mortems, metrics-driven bottleneck identification, and chaos engineering +- Customer-Centricity means embedding feedback loops via feature flagging and A/B testing + +### Agile + DevOps Integration +- Agile and DevOps are symbiotic — Agile provides iterative development, DevOps extends agility to operations +- Shift-Left practices bring operations concerns (security, performance) into the development phase +- Value Stream Mapping visualizes workflows to eliminate waste and streamline handoffs + +### Transformation Strategy +- Leadership buy-in is essential — executives must champion collaboration and allocate resources +- Upskilling through certifications (AWS DevOps, Kubernetes) and internal communities of practice (Guilds/CoEs) is critical +- Pilot projects should demonstrate quick wins before enterprise-wide rollout +- Resistance must be addressed by emphasizing that automation frees teams for higher-value work + +### Future Trends +- AI and ML for intelligent automation in code reviews, anomaly detection, and self-healing infrastructure +- GitOps as the standard for managing infrastructure via Git as the single source of truth +- Serverless DevOps reducing operational overhead via FaaS (e.g., AWS Lambda) +- Edge Computing and IoT DevOps enabling real-time performance optimization closer to end-users +- DevSecOps embedding security more deeply into CI/CD workflows + +## Key Quotes + +> "DevOps isn't just about tools or automation; it's a mindset shift that prioritizes collaboration, continuous learning, and customer-centricity." + +> "DevOps isn't a checkbox—it's a continuous evolution." + +## Connections + +### Related Entities +- [[Hemant Sawant]] — Author of this LinkedIn article + +### Related Concepts +- [[DevOps Culture]] — Core cultural principles covered in this article +- [[CI/CD Pipeline]] — Key automation enabler discussed +- [[Infrastructure as Code (IaC)]] — Automation pillar of DevOps +- [[DevSecOps]] — Shift-Left security integration +- [[GitOps]] — Future trend for infrastructure management +- [[Agile Practices]] — Complementary methodology integrated with DevOps +- [[Continuous Improvement (Kaizen)]] — Japanese philosophy applied to DevOps +- [[Value Stream Mapping]] — Lean technique for DevOps workflow optimization +- [[Feature Flagging]] — Customer feedback mechanism in DevOps +- [[Chaos Engineering]] — Proactive resilience testing +- [[Shift-Left Testing]] — Moving testing earlier in the development lifecycle diff --git a/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md b/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md new file mode 100644 index 00000000..ddbf01a3 --- /dev/null +++ b/wiki/sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md @@ -0,0 +1,184 @@ +# DevOps Maturity Model From Traditional IT to Advanced DevOps + +## Source File +- [[raw/Cloud & DevOps/DevOps Maturity Model From Traditional IT to Advanced DevOps.md]] + +## Metadata +- **Source**: https://www.bacancytechnology.com/blog/devops-maturity-model +- **Author**: shenwei +- **Published**: 2024-08-14 +- **Created**: 2025-03-01 +- **Description**: Explore the DevOps Maturity Model: its five stages, benefits, progress metrics, security considerations & how to avoid challenges for effective implementation. + +## Quick Summary + +The blog covers the DevOps Maturity Model, exploring its key components and the five distinct stages of maturity. We'll uncover how adopting this model revolutionizes your organization, enhances security practices, and tackles common challenges you might face. By offering actionable insights, we aim to guide you through measuring and optimizing your DevOps journey, ensuring continuous improvement and long-term success. + +## What is the DevOps Maturity Model? + +The DevOps maturity model is a structured framework that guides organizations through adopting and implementing DevOps principles. This model helps assess an organization's current DevOps practices, identify improvement areas, and outline steps to advance to higher maturity levels. It also evaluates your DevOps practices, covering aspects such as collaboration, release speed, and quality, adherence to principles, use of automation, and tool sets. This DevOps Maturity Model assessment allows organizations to: + +- Analyze and measure their current DevOps capabilities and methodologies. +- Establish benchmarks for their existing DevOps practices. +- Define their target maturity level. +- Identify key areas that require enhancement. +- Develop a strategic roadmap to advance to higher maturity levels. +- Acquire knowledge about optimal practices, security measures, and key performance indicators. + +## Key Focus Areas for DevOps Maturity Levels + +Experts suggest assessing an organization's DevOps maturity by examining its performance in four key areas: + +### Culture and Strategy +In the DevOps maturity model, culture shapes team collaboration and operations. A teamwork, transparency, and unity culture supports efficient deployment and monitoring. For advanced maturity, the team is supposed to adopt a customer-centric and product-oriented mindset, ensuring all team members align their goals to deliver rapid value. + +### Automation +DevOps automation or AutoDevOps is crucial for continuous delivery and deployment. It simplifies development, testing, and production by automating repetitive tasks, which saves time and improves resource efficiency in the CI/CD process. + +### Structure and Process +In the maturity model in DevOps, the process element involves breaking down work into manageable steps to complete a product's lifecycle. Effective DevOps processes should be standardized and clearly defined to maximize efficiency. Key characteristics of a mature DevOps framework include handling work in small, manageable chunks, maintaining complete transparency of progress, and eliminating unnecessary steps that lead to delays and resource waste. + +### Collaboration and Sharing +Collaboration is a cornerstone of the DevOps model and a key metric of team effectiveness and productivity. Cohesive teams are more likely to optimize processes and develop practical solutions, leveraging diverse skill sets towards a unified objective. + +### Technology +Selecting the appropriate technology is crucial in the DevOps framework. The chosen tools and technologies should align with your team's needs to maximize productivity and effectiveness. Modern tools enable DevOps teams to continuously develop and monitor products, aiming to deliver valuable software to customers swiftly. + +## What Defines a High-Quality DevOps Maturity Model + +- **Assessment Criteria**: Standards used to evaluate the effectiveness and maturity of DevOps practices within an organization. +- **Maturity Levels**: A structured progression of DevOps adoption typically encompasses five stages, though some models may include additional phases. +- **DevOps Practices**: Detailed descriptions of core DevOps techniques including release management, task automation, security protocols, CI/CD, and IaC. +- **Relevant Metrics**: KPIs for evaluating DevOps effectiveness including deployment frequency, MTTR, and change failure rate. +- **Cultural Guides**: Strategies for assessing and enhancing organizational culture to align with DevOps principles. +- **Tools and Technologies**: Version control systems, CI/CD platforms, automation tools, and containerization solutions. +- **Roles and Responsibilities**: Precise definitions of team roles including process ownership, disaster recovery, QA, CI/CD pipeline design, threat response, and system availability. + +## 5 Stages of the DevOps Maturity Model + +### Phase 1: Initial/Ad-Hoc (You Haven't Started DevOps) + +| Aspect | Description | +|--------|-------------| +| Organization | Teams (development, operations, security, product management, and users) work in isolation with different priorities, leading to inefficiencies. | +| Delivery | Waterfall approach, focusing on features and timelines instead of business outcomes. Release cycles based on milestones rather than user feedback or market changes. | +| Automation | Manual infrastructure management is slow and error-prone. Servers receive individual attention instead of being managed in bulk. | +| Testing | Manual testing creates bottlenecks and delays. | +| Security | Security involvement occurs only weeks before release, focusing on minimal compliance scans. | +| Monitoring | Outages are reported by users rather than detected proactively, leading to reactive responses. | +| Operations | Operations teams receive releases with minimal planning, affecting deployment efficiency. | + +### Phase 2: DevOps in Pockets + +| Aspect | Description | +|--------|-------------| +| Organization | Dev and Ops teams work together on small, strategic projects. | +| Delivery | Agile practices are introduced, focusing on business and user value instead of just project planning. | +| Version Control | Version control is used to manage environments and configurations. | +| Automation | Teams use automation to reduce release risks, but some automation is superficial. | +| Testing | Unit, integration, and end-to-end tests are implemented to enhance quality. | +| Security | Security operates separately from the rest of the team for now. | +| Monitoring | Essential monitoring tools alert the team to issues as soon as they affect users. | +| Manual Interventions | Ops staff must manually intervene when issues occur in production. | +| Operations | The operations team stays informed about upcoming releases and looks for improvement opportunities from performance alerts. | + +### Phase 3: Automated and Defined + +| Aspect | Description | +|--------|-------------| +| Organization | Well-defined and standardized processes across Dev and Ops teams. | +| Delivery | Agile practices are increasingly integrated across development, operations, design, and business teams. | +| Automation | Most infrastructure is automated, making provisioning repeatable and reliable, enabling more frequent deployments. | +| Testing | Security scans are incorporated into testing throughout the development process rather than conducted only at deployment. | +| Security | Security becomes involved in design, architecture, and operations discussions. | +| Bundled Releases | Releases often bundle unrelated features into big projects. | +| Technical Debt | Concepts of MVPs and technical debt still need to be prioritized. | +| Operations | The operations team adopts new automation techniques in their practices. | + +### Phase 4: Highly Optimized DevOps + +| Aspect | Description | +|--------|-------------| +| Organization | Ops and development teams work closely with project management and security in product planning. | +| Automation | Immutable infrastructure replaces old servers rather than updating them. Infrastructure and code updates are managed through pipelines. Security updates are incorporated directly into the product development workflow. | +| Testing | Performance and load testing ensure deployments are ready for production scale. | +| Tech Debt and MVPs | Use of MVPs and management of tech debt to speed up releases. | +| Security | Dependency management identifies third-party vulnerabilities before they cause issues. Continuous security monitoring spreads security awareness across the team. | +| Monitoring | Continuous application monitoring tracks the system's overall health for early problem detection and analysis of root causes. | +| Operations | Developers consider operational aspects in documentation, analytics, and standard operating procedures. | + +### Phase 5: Fully Mature DevOps + +| Aspect | Description | +|--------|-------------| +| Organization | Self-sufficient, full-stack teams across business units. | +| Delivery | Multiple deployments per day with high certainty and minimal risk. | +| Automation | Zero human intervention for code changes passing through the pipeline. | +| Testing | Continuous use of real-time data to make informed decisions and optimize processes. | +| Security | Prevent insecure or non-compliant code from reaching production; high-level security integration. | +| Monitoring | Max uptime with no interruptions to customer experience; high collaboration across teams. | +| Operations | Rapid, data-driven decision-making and innovation are encouraged; teams excel in collaboration and experimentation. | + +## Business Benefits of Adopting the Maturity Model in DevOps + +- **Quickier Adjustment to Changes**: CI/CD pipelines enable swift roll-out of new features and maintain operational agility. +- **Capability to Seize Opportunities**: Advanced DevOps practices enable rapid deployment of updates, helping companies enter new markets ahead of competitors. +- **Spot Areas of Satisfaction**: Consistent evaluation of practices helps pinpoint inefficiencies and implement targeted improvements. +- **Better Scalability**: IaC enables automated resource provisioning and management with minimal manual effort. +- **Enhanced Operational Performance**: Automation of repetitive tasks bridges gaps between development and operations teams, reducing manual errors. +- **Faster Delivery Times**: Automated testing, integration, and deployment significantly reduce time-to-market. +- **Improved Quality**: Continuous monitoring and feedback loops enable early detection and resolution of issues. + +## Security Linked With the DevOps Maturity Model + +As organizations advance in their DevOps automation, the need for faster release cycles and digital innovation becomes crucial, intensifying the focus on security. The core of DevOps security is merging development, operations, and security into a unified process — realized through **DevSecOps**, which guarantees that security is woven into every phase of the Software Development Lifecycle. Effective DevSecOps practices involve collaboration between DevOps and security teams, implementing security policies and frameworks across all tools and resources. Solutions like containerization address security issues by minimizing the exposure of vulnerable resources. + +## Most Common Roadblocks That Hold DevOps Maturity Back + +- Poor communication between Dev and Ops teams +- Lack of clear objectives and strategies +- Resistance to change +- Insufficient investments in tools, training, and resources +- Poor governance leading to inconsistent practices +- Inflexible processes and workflows +- Excluding end-users from the improvement project +- Inadequate integration with business processes + +## How To Measure DevOps Maturity + +DevOps maturity metrics include: + +- **Time-To-Market**: Period from initial concept to product launch +- **Lead Time**: Interval from code commitment to deployment +- **Development Frequency**: Rate at which code is deployed within a set period +- **Code Quality**: Code complexity, test coverage, and feedback from code evaluations +- **Code Deployment Success Rate**: Proportion of successful deployments +- **Change Failure Rate**: Proportion of deployments that encounter issues or failures +- **Rollback Rate**: Proportion of deployments that are reverted +- **Error Budget**: Permissible rate of errors and failures in production +- **Availability**: Time the system remains operational and accessible to users +- **Scalability**: System's ability to manage increased load without performance issues +- **Time-in-stage**: Average duration to complete each phase of the development process +- **Code Review Feedback Loop Time**: Time to receive and act on feedback from code reviews +- **MTTR (Mean Time to Recovery)**: Average time to recover from a failure +- **MTTD (Mean Time to Detect)**: Average time to identify a problem +- **MTTA (Mean Time to Acknowledge)**: Average time to acknowledge and begin addressing a problem + +## Related Concepts +- [[concepts/DevOps-Maturity]] — General DevOps maturity assessment +- [[concepts/DORA-Metrics]] — Core DORA metrics for DevOps performance measurement +- [[concepts/DevSecOps]] — Security integration in DevOps +- [[concepts/Continuous-Integration]] — CI practices in DevOps maturity +- [[concepts/Continuous-Deployment]] — CD practices in DevOps maturity +- [[concepts/Lead-Time]] — Lead Time for changes metric +- [[concepts/Time-to-Market]] — Time-to-market metric +- [[concepts/MTTR]] — Mean Time to Recovery +- [[concepts/MTTD]] — Mean Time to Detect +- [[concepts/MTTA]] — Mean Time to Acknowledge +- [[concepts/Change-Failure-Rate]] — Change failure rate metric +- [[concepts/Error-Budget]] — Error budget concept + +## Source References +- This source adds depth to the [[entities/DevOps-Maturity-Model]] entity with detailed Phase 1-5 descriptions +- Complements [[concepts/DevOps-Maturity]] with specific organizational and technical characteristics at each maturity level +- Expands [[concepts/DORA-Metrics]] with additional operational metrics (MTTD, MTTA, Time-to-Market, Rollback Rate, Error Budget, Availability, Scalability) diff --git a/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md b/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md new file mode 100644 index 00000000..3c7f7659 --- /dev/null +++ b/wiki/sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md @@ -0,0 +1,154 @@ +--- +title: How Can a Multi Cloud Strategy Transform Your Business ROI? +source: https://www.bacancytechnology.com/blog/multi-cloud-strategy +author: shenwei +published: 2024-12-24 +created: 2025-03-01 +description: Explore how a multi-cloud strategy can boost performance, reduce risks, and maximize ROI on your cloud investments while ensuring scalability and flexibility. +tags: [Multi-Cloud, Cloud Strategy, ROI, Cloud DevOps] +--- + +# How Can a Multi Cloud Strategy Transform Your Business ROI? + +## Source File +- [[raw/Cloud & DevOps/How Can a Multi Cloud Strategy Transform Your Business ROI.md]] + +## Quick Summary + +This article explores what a multi-cloud strategy is, why it's a game-changer for businesses, and how it addresses key challenges like vendor lock-in, compliance, and performance optimization. The guide covers leveraging strengths of multiple cloud providers, streamlining operations, and reducing risks. + +## Key Statistics + +- **78%** of businesses leveraging multi-cloud have workloads deployed in more than three public clouds (Virtana) +- **86%** of companies intend to adopt multi-cloud by end of 2024 (New Horizons) +- **30%** reduction in operations costs after optimizing resources and negotiating favorable prices (Forrester) + +## What is Multi-Cloud Strategy? + +**Definition**: A distinctive approach using instances of services on multiple clouds (Azure, GCP, AWS) instead of one vendor, allowing businesses to leverage each provider's strengths and unique features. + +**How It Works**: Businesses distribute workloads across providers to access specific services or pricing models without single-provider dependency. + +### Common Misconceptions + +- **Not Just a Backup Strategy**: Multi-cloud is not merely disaster recovery — its true value lies in optimizing performance, cost, and scalability +- **Not Always More Complex**: With right tools (cloud automation, governance frameworks, containerization), multi-cloud strengthens system resilience + +## Why Businesses Adopt Multi-Cloud + +1. **Avoiding Vendor Lock-In** — Pick best cloud services based on costs, performance, or special functions +2. **Increased Resilience and Reliability** — Redundancy across platforms ensures service continuity +3. **Improved Security Posture** — Deploy different security mechanisms within each provider's strong points +4. **Scalability** — Accommodate fluctuating demands with flexible resource allocation +5. **Cost Optimization** — Tap into each provider's cost advantages (one may be cheaper for storage, another for compute) +6. **Access to Innovation** — Stay at forefront with different providers' tools and services +7. **Regulatory Compliance** — Pick providers with region/industry-specific certifications +8. **Performance Optimization** — Select best provider for different workloads (ML vs. analytics) + +## Key Business Challenges Addressed + +1. **Risk Mitigation** — Distribute workloads over multiple clouds to prevent single-provider failure +2. **Cost Optimization** — Get best deals across providers, reduce overhead costs +3. **Data Sovereignty** — Follow global and regional data regulations with compliant storage +4. **Performance** — Optimize for different workload types with superior infrastructure +5. **Complexity Management** — Use multi-cloud management tools for centralized control + +## How Multi-Cloud Maximizes ROI + +### Cost Reduction +- Avoid high single-cloud pricing structures +- Drive hard bargains for better rates +- Prevent paying for unnecessary resources + +### Resource Optimization +- Allocate workloads to best-suited provider (e.g., Google Cloud for ML, AWS/Azure for general infra) + +### Efficiency Gains +- Create tailored cloud architecture +- Reduce downtime, improve performance +- Faster deployment times, better availability + +### Flexibility in Scaling +- Dynamically allocate resources based on demand +- Expand on one provider during traffic spikes without capacity limits +- Avoid overpaying for unused capacity + +### Better Risk Management +- Eliminate single-provider dependency +- Other providers step in when one goes down + +## Real-World Use Cases + +### E-Commerce +- High availability and scalability during peak seasons (Black Friday, Cyber Monday) +- Scale resources across providers for traffic spikes +- Fast customer load times + +### Healthcare +- Keep sensitive patient data secure (HIPAA compliance) +- Distribute data across compliant cloud platforms +- Cut costs from single-cloud dependency + +### Finance +- Secure financial data and protect from regulatory requirements +- Use best security features of different providers +- Reduce risk and vendor lock-in for better SLAs and ROI + +## Implementation Steps + +### Step 1: Assess Your Needs +- Identify goals (resiliency, cost optimization, scale) +- Budget analysis +- Resource requirements assessment + +### Step 2: Choose Right Providers +- Align services with needs (AWS for infra, Google Cloud for analytics, Azure for AI) +- Evaluate features, security, compliance, cost, performance + +### Step 3: Integrate and Manage +- Adopt multi-cloud management tools (Kubernetes, Terraform) +- Ensure data interoperability, avoid data silos + +### Step 4: Monitor and Optimize +- Track resource usage (CloudHealth, Datadog) +- Implement cost-saving measures through workload optimization + +## Challenges and Solutions + +1. **Integration Complexity** + - **Challenge**: Compatibility issues and operational silos + - **Solution**: Use Kubernetes, Terraform, or cloud APIs + +2. **Security Risks** + - **Challenge**: Data breaches and inconsistent policies + - **Solution**: Centralized security protocols, multi-cloud IAM, end-to-end encryption + +3. **Lack of Expertise** + - **Challenge**: Specialized skills may be scarce + - **Solution**: Invest in upskilling, hire experts, or partner with managed providers + +## Related Concepts + +- [[Multi-Cloud-Strategy]] — Updated with ROI maximization framework +- [[Cloud-Maturity-Model]] — Cloud maturity levels for multi-cloud adoption +- [[Cloud-Adoption-Strategy]] — Overall cloud adoption planning +- [[FinOps]] — Cloud financial management +- [[Vendor-Lock-In]] — Risk of single-provider dependency +- [[Data-Sovereignty]] — Regional compliance requirements +- [[Kubernetes]] — Container orchestration for multi-cloud +- [[Terraform]] — Infrastructure as Code for multi-cloud + +## Key Entities + +- [[Cloud Computing]] — Updated with multi-cloud deployment model +- [[AWS]] — Amazon Web Services +- [[Azure]] — Microsoft Azure +- [[Google-Cloud]] — Google Cloud Platform + +## Notes + +This source provides a comprehensive business case for multi-cloud ROI, extending the existing [[Multi-Cloud-Strategy]] concept with: +- Quantified benefits (30% cost reduction, 78% adoption rate) +- Industry-specific use cases (e-commerce, healthcare, finance) +- Practical implementation roadmap (4 steps) +- Real-world challenges with proven solutions diff --git a/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md b/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md new file mode 100644 index 00000000..f571a885 --- /dev/null +++ b/wiki/sources/the-myths-and-misconceptions-about-cloud-computing-linkedin.md @@ -0,0 +1,62 @@ +--- +title: "The Myths and Misconceptions About Cloud Computing | LinkedIn" +source: https://www.linkedin.com/pulse/myths-misconceptions-cloud-computing-raj-vardhan-singh-w86mc/?trackingId=rM%2B%2BhFXj9kp11hppPbPFkQ%3D%3D +author: shenwei +published: 2001-02-25 +created: 2025-03-02 +description: +tags: [] +--- + +# The Myths and Misconceptions About Cloud Computing + +Cloud computing has revolutionized the way businesses and individuals manage data, applications, and IT infrastructure. However, despite its widespread adoption, many myths and misconceptions persist, leading to confusion and hesitation among potential users. In this article, we debunk some of the most common cloud computing myths to provide a clearer understanding of its capabilities and limitations. + +## Myth 1: Cloud Computing is Not Secure + +### Reality: Cloud Security is Often More Robust Than On-Premises Solutions + +One of the biggest misconceptions about cloud computing is that it is inherently insecure. In reality, leading cloud providers invest heavily in security measures, including encryption, firewalls, and multi-factor authentication. Many cloud platforms comply with stringent industry standards such as ISO 27001, HIPAA, and GDPR. Additionally, cloud providers offer automated security updates and 24/7 monitoring, reducing the risk of breaches compared to traditional on-premises systems. + +## Myth 2: The Cloud is Just Someone Else's Computer + +### Reality: The Cloud is a Vast Network of Data Centers with Advanced Infrastructure + +While it is true that cloud services rely on remote servers, they are far more than just "someone else's computer." Cloud providers operate highly sophisticated data centers with redundancy, scalability, and high availability. These infrastructures are designed to handle massive workloads, offer automated failover, and provide secure, scalable computing power that surpasses typical on-premises solutions. + +## Myth 3: Cloud Computing is Too Expensive + +### Reality: Cloud Computing Can Be Cost-Effective with Proper Management + +Some organizations assume that moving to the cloud will lead to skyrocketing costs. However, cloud computing follows a pay-as-you-go model, allowing businesses to scale resources as needed. Cost optimization strategies such as reserved instances, auto-scaling, and serverless computing help reduce expenses. Additionally, eliminating the need for on-premises hardware, maintenance, and upgrades often results in significant cost savings. + +## Myth 4: You Lose Control Over Your Data in the Cloud + +### Reality: Cloud Services Provide Extensive Data Control and Management Tools + +A common fear is that once data is in the cloud, companies lose control over it. However, cloud providers offer robust data governance tools, allowing organizations to manage permissions, encrypt data, and monitor access logs. Additionally, many cloud services provide hybrid and multi-cloud options, enabling businesses to maintain control over where and how their data is stored. + +## Myth 5: Cloud Computing is Only for Large Enterprises + +### Reality: Businesses of All Sizes Can Benefit from the Cloud + +While large enterprises have been early adopters, cloud computing is highly accessible to small and medium-sized businesses (SMBs). Cloud platforms offer flexible pricing, allowing SMBs to leverage enterprise-grade technology without large upfront investments. Many startups and small businesses rely on cloud solutions for agility, scalability, and cost savings. + +## Myth 6: Migration to the Cloud is Too Complex and Risky + +### Reality: Cloud Migration Can Be Smooth with Proper Planning + +Although migrating to the cloud requires careful planning, cloud providers offer extensive tools and support to facilitate the process. Strategies like phased migration, hybrid cloud solutions, and professional cloud migration services help mitigate risks and ensure a smooth transition. With the right approach, businesses can move workloads to the cloud with minimal disruption. + +## Myth 7: Cloud Performance is Unreliable + +### Reality: Cloud Providers Offer High Availability and Redundancy + +Some believe that cloud-based services are prone to frequent outages. However, major cloud providers offer service-level agreements (SLAs) that guarantee uptime, often exceeding 99.99%. Redundant infrastructure, automated failover, and global data center distribution enhance reliability, making cloud solutions highly resilient. + +## Last but not least + +Cloud computing is often misunderstood due to persistent myths and misconceptions. In reality, the cloud offers **enhanced security, cost-effectiveness, scalability, and control over data**. By debunking these myths, businesses, and individuals can make informed decisions about adopting cloud technology to drive efficiency and innovation. + +## Source File +- [[raw/Cloud & DevOps/The Myths and Misconceptions About Cloud Computing LinkedIn.md]] diff --git a/wiki/sources/what-i-know-about-cloud-service-delivery-1.md b/wiki/sources/what-i-know-about-cloud-service-delivery-1.md new file mode 100644 index 00000000..38e4161b --- /dev/null +++ b/wiki/sources/what-i-know-about-cloud-service-delivery-1.md @@ -0,0 +1,92 @@ +--- +title: "What I Know About Cloud Service Delivery 1" +source: +author: shenwei +published: +created: +description: +tags: [] +link: +--- + +## Source File +- [[raw/Cloud & DevOps/What I know about Cloud Service Delivery 1.md]] + +## Summary + +This document provides a comprehensive overview of **Cloud Service Delivery**, defining it as the bridge between raw cloud technology capabilities (IaaS, PaaS, SaaS) and the reliable, secure, performant, and cost-effective services that businesses and users consume. It covers the organizational structure of a Cloud Service Delivery team, 12 functional domains of cloud service delivery operations, and introduces the Cloud DevOps Maturity Model and AIOps concepts. + +## Key Concepts + +### Core Concepts +- [[Cloud Service Delivery]] — The entire lifecycle of making cloud services operational, available, secure, performant, and valuable to end-users +- [[Cloud Service Delivery Team]] — Multi-disciplinary team: Cloud Infrastructure Engineer, Cloud Operation Engineer (DevOps/SRE), Cloud Security Specialists, Cloud Support Engineer, Cloud FinOps Engineer +- [[Cloud DevOps Maturity Model]] — Maturity framework for evaluating cloud DevOps capabilities +- [[AIOps]] — Artificial Intelligence for IT Operations + +### Operational Domains +1. [[Service Provisioning & Deployment]] — Setting up cloud infrastructure, automating deployments, configuring services, managing resource allocation and scaling +2. [[Infrastructure Management]] — Monitoring health/performance/capacity, patching, managing physical data center aspects, ensuring HA and DR +3. [[Platform Management (PaaS)]] — Managing middleware, databases, development tools, runtime environments, platform scalability/security/performance +4. [[Application Operations & Management]] — Monitoring app performance, deploying updates, managing configuration and secrets, ensuring scalability and resilience +5. [[Security & Compliance Management]] — Implementing security controls (firewalls, IDS/IPS, encryption, IAM), vulnerability scanning, incident response, regulatory compliance (GDPR, HIPAA, PCI-DSS), auditing +6. [[Performance & Availability Monitoring]] — 24/7 monitoring, SLA/SLO tracking, proactive detection, incident response +7. [[Incident & Problem Management]] — Responding to alerts, troubleshooting, incident management, problem management (root cause analysis) +8. [[Change & Configuration Management]] — Change control, Infrastructure as Code (IaC), testing and rollback plans +9. [[Cost Management & Optimization]] — Monitoring consumption, eliminating waste, right-sizing, reserved instances/savings plans +10. [[Customer Onboarding & Support]] — User setup, documentation, helpdesk/service desk, billing inquiries +11. [[Service Governance & Lifecycle Management]] — Service catalogs, SLAs, service lifecycle (introduction, operation, retirement), continuous improvement, vendor management +12. [[Backup, Recovery & Disaster Management]] — Backup strategies, restore testing, DR plans, failover/failback procedures + +### Related Concepts +- [[SLA]] — Service Level Agreement (e.g., 99.9% vs 99.99% uptime) +- [[SLO]] — Service Level Objective +- [[IaC]] — Infrastructure as Code +- [[FinOps]] — Cloud financial management +- [[DevOps]] — Development and Operations integration +- [[SRE]] — Site Reliability Engineering +- [[WAF]] — Web Application Firewall +- [[APM]] — Application Performance Monitoring +- [[BPM]] — Business Performance Monitoring + +## Best Practices Mentioned + +| Domain | Best Practice | +|--------|---------------| +| Infrastructure Monitoring | AWS CloudWatch as data source in Grafana | +| Security | Cloud Application WAF management, IP whitelist to tenant level, Security Scanning | +| Availability | Service Availability Check (APM/BPM, New Relic, AWS CloudWatch Synthetic, Health Page) | +| Uptime | SLA 99.9% vs 99.99% ([uptime.is](https://uptime.is/)) | +| Alerting | Grafana Alerting with different severity levels | +| Change Management | Planned Change vs Emergency Change | + +## Key Insights + +1. **Cloud Service Delivery is a Bridge**: It connects raw IaaS/PaaS/SaaS capabilities to the reliable, secure, performant services that end users actually consume. + +2. **Multi-Disciplinary Team Required**: Effective cloud service delivery requires diverse roles — infrastructure engineers, DevOps/SRE, security specialists, support engineers, and FinOps. + +3. **12 Functional Domains**: From provisioning to disaster recovery, cloud service delivery spans the entire service lifecycle. + +4. **Monitoring is Foundational**: 24/7 monitoring with SLA/SLO tracking and proactive alerting (Grafana) is essential. + +5. **Security is Layered**: WAF, IP whitelisting, security scanning, and compliance (GDPR, HIPAA, PCI-DSS) must be integrated throughout. + +6. **Cost Awareness**: FinOps practices — eliminating waste, right-sizing, reserved instances — are critical for cloud ROI. + +7. **Maturity Model**: Organizations should assess their cloud DevOps maturity and progress systematically. + +## Connections to Other Sources + +- Related to [[Cloud Operating Model]] — strategies and best practices for cloud operations +- Related to [[Cloud Maturity Model]] — 5 maturity levels for cloud adoption +- Related to [[DevOps Maturity Model]] — from traditional IT to advanced DevOps +- Related to [[FinOps]] practices in cloud cost optimization +- Related to [[ITSM]] frameworks for service management + +## Metadata + +- **Author**: shenwei +- **Source File**: raw/Cloud & DevOps/What I know about Cloud Service Delivery 1.md +- **Created**: +- **Tags**: Cloud, DevOps, IT Operations, Cloud Infrastructure