feat: complete Day 1–5 plugin + all essential docs updated

Skills (6 total, 30 commands):
- Add skills/day5-strategy/ — GenAI/RAG, data products, modernization, operating model
- Add skills/skill-orchestrator/ — meta-skill: discover-client, assess-maturity,
  orchestrate-engagement, translate-for-stakeholder, estimate-effort

Knowledge Base (6 files):
- Add knowledge-base/genai-data-patterns.md (RAG, vector store, LLM safety, PHI de-ID)
- Add knowledge-base/financial-services-patterns.md (Basel, AML, BCBS 239, payments)
- Add knowledge-base/manufacturing-patterns.md (IIoT, digital twin, Industry 4.0)
- Update knowledge-base/README.md to reflect all 6 actual KB files

Examples:
- Add newlife-hospital-day5-solution.html (9-tab: GenAI, data products, modernization,
  operating model, $127M NPV business case, final blueprint)
- Update examples/newlife-hospital/README.md — all Days 1–5 covered

Templates + Test Scenarios:
- Add templates/ (SoW, board deck, project charter, engagement brief, data architecture brief)
- Add test-scenarios/plug-and-play-test-scenarios.md

Docs:
- README.md: badge 5→6, roadmap all Active, repo structure corrected,
  portfolio entries for Days 3–5, case studies table expanded to all 5 days
- ARCHITECTURE.md: fix folder names (day3-cloud-data, day4-analytics, day5-strategy),
  add skill-orchestrator row, update command counts
- Add RESTRUCTURE-PLAN.md (public/private repo split strategy)

skills/index.json: 6 skills / 30 commands

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: wjlgatech

README.md

