Replace content with fixed, deduplicated architecture.

.gitignore

@@ -7,4 +7,5 @@ resources/
 
 # OS files
 .DS_Store
-
+GIT_INSTRUCTIONS.md
+PR_DESCRIPTION.md

GIT_INSTRUCTIONS.md

@@ -0,0 +1,43 @@
+# How to apply this content update
+
+## Prerequisites
+- Close PR #7 (this supersedes it)
+- You have push access to dcm-project/dcm-project.github.io
+
+## Steps
+
+```bash
+# 1. Clone the repo
+git clone git@github.com:dcm-project/dcm-project.github.io.git
+cd dcm-project.github.io
+
+# 2. Create branch
+git checkout -b content-update
+
+# 3. Remove old content (preserve everything else)
+rm -rf content/ static/
+git add -A
+git commit -m "Remove old content for replacement"
+
+# 4. Copy new content from the package
+cp -r /path/to/website-content/content .
+cp -r /path/to/website-content/static .
+
+# 5. Do NOT commit PR_DESCRIPTION.md or GIT_INSTRUCTIONS.md
+# (they're for your reference only)
+
+# 6. Add and commit
+git add -A
+git commit -m "Update content: fixed, deduplicated architecture (55 data model docs, 15 specs, 4 OpenAPI)
+
+Addresses all PR #7 review comments:
+- Eliminated duplicate data-model directories
+- Fixed all broken cross-references
+- Removed 116 duplicate files
+- Updated provider count (12), policy count (8), classification enum (8)
+- Synced all OpenAPI YAMLs with canonical schemas"
+
+# 7. Push and open PR
+git push origin content-update
+# Use PR_DESCRIPTION.md as the PR body
+```

PR_DESCRIPTION.md

@@ -0,0 +1,47 @@
+# Replace content with fixed, deduplicated architecture
+
+**Closes PR #7** — this PR replaces the content from PR #7 with the complete, fixed architecture documentation. All review comments from PR #7 are addressed:
+
+## Issues fixed from PR #7
+
+- **@jenniferubah, @gabriel-farache:** Duplicate `data-model/` and `architecture/data-model/` directories → **eliminated**. Only `architecture/data-model/` exists now (55 docs with number prefixes).
+- **@gabriel-farache:** Broken links to foundations, provider-contract, policy-contract, capabilities matrix → **all fixed**. Zero broken cross-references verified.
+- **@gabriel-farache:** "links broken, I think all links should be reviewed" → **done**. Full automated cross-reference scan, zero broken links.
+- **@machacekondra:** Slug duplicates (e.g., `foundations.md` duplicating `00-foundations.md`) → **removed**. 53 slug duplicates eliminated.
+- **@machacekondra:** K8s operator SDK imperative vs declarative concern → addressed in updated `dcm-operator-sdk-api.md`
+- **@pkliczewski:** Accreditation flow diagrams, data_classification ownership, GitOps handling → all clarified in updated docs
+
+## What changed vs PR #7
+
+- 116 duplicate files removed (55 flat data-model copy + 53 slug dupes + 8 spec slug dupes)
+- Provider count: 11 → 12 (ITSM Provider added)
+- Policy count: 7 → 8 (ITSM Action added)
+- data_classification enum: 5 → 8 values (phi, pci, classified added)
+- All OpenAPI YAMLs synced with canonical schemas
+- Capabilities Matrix deduplicated (6 duplicate summary tables removed)
+- All Discussion Topics marked Resolved with cross-references
+
+## Content structure
+
+```
+content/
+├── _index.md
+└── docs/
+    ├── architecture/
+    │   ├── data-model/            ← 55 docs + _index.md (SINGLE location)
+    │   └── specifications/        ← 15 specs + 4 OpenAPI YAMLs + _index.md
+    ├── capabilities-matrix.md
+    ├── DISCUSSION-TOPICS.md
+    ├── taxonomy.md
+    ├── project-overview.md
+    ├── enhancements/
+    ├── implementations/
+    └── schemas/
+static/
+└── capabilities/
+    └── DCM-Capabilities-Matrix.csv
+```
+
+## How to apply
+
+This PR only touches `content/` and `static/`. No changes to `.github/workflows/`, `hugo.yaml`, `go.mod`, `go.sum`, `Makefile`, `assets/`, or `layouts/`.

content/_index.md

@@ -3,66 +3,53 @@ title: DCM Project
 toc: false
 ---
 
-<div class="hx-mt-6"></div>
+# Data Center Management
 
-{{< hextra/hero-headline >}}
-  Data Center Management
-{{< /hextra/hero-headline >}}
+**Hyperscaler-like cloud experience for enterprise on-premises and sovereign cloud infrastructure.**
 
-<div class="hx-mt-6"></div>
+DCM is an open-source governing framework that gives enterprise IT organizations the operational 
+model and self-service capabilities of a public cloud provider — on infrastructure they own and control.
 
-{{< hextra/hero-subtitle >}}
-  Hyperscaler-like cloud experience for&nbsp;<br class="sm:hx-block hx-hidden" />enterprise on-premises and sovereign cloud infrastructure
-{{< /hextra/hero-subtitle >}}
+{{< button href="/docs/project-overview" >}}What is DCM?{{< /button >}}
+{{< button href="/docs" >}}Documentation{{< /button >}}
+{{< button href="/docs/implementations" >}}Implementations{{< /button >}}
+{{< button href="https://github.com/dcm-project" >}}GitHub{{< /button >}}
 
-<div class="hx-mt-6"></div>
-
-{{< hextra/hero-button text="Get Started" link="docs" >}}
-{{< hextra/hero-button text="View on GitHub" link="https://github.com/dcm-project" >}}
-
-<div class="hx-mt-6"></div>
+---
 
-## About DCM
+## The Problem DCM Solves
 
-The Data Center Management (DCM) project provides a hyperscaler-like cloud experience for enterprise on-premises and sovereign cloud infrastructure. DCM is an **API-first, technology-agnostic framework** that relies on a declarative data model where the desired state of infrastructure is defined as code.
+Enterprise on-premises infrastructure is managed by dozens of disconnected tools and manual 
+processes. A single VM can take weeks across five teams. No one has a trustworthy answer to: 
+*what exists, what was requested, what was provisioned, and does current state match intended state?*
 
-The overarching goal is to define the configuration of an entire data center in version-controlled code, enabling rapid deployment and full environment recovery.
+DCM establishes a unified, declarative single source of truth for all infrastructure state 
+and connects it to a policy-driven control plane that governs every lifecycle operation.
 
-<div class="hx-mt-12"></div>
+## Three Foundational Abstractions
 
-## Core Principles
+{{< cards >}}
+  {{< card title="Data" icon="database" subtitle="Every artifact with a UUID, lifecycle state, and field-level provenance. Four states: Intent · Requested · Realized · Discovered." >}}
+  {{< card title="Provider" icon="plug" subtitle="11 typed provider contracts. Service, Information, Storage, Meta, Credential, Auth, Policy, Notification, Message Bus, ITSM, Peer DCM." >}}
+  {{< card title="Policy" icon="shield-check" subtitle="7 typed policy schemas. GateKeeper · Validation · Transformation · Orchestration Flow · Recovery · Governance Matrix · Lifecycle." >}}
+{{< /cards >}}
 
-{{< hextra/feature-grid >}}
-  {{< hextra/feature-card
-    title="🔌 API-First Design"
-    subtitle="Technology-agnostic framework built on modern API principles for maximum flexibility."
-    style="background: radial-gradient(ellipse at 50% 80%,rgba(194,97,254,0.15),hsla(0,0%,100%,0));"
-  >}}
-  {{< hextra/feature-card
-    title="☁️ Cloud-Native Approach"
-    subtitle="Moving away from monolithic management toward distributed, cloud-native principles."
-    style="background: radial-gradient(ellipse at 50% 80%,rgba(62,151,255,0.15),hsla(0,0%,100%,0));"
-  >}}
-  {{< hextra/feature-card
-    title="📚 Service Catalog"
-    subtitle="Comprehensive catalog system for managing services and infrastructure offerings."
-  >}}
-  {{< hextra/feature-card
-    title="⚖️ Rules Engine"
-    subtitle="Built-in governance and policy enforcement through a flexible rules engine."
-  >}}
-{{< /hextra/feature-grid >}}
+## Who Benefits
 
-<div class="hx-mt-16"></div>
+{{< cards >}}
+  {{< card title="Application Teams" icon="users" subtitle="Self-service catalog. Request infrastructure. Receive provisioned resources. No tickets, no manual coordination." >}}
+  {{< card title="Platform Engineers" icon="cog" subtitle="Single control plane. Policy-governed standards. Automatic drift detection. Consistency is structural." >}}
+  {{< card title="Security & Compliance" icon="lock-closed" subtitle="Policy-as-code tested before activation. Tamper-evident audit trail. Continuous accreditation monitoring." >}}
+  {{< card title="Regulated Industries" icon="building-library" subtitle="FedRAMP · CMMC · HIPAA · SOC 2 · ISO 27001 · DoD IL2–IL6. Compliance by construction." >}}
+{{< /cards >}}
 
 ---
 
-<div class="hx-mt-16"></div>
-
-## Explore More
+## Explore
 
 {{< cards >}}
-  {{< card link="docs" title="Documentation" icon="book-open" subtitle="Guides, tutorials, and technical documentation" >}}
-  {{< card link="docs/enhancements" title="Enhancements" icon="light-bulb" subtitle="Enhancement proposals documenting new features and changes" >}}
-  {{< card link="blog" title="Blog & Updates" icon="newspaper" subtitle="Latest news, releases, and articles" >}}
+  {{< card link="docs/project-overview" title="Project Overview" icon="information-circle" subtitle="What DCM is, what it does, who it benefits, where it operates." >}}
+  {{< card link="docs/architecture" title="Architecture" icon="template" subtitle="55 data model docs · 15 specs · 299 capabilities across 38 domains." >}}
+  {{< card link="docs/implementations" title="Implementations" icon="rocket-launch" subtitle="Reference implementations. Example #1: Summit 2026 demo on OpenShift." >}}
+  {{< card link="https://github.com/dcm-project" title="GitHub" icon="code-bracket" subtitle="Source, issues, and contributions." >}}
 {{< /cards >}}