@@ -9,7 +9,7 @@
 Community-built skills that turn Claude into a senior data architect — for modeling, platforms, cloud, AI, and modernization.
 
 [![CI](https://github.com/wjlgatech/data-architecture/actions/workflows/ci.yml/badge.svg)](https://github.com/wjlgatech/data-architecture/actions/workflows/ci.yml)
-[![Skills](https://img.shields.io/badge/skills-5%2F25-7b2fff?logo=anthropic)](https://github.com/wjlgatech/data-architecture/tree/main/skills)
+[![Skills](https://img.shields.io/badge/skills-6%2F25-7b2fff?logo=anthropic)](https://github.com/wjlgatech/data-architecture/tree/main/skills)
 [![Contributors](https://img.shields.io/github/contributors/wjlgatech/data-architecture?color=orange)](https://github.com/wjlgatech/data-architecture/graphs/contributors)
 [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen?logo=github)](CONTRIBUTING.md)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -70,41 +70,51 @@ Once installed, Claude responds to built-in commands:
 
 ## 🗺️ Roadmap
 
-| Day | Module | Skills | Status |
-|-----|--------|--------|--------|
+| Day | Module | Commands | Status |
+|-----|--------|----------|--------|
+| 0️⃣ | **Skill Orchestrator** | `discover-client`, `assess-maturity`, `orchestrate-engagement`, `translate-for-stakeholder`, `estimate-effort` | ✅ **Active** |
 | 1️⃣ | **Intro to Data Architecture & Modeling** | `design-model`, `choose-architecture`, `kpi-catalog`, `audit-vault`, `dimension-map` | ✅ **Active** |
-| 2️⃣ | **New Data Management** | `data-quality`, `master-data`, `governance`, `metadata-catalog` | 🔨 Building |
-| 3️⃣ | **Cloud Data & Technology** | `platform-selector`, `snowflake-patterns`, `databricks-patterns`, `lakehouse-design` | 📋 Planned |
-| 4️⃣ | **Data Intelligence & AI** | `ml-feature-store`, `rag-architecture`, `ai-governance`, `model-ops` | 📋 Planned |
-| 5️⃣ | **Data Modernization** | `migration-planner`, `legacy-assessment`, `modernization-roadmap` | 📋 Planned |
+| 2️⃣ | **Data Management** | `design-mdm`, `check-data-quality`, `governance-check`, `lifecycle-plan`, `security-review` | ✅ **Active** |
+| 3️⃣ | **Cloud Data & Technology** | `design-cloud-platform`, `design-data-platform`, `design-ingestion-pipeline`, `design-api-layer`, `multi-region-plan` | ✅ **Active** |
+| 4️⃣ | **Data Intelligence, Analytics & AI** | `analyze-big-data`, `design-nlp-pipeline`, `build-mlops-pipeline`, `design-realtime-intelligence`, `responsible-ai-review` | ✅ **Active** |
+| 5️⃣ | **Data Strategy & GenAI** | `design-genai-architecture`, `data-strategy-alignment`, `build-data-product`, `modernization-roadmap`, `operating-model-design` | ✅ **Active** |
 
-**We build one module per day. PRs are merged daily. Join and ship something.**
+**6 skills · 30 commands · full 5-day curriculum complete. PRs welcome to extend any module.**
 
 ---
 
 ## 📁 Repository Structure
 
 ```
 data-architecture/
-├── skills/                     # 🧠 Claude skills (one folder = one skill module)
-│   ├── day1-modeling/          # Data modeling: Vault, Star, 3NF, AUDM
-│   │   ├── SKILL.md            # Main Claude instructions (paste into system prompt)
-│   │   ├── metadata.json       # Skill metadata, version, tags
-│   │   ├── commands/           # Slash command definitions
-│   │   └── references/         # Deep reference material
-│   ├── day2-data-management/   # Placeholder — contribute here!
-│   ├── day3-cloud/             # Placeholder — contribute here!
-│   ├── day4-ai-analytics/      # Placeholder — contribute here!
-│   └── day5-modernization/     # Placeholder — contribute here!
+├── skills/                       # 🧠 Claude skills (one folder = one skill module)
+│   ├── skill-orchestrator/       # Meta-skill: client intake, maturity, engagement orchestration
+│   ├── day1-modeling/            # Data modeling: Vault, Star, 3NF, AUDM
+│   │   ├── SKILL.md              # Main Claude instructions (paste into system prompt)
+│   │   ├── metadata.json         # Skill metadata, version, tags
+│   │   ├── commands/             # Slash command definitions
+│   │   └── references/           # Deep reference material
+│   ├── day2-data-management/     # MDM, Data Quality, Governance, Lifecycle, Security
+│   ├── day3-cloud-data/          # Cloud platforms, Lakehouse, FHIR, multi-region
+│   ├── day4-analytics/           # Big data, clinical NLP, MLOps, real-time, responsible AI
+│   ├── day5-strategy/            # GenAI/RAG, data products, modernization, operating model
+│   └── index.json                # Machine-readable skill registry
 │
-├── schemas/                    # 🔒 JSON schemas for CI validation
-├── templates/                  # 🧩 Copy-paste starters for new skills
-├── examples/                   # 📖 Real case studies
-│   └── newlife-pharmacy/       # Pharma supply chain (Day 1 case study)
-├── docs/                       # 📚 Architecture decisions, specs
-├── tests/                      # ✅ Validation scripts (run by CI)
-├── scripts/                    # 🛠️ CLI tooling
-└── .github/                    # ⚙️ Workflows, issue/PR templates
+├── knowledge-base/               # 📚 Cross-skill shared domain knowledge
+│   ├── healthcare-standards.md   # HL7 FHIR, ICD-10, LOINC, SNOMED
+│   ├── cloud-platform-patterns.md
+│   ├── analytics-patterns.md
+│   └── genai-data-patterns.md
+│
+├── schemas/                      # 🔒 JSON schemas for CI validation
+├── templates/                    # 🧩 Copy-paste starters for new skills
+├── examples/                     # 📖 Real case studies (interactive HTML)
+│   ├── newlife-pharmacy/         # Pharma supply chain — Day 1
+│   └── newlife-hospital/         # Healthcare HIS — Days 2–5
+├── docs/                         # 📄 Architecture decisions, specs
+├── tests/                        # ✅ Validation scripts (run by CI)
+├── scripts/                      # 🛠️ CLI tooling
+└── .github/                      # ⚙️ Workflows, issue/PR templates
 ```
 
 ---
@@ -197,22 +207,75 @@ npm run validate
 
 ---
 
-### Coming Soon
+---
+
+### Day 3 · Cloud Data Platform — Azure Medallion Lakehouse
+
+> *NewLife Hospital — Multi-region healthcare data platform, FHIR R4 API, Medallion Lakehouse, 90+ countries*
+
+**One-line verdict:** Azure Medallion Lakehouse (Bronze/Silver/Gold) on Delta Lake — the only pattern that handles FHIR R4 streaming ingestion, multi-jurisdictional data residency, and clinical AI feature serving from a single coherent architecture.
+
+| Dimension | Decision |
+|---|---|
+| Platform | **Azure** — ADF, Event Hub, Databricks, Delta Lake, Synapse, ADLS Gen2 |
+| Architecture | Medallion Lakehouse — Bronze (raw FHIR) → Silver (cleaned) → Gold (marts) |
+| APIs | FHIR R4 with SMART on FHIR OAuth 2.0, geo-load balancing, 99.9% SLA |
+| Multi-Region | Hub-and-spoke — 5 regional nodes, data residency enforcement per GDPR/PIPL/PDPA |
+| Security | Zero Trust, Private Endpoints, Azure Purview RBAC, field-level encryption |
+| Clinical AI | Predictive sepsis, NLP discharge summaries, imaging triage — all within Medallion Gold |
+
+**[▶ Open Interactive Solution →](https://htmlpreview.github.io/?https://github.com/wjlgatech/data-architecture/blob/main/examples/newlife-hospital/newlife-hospital-day3-solution.html)**
+
+---
+
+### Day 4 · Data Intelligence, Analytics & AI
+
+> *NewLife Hospital — Clinical NLP, Medical Imaging AI, Real-time Sepsis Alerting, MLOps, $2M→$6M Year-1 ROI*
+
+**One-line verdict:** Lambda architecture for batch + streaming analytics, with a unified MLOps platform (MLflow + Databricks) that governs clinical models from FDA SaMD Class II compliance to bedside alerting in under 60 seconds.
+
+| Dimension | Decision |
+|---|---|
+| Big Data | Lambda architecture — Spark batch (Databricks) + Kafka/Event Hub streaming |
+| Clinical NLP | spaCy + Med7 + BERT-clinical pipeline: 92%+ F1 on entity extraction |
+| Imaging AI | CNN + ViT ensemble, 3-stage review workflow, FDA SaMD Class II governance |
+| Real-time | NEWS2 sepsis score — Kafka → Feature Store → model inference → alert in <60s |
+| MLOps | MLflow + AzureML: Experiment → Train → Validate → Deploy → Monitor → Retrain |
+| Responsible AI | Bias audit, GDPR Art. 22 human-in-loop, FDA SaMD classification, explainability |
+| ROI | Year 1: $2M invest → $6M return · Year 2: $4M → $16M · Year 3: $8M → $40M |
+
+**[▶ Open Interactive Solution →](https://htmlpreview.github.io/?https://github.com/wjlgatech/data-architecture/blob/main/examples/newlife-hospital/newlife-hospital-day4-solution.html)**
+
+---
+
+### Day 5 · Data Strategy, GenAI & Final Blueprint
+
+> *NewLife Hospital — RAG pipeline, Data Products, $127M NPV business case, 5-year operating model*
+
+**One-line verdict:** A GenAI Clinical Intelligence Platform built on Retrieval-Augmented Generation, with PHI de-identification gate, vector store serving 200M+ patient records, and a federated data product marketplace — all governed by a CDO-led operating model with a measurable $127M NPV over 5 years.
+
+| Dimension | Decision |
+|---|---|
+| GenAI Architecture | RAG pipeline — PHI De-ID → Chunking → Embedding → Vector Store → LLM → Audit |
+| Vector Store | Azure AI Search (hybrid dense + sparse) — HIPAA-compliant, 200M+ patient records |
+| Data Products | Federated marketplace — 12 certified products across Clinical, Ops, Finance, Research |
+| Modernization | Legacy EHR → Cloud: Assess (3I) → Lift-and-Shift → Re-platform → Re-architect |
+| Operating Model | CDO → Data Domains → Product Owners → Engineers · Hub-and-Spoke federated |
+| Business Case | $127M NPV, 287% ROI, 18-month payback — board-ready financial model |
 
-| Day | Module | Status |
-|---|---|---|
-| Day 3 | Cloud Data & Technology (Snowflake · Databricks · Azure Synapse · Lakehouse) | 🔜 Building |
-| Day 4 | Data Intelligence, Analytics & AI (ML Feature Store · RAG · AI Governance) | 📋 Planned |
-| Day 5 | Data Modernization (Legacy Assessment · Migration Playbooks · Modernization Roadmap) | 📋 Planned |
+**[▶ Open Interactive Solution →](https://htmlpreview.github.io/?https://github.com/wjlgatech/data-architecture/blob/main/examples/newlife-hospital/newlife-hospital-day5-solution.html)**
 
 ---
 
 ## 📖 Case Studies
 
-| Case Study | Domain | Skills Used | Link |
+| Case Study | Domain | Days | Link |
 |---|---|---|---|
-| NewLife Pharmacy Supply Chain | Pharmaceutical D2P | Data Vault 2.0, KPI Catalog, 30+ KPIs | [View →](examples/newlife-pharmacy/) |
-| NewLife Hospital Unified HIS | Healthcare MDM + Governance | Federated MDM, GDPR/HIPAA, Zero Trust | [View →](examples/newlife-hospital/) |
+| NewLife Pharmacy Supply Chain | Pharmaceutical D2P | Day 1 | [View →](examples/newlife-pharmacy/) |
+| NewLife Hospital — Data Management | Healthcare MDM + Governance | Day 2 | [View →](examples/newlife-hospital/) |
+| NewLife Hospital — Cloud Platform | Healthcare Lakehouse + FHIR | Day 3 | [View →](examples/newlife-hospital/) |
+| NewLife Hospital — Analytics & AI | Clinical NLP, MLOps, Sepsis AI | Day 4 | [View →](examples/newlife-hospital/) |
+| NewLife Hospital — Strategy & GenAI | RAG, Data Products, $127M NPV | Day 5 | [View →](examples/newlife-hospital/) |
 
 ---
 

RESTRUCTURE-PLAN.md

@@ -0,0 +1,198 @@
+# Repository Restructure Plan
+*Public ↔ Private Split — Data Architecture Consulting OS*
+
+---
+
+## The Strategic Logic
+
+Two repos. Two different jobs. Never merge them.
+
+```
+PUBLIC REPO (wjlgatech/data-architecture-school)
+  Job: Marketing engine + authority signal + lead generation
+  Audience: CDOs, data leaders, engineers, students
+  Content: Free curriculum, case studies, examples
+  Goal: Drive inbound — CDOs find this → follow Wu → book a call
+
+PRIVATE REPO (wjlgatech/consulting-os) ← NEW, PRIVATE
+  Job: Competitive moat + operating system of the consulting practice
+  Audience: Wu + approved collaborators only
+  Content: skill-orchestrator, industry KBs, templates, test scenarios
+  Goal: Enable 90-95% autonomous engagement delivery
+```
+
+**Why not make everything private?**
+Because the public repo is your $0 marketing budget. Every CDO who searches "FHIR data architecture" or "healthcare data lakehouse" and finds your GitHub is a warm lead. Take that away and you need to spend $50K/month on LinkedIn ads to replace it.
+
+**Why make the plugin private?**
+Because the skill-orchestrator + templates is what gives you the 80% margin advantage. If a competitor forks it, they close that gap in 3 months. Your moat is not just the technology — it's the synthesis of domain knowledge + AI automation. That's proprietary.
+
+---
+
+## Step-by-Step Restructure
+
+### Step 1: Create the Private Repo (do this first, today)
+
+```bash
+# On GitHub.com:
+# Create new repo: wjlgatech/consulting-os
+# Visibility: PRIVATE
+# Initialize with README
+
+# Clone locally, then copy the private content:
+git clone git@github.com:wjlgatech/consulting-os.git
+cd consulting-os
+
+# Copy private content from data-architecture-school:
+cp -r ../data-architecture-school/skills/ ./
+cp -r ../data-architecture-school/knowledge-base/ ./
+cp -r ../data-architecture-school/templates/ ./
+cp -r ../data-architecture-school/test-scenarios/ ./
+cp -r ../data-architecture-school/schemas/ ./
+
+git add -A
+git commit -m "chore: initial consulting OS — skill-orchestrator + KB + templates"
+git push origin main
+```
+
+### Step 2: Clean the Public Repo
+
+Remove the private IP from the public repo. Keep everything that serves as marketing.
+
+**REMOVE from public repo (data-architecture-school):**
+```
+skills/skill-orchestrator/          ← Core IP — move to private
+knowledge-base/financial-services-patterns.md  ← Industry IP
+knowledge-base/manufacturing-patterns.md       ← Industry IP
+knowledge-base/genai-data-patterns.md          ← move (healthcare-standards stays)
+templates/statement-of-work.md      ← move (engagement templates are IP)
+templates/board-deck-outline.md     ← move
+templates/project-charter.md        ← move
+templates/data-architecture-brief.md ← move
+templates/engagement-brief.md       ← move
+test-scenarios/                     ← move (reveals methodology)
+skills/index.json                   ← move (reveals plugin architecture)
+```
+
+**KEEP in public repo (data-architecture-school) — these are your marketing:**
+```
+README.md                           ← rewrite as marketing-facing (below)
+examples/newlife-hospital/          ← case study proof (anonymise if needed)
+examples/newlife-pharmacy/          ← case study proof
+skills/day1-modeling/               ← curriculum content (draws inbound)
+skills/day2-data-management/        ← curriculum content
+skills/day3-cloud-data/             ← curriculum content
+skills/day4-analytics/              ← curriculum content
+skills/day5-strategy/               ← curriculum content
+knowledge-base/healthcare-standards.md    ← authority content (public)
+knowledge-base/regulatory-compliance.md  ← authority content (public)
+docs/                               ← architecture documentation
+```
+
+### Step 3: Rewrite the Public README as a Marketing Document
+
+The current README says "Data Architecture School." Rewrite it to:
+
+```markdown
+# Data Architecture School
+**Free 5-day curriculum for data architects and CDOs**
+
+Built by [Wu] — Principal Architect, love12xfuture
+
+---
+
+## What's here
+
+5 days of open-source data architecture curriculum covering:
+- Data modeling (Data Vault 2.0, Star Schema, 3NF)
+- Data management (MDM, DQ, Governance, HIPAA)
+- Cloud data platforms (Azure Medallion Lakehouse, FHIR R4)
+- Analytics & AI (MLOps, Clinical NLP, Responsible AI)
+- Data Strategy & GenAI (RAG pipelines, Data Products, Operating Model)
+
+Each day includes: frameworks, patterns, decision tools, and a real-world case study
+(NewLife Hospital — 300 hospitals, 90 countries, $127M NPV business case).
+
+---
+
+## Working with your own data architecture challenges?
+
+If you're a CDO or health system CIO dealing with:
+- Fragmented EHR data across multiple systems
+- Regulatory pressure (HIPAA, state mandates) with no data governance
+- Board pressure to "do something with AI" but no clean data foundation
+- A failed data platform project that needs rescuing
+
+→ [Book a 30-minute discovery call](https://calendly.com/[YOUR_LINK])
+
+---
+
+## Follow the work
+
+YouTube: love12xfuture
+LinkedIn: [Wu's profile]
+```
+
+### Step 4: Add .gitignore to Private Repo
+
+```gitignore
+# consulting-os private repo .gitignore
+.env
+client-engagements/        # Never commit client data
+*.client.md                # Client-specific files
+engagements/               # Active engagement working files
+```
+
+### Step 5: Access Control on Private Repo
+
+GitHub settings for `consulting-os`:
+- Default branch: `main`
+- Branch protection: require PR review before merging (even as solo founder — discipline matters)
+- Collaborator access: invite only via Settings → Collaborators
+- Secret scanning: enabled
+- Dependency review: enabled
+
+---
+
+## Future Structure (Private Repo)
+
+As the practice grows, the private repo evolves:
+
+```
+consulting-os/
+├── skills/                    ← plugin skills (orchestrator + Day 1-5)
+├── knowledge-base/            ← industry KBs
+├── templates/                 ← engagement deliverable templates
+├── test-scenarios/            ← validation suite
+├── schemas/                   ← skill schema validation
+├── engagements/               ← NEVER COMMIT (gitignored)
+│   ├── client-a/              ← working files per client
+│   └── client-b/
+├── playbooks/                 ← (future) per-industry playbooks
+│   ├── healthcare/
+│   ├── financial-services/
+│   └── manufacturing/
+└── CLAUDE.md                  ← Wu memory file (ops context)
+```
+
+---
+
+## Intellectual Property Protection (Beyond GitHub)
+
+1. **Copyright notice:** Add to all private repo files:
+   `© 2026 [Wu / Firm Name]. All rights reserved. Confidential and proprietary.`
+
+2. **Terms of engagement:** SoW template already includes IP ownership clause.
+   Add: "All methodology, frameworks, templates, and tools used in delivery remain
+   the intellectual property of [Firm]. Client receives license to use deliverables only."
+
+3. **Collaborator agreements:** Before giving any collaborator access to private repo,
+   sign an NDA + IP assignment agreement. Template available on request.
+
+4. **Consider a trademark:** "skill-orchestrator" as a brand name for the consulting OS.
+   Low cost ($350 USPTO filing); protects the brand as you grow.
+
+---
+
+*Restructure plan — Data Architecture Consulting OS*
+*Version 1.0 — 2026-03-18*