content/docs/AI-ONBOARDING.md

@@ -0,0 +1,107 @@
+# Using the DCM AI Prompt for Architecture Exploration
+
+**Purpose:** The DCM AI prompt (`DCM-AI-PROMPT.md`) is a 5,772-line comprehensive knowledge base covering every architectural decision, capability, data structure, and cross-reference in DCM. When loaded into Claude or another capable LLM, it enables conversational exploration of the architecture — faster than reading documentation.
+
+---
+
+## How to Use It
+
+### Option 1: Claude.ai (Recommended)
+
+1. Go to [claude.ai](https://claude.ai)
+2. Start a new conversation
+3. Attach `DCM-AI-PROMPT.md` as a file (drag and drop, or use the attachment button)
+4. Ask your question
+
+The prompt stays active for the entire conversation. You can ask follow-up questions without re-uploading.
+
+### Option 2: Claude Projects
+
+1. Create a Project in Claude
+2. Add `DCM-AI-PROMPT.md` to the Project's knowledge base
+3. Every conversation in that Project automatically has the full architecture context
+
+This is the best option for ongoing use — the prompt is always available without re-uploading.
+
+### Option 3: Other LLMs
+
+The prompt works with any LLM that supports large context windows (128K+ tokens). Upload `DCM-AI-PROMPT.md` as context. The prompt is plain Markdown with no tool-specific formatting.
+
+---
+
+## Example Questions
+
+### Understanding a concept
+> "How does the override model work?"  
+> → 2-paragraph answer explaining the 5 mechanisms with severity ordering
+
+> "What's the difference between Internal and External policy evaluation?"  
+> → Comparison of the two modes with when to use each
+
+> "What happens when a sovereignty policy blocks a request?"  
+> → Full flow: POLICY_BLOCKED state, consumer guidance, resolution options
+
+### Finding specific details
+> "What are the 5 provider types and when would I use each?"  
+> → Table with type, capability, data direction, and example
+
+> "What SQL tables exist and what's in each one?"  
+> → Full schema overview with 18 tables, their purposes, and RLS details
+
+> "What events does the system emit during a VM provision?"  
+> → Ordered list of events with payloads from intent through realization
+
+### Implementation guidance
+> "I'm building a new service provider. What endpoints do I need to implement?"  
+> → Provider contract requirements by level (Level 1: basic, Level 2: discovery, Level 3: full)
+
+> "How do I write a GateKeeper policy that blocks VMs over 16 CPUs for a specific tenant?"  
+> → Example Rego policy with match conditions, output schema, and test cases
+
+> "How does the three-tier app example work end to end?"  
+> → Full walkthrough with YAML payloads, dependency resolution, and binding field injection
+
+### Cross-cutting questions
+> "Does the architecture cover [specific capability] from PR #50?"  
+> → Yes/no with specific doc references and capability IDs
+
+> "What would change if we added a new provider type?"  
+> → Schema migration needed, contract extension points, capabilities to declare
+
+---
+
+## What the Prompt Covers
+
+The prompt contains 125 sections organized into these areas:
+
+| Area | Sections | What's in it |
+|------|----------|-------------|
+| Foundational Abstractions | 0-3 | Data, Provider, Policy — the three pillars |
+| Data Model | 4-14 | Four states, layers, entities, relationships, groups |
+| Control Plane | 15-16 | 9 services, pipeline flow, request routing |
+| Providers | 16-22 | 6 types, contracts, naturalization, discovery |
+| Policy | 17, 23-28 | 8 types, evaluation model, overrides, templates |
+| Audit & Security | 29-35 | Merkle tree, stage signing, governance matrix, zero trust |
+| API Specifications | 36-40 | Consumer API (74 paths), Admin API (61 paths), Provider Callback |
+| Capabilities | 41 | 331 capabilities across 39 domains |
+| SQL Schema | 42 | 18 tables with column definitions |
+| Event Catalog | 43 | 109 events across 23 domains |
+| Implementation | 44-50 | Deployment, profiles, test framework |
+
+---
+
+## Tips
+
+- **Be specific.** "How does policy evaluation work?" gets a better answer than "Tell me about policies."
+- **Ask for examples.** "Show me the YAML payload at each stage of a VM provision" gets concrete data structures.
+- **Ask for cross-references.** "Which docs should I read for provider development?" gets a prioritized list.
+- **Ask for comparisons.** "How does this differ from Crossplane / Kessel / KRO?" gets an informed comparison.
+- **Ask implementation questions.** "What Go interfaces would a new service provider need?" gets code-level guidance.
+
+---
+
+## Where to Find the Prompt
+
+- **DCM repo:** `architecture/ai/DCM-AI-PROMPT.md`
+- **Website:** Published at `dcm-project.github.io/docs/architecture/ai/DCM-AI-PROMPT/`
+- **Examples repo:** Copied into `docs/DCM-AI-PROMPT.md` for reference