docs: reorganize documentation by persona

Rename documentation directories to align with user personas:
- docs/architecture → docs/contributor
- docs/integration → docs/integrator
- docs/user-guide → docs/user
- docs/demos → examples/demos

Update all internal links across README.md, OVERVIEW.md, DEVELOPMENT.md,
CONTRIBUTING.md, RELEASING.md, copilot-instructions.md, and demo files.

This follows CNCF best practices for documentation organization,
making it easier for users to find relevant docs based on their role.

Signed-off-by: Mark Chmarny <mchmarny@nvidia.com>

Author: mchmarny

.github/copilot-instructions.md

@@ -124,7 +124,7 @@ NVIDIA Eidos provides validated GPU-accelerated Kubernetes configurations throug
    make test
    ```
 
-→ See [Bundler Development Guide](docs/architecture/component.md) for full details
+→ See [Bundler Development Guide](docs/contributor/component.md) for full details
 
 ### I Need To: Add New API Endpoint
 
@@ -327,9 +327,9 @@ eidos bundle -r recipe.yaml -b gpu-operator,network-operator \
 - **[Contributing Guide](../CONTRIBUTING.md)** – Design principles, development setup, PR process
 - **[Development Guide](../DEVELOPMENT.md)** – Local development, Make targets, Tilt/Kind setup
 - **[Release Process](../RELEASING.md)** – Maintainer guide for releases, verification, hotfixes
-- **[Architecture Overview](../docs/architecture/README.md)** – System design
-- **[Bundler Development](../docs/architecture/component.md)** – Create new bundlers
-- **[API Reference](../docs/integration/api-reference.md)** – REST API endpoints
+- **[Architecture Overview](../docs/contributor/README.md)** – System design
+- **[Bundler Development](../docs/contributor/component.md)** – Create new bundlers
+- **[API Reference](../docs/integrator/api-reference.md)** – REST API endpoints
 - **[GitHub Actions README](actions/README.md)** – CI/CD architecture
 - **[API Specification](../api/eidos/v1/server.yaml)** – OpenAPI spec
 - **[.versions.yaml](../.versions.yaml)** – Tool versions (single source of truth)

CONTRIBUTING.md

@@ -297,6 +297,6 @@ Signed-off-by: Your Name <your@email.com>
 - [DEVELOPMENT.md](DEVELOPMENT.md) - Development setup, architecture, and tooling
 - [README.md](README.md) - Project overview and quick start
 - [docs/OVERVIEW.md](docs/OVERVIEW.md) - System overview and glossary
-- [docs/architecture/README.md](docs/architecture/README.md) - Architecture documentation
+- [docs/contributor/README.md](docs/contributor/README.md) - Architecture documentation
 
 Thank you for contributing to NVIDIA Eidos! Your efforts help improve GPU-accelerated infrastructure for everyone.

DEVELOPMENT.md

@@ -261,7 +261,7 @@ eidos/
 
 Business logic lives in `pkg/*` packages. The `pkg/cli` and `pkg/api` packages handle user interaction only, delegating to functional packages so both CLI and API can share the same logic.
 
-For detailed architecture documentation, see [docs/architecture/README.md](docs/architecture/README.md).
+For detailed architecture documentation, see [docs/contributor/README.md](docs/contributor/README.md).
 
 ## Development Workflow
 
@@ -651,10 +651,10 @@ make dev-reset
 ## Additional Resources
 
 ### Project Documentation
-- [Architecture Overview](docs/architecture/README.md) - System design and components
-- [CLI Architecture](docs/architecture/cli.md) - CLI command structure
-- [Data Architecture](docs/architecture/data.md) - Recipe data model
-- [Bundler Development](docs/architecture/component.md) - Creating new bundlers
+- [Architecture Overview](docs/contributor/README.md) - System design and components
+- [CLI Architecture](docs/contributor/cli.md) - CLI command structure
+- [Data Architecture](docs/contributor/data.md) - Recipe data model
+- [Bundler Development](docs/contributor/component.md) - Creating new bundlers
 
 ### External Resources
 - [Go Documentation](https://golang.org/doc/)

Makefile

@@ -232,8 +232,8 @@ cleanup: ## Cleans up Eidos Kubernetes resources (requires kubectl)
 .PHONY: demos
 demos: ## Creates demo GIFs using VHS tool (requires: brew install vhs)
 	@command -v vhs >/dev/null 2>&1 || (echo "Error: vhs is not installed. Install: brew install vhs" && exit 1)
-	vhs docs/demos/videos/cli.tape -o docs/demos/videos/cli.gif
-	vhs docs/demos/videos/e2e.tape -o docs/demos/videos/e2e.gif
+	vhs examples/demos/videos/cli.tape -o examples/demos/videos/cli.gif
+	vhs examples/demos/videos/e2e.tape -o examples/demos/videos/e2e.gif
 
 # =============================================================================
 # Tilt Local Development

README.md

@@ -55,7 +55,7 @@ curl -sfL -H "Authorization: token $GITHUB_TOKEN" \
   https://raw.githubusercontent.com/NVIDIA/eidos/main/install | bash -s --
 ```
 
-See [Installation Guide](docs/user-guide/installation.md) for manual installation, building from source, and container images.
+See [Installation Guide](docs/user/installation.md) for manual installation, building from source, and container images.
 
 ### Quick Start
 
@@ -79,43 +79,45 @@ eidos recipe --service eks --accelerator gb200 --os ubuntu --intent training --p
 eidos bundle --recipe recipe.yaml -o ./bundles
 ```
 
-The generated `bundles/` directory contains a Helm umbrella chart ready to deploy or commit to your GitOps repository. See [CLI Reference](docs/user-guide/cli-reference.md) for more options.
+The generated `bundles/` directory contains a Helm umbrella chart ready to deploy or commit to your GitOps repository. See [CLI Reference](docs/user/cli-reference.md) for more options.
 
 ### Get Started by Use Case
 
-These use cases reflect common ways teams interact with Eidos.
+Choose the documentation path that matches how you'll use Eidos.
 
 <details>
-<summary><strong>Platform and Infrastructure Operators</strong></summary>
+<summary><strong>User</strong> – Platform and Infrastructure Operators</summary>
 
-You are responsible for deploying and operating GPU-accelerated Kubernetes clusters. 
-- **[Installation Guide](docs/user-guide/installation.md)** – Install the eidos CLI (automated script, manual, or build from source)
-- **[CLI Reference](docs/user-guide/cli-reference.md)** – Complete command reference with examples
-- **[API Reference](docs/user-guide/api-reference.md)** – Complete API reference with examples
-- **[Agent Deployment](docs/user-guide/agent-deployment.md)** – Deploy the Kubernetes agent to get automated configuration snapshots
+You deploy and operate GPU-accelerated Kubernetes clusters using validated configurations.
+
+- **[Installation Guide](docs/user/installation.md)** – Install the eidos CLI (automated script, manual, or build from source)
+- **[CLI Reference](docs/user/cli-reference.md)** – Complete command reference with examples
+- **[API Reference](docs/user/api-reference.md)** – REST API quick start
+- **[Agent Deployment](docs/user/agent-deployment.md)** – Deploy the Kubernetes agent for automated snapshots
 </details>
 
 <details>
-<summary><strong>Developers and Contributors</strong></summary>
+<summary><strong>Contributor</strong> – Developers and Maintainers</summary>
 
-You are contributing code, extending functionality, or working on Eidos internals. 
+You contribute code, extend functionality, or work on Eidos internals.
 
 - **[Contributing Guide](CONTRIBUTING.md)** – Development setup, testing, and PR process
 - **[Development Guide](DEVELOPMENT.md)** – Local development, Make targets, and tooling
-- **[Architecture Overview](docs/architecture/README.md)** – System design and components
-- **[Bundler Development](docs/architecture/component.md)** – How to create new bundlers
-- **[Data Architecture](docs/architecture/data.md)** – Recipe data model and query matching
+- **[Architecture Overview](docs/contributor/README.md)** – System design and components
+- **[Bundler Development](docs/contributor/component.md)** – How to create new bundlers
+- **[Data Architecture](docs/contributor/data.md)** – Recipe data model and query matching
 </details>
 
 <details>
-<summary><strong>Integrators and Automation Engineers</strong></summary>
+<summary><strong>Integrator</strong> – Automation and Platform Engineers</summary>
 
-You are integrating Eidos into CI/CD pipelines, GitOps workflows, or a larger product or service. 
+You integrate Eidos into CI/CD pipelines, GitOps workflows, or larger platforms.
 
-- **[API Reference](docs/integration/api-reference.md)** – REST API endpoints and usage examples
-- **[Data Flow](docs/integration/data-flow.md)** – Understanding snapshots, recipes, and bundles
-- **[Automation Guide](docs/integration/automation.md)** – CI/CD integration patterns
-- **[Kubernetes Deployment](docs/integration/kubernetes-deployment.md)** – Self-hosted API server setup
+- **[API Reference](docs/integrator/api-reference.md)** – REST API endpoints and usage examples
+- **[Data Flow](docs/integrator/data-flow.md)** – Understanding snapshots, recipes, and bundles
+- **[Automation Guide](docs/integrator/automation.md)** – CI/CD integration patterns
+- **[Kubernetes Deployment](docs/integrator/kubernetes-deployment.md)** – Self-hosted API server setup
+- **[Recipe Development](docs/integrator/recipe-development.md)** – Adding and modifying recipe metadata
 </details>
 
 ## Project Structure

RELEASING.md

@@ -174,7 +174,7 @@ curl http://localhost:8080/health
 
 ## Demo Cloud Run Deployment
 
-> **Note**: This is a **demonstration deployment** for testing and development purposes only. It is not a production service. Users should self-host the `eidosd` API server in their own infrastructure for production use. See [API Server Documentation](docs/architecture/api-server.md) for deployment guidance.
+> **Note**: This is a **demonstration deployment** for testing and development purposes only. It is not a production service. Users should self-host the `eidosd` API server in their own infrastructure for production use. See [API Server Documentation](docs/contributor/api-server.md) for deployment guidance.
 
 The `eidosd` API server demo is automatically deployed to Google Cloud Run on successful release:
 

docs/OVERVIEW.md

@@ -102,42 +102,42 @@ Eidos prioritizes trust in the software supply chain.
 
 ## Documentation
 
-### User Guide
+Documentation is organized by persona to help you find what you need quickly.
 
-| Document | Description |
-|----------|-------------|
-| [Installation](user-guide/installation.md) | Installing the `eidos` CLI |
-| [CLI Reference](user-guide/cli-reference.md) | Complete CLI command reference with examples |
-| [API Reference](user-guide/api-reference.md) | Quick start for the REST API |
-| [Agent Deployment](user-guide/agent-deployment.md) | Running the snapshot agent as a Kubernetes Job |
+### User Documentation
 
-### Architecture
+For platform operators deploying and operating GPU-accelerated Kubernetes clusters.
 
 | Document | Description |
 |----------|-------------|
-| [Architecture Overview](architecture/README.md) | System design, patterns, and deployment topologies |
-| [CLI Architecture](architecture/cli.md) | Detailed CLI implementation and workflow diagrams |
-| [API Server Architecture](architecture/api-server.md) | HTTP server design, middleware, and endpoints |
-| [Data Architecture](architecture/data.md) | Recipe metadata system, criteria matching, and inheritance |
-| [Bundler Development](architecture/component.md) | Guide for creating new bundlers |
+| [Installation](user/installation.md) | Installing the `eidos` CLI |
+| [CLI Reference](user/cli-reference.md) | Complete CLI command reference with examples |
+| [API Reference](user/api-reference.md) | Quick start for the REST API |
+| [Agent Deployment](user/agent-deployment.md) | Running the snapshot agent as a Kubernetes Job |
 
-### Integration
+### Contributor Documentation
+
+For developers contributing code, extending functionality, or working on Eidos internals.
 
 | Document | Description |
 |----------|-------------|
-| [API Reference](integration/api-reference.md) | Complete REST API specification with examples |
-| [Automation](integration/automation.md) | CI/CD integration patterns |
-| [Data Flow](integration/data-flow.md) | Understanding recipe data architecture |
-| [Kubernetes Deployment](integration/kubernetes-deployment.md) | Self-hosted API server deployment |
-| [Recipe Development](integration/recipe-development.md) | Adding and modifying recipe metadata |
+| [Architecture Overview](contributor/README.md) | System design, patterns, and deployment topologies |
+| [CLI Architecture](contributor/cli.md) | Detailed CLI implementation and workflow diagrams |
+| [API Server Architecture](contributor/api-server.md) | HTTP server design, middleware, and endpoints |
+| [Data Architecture](contributor/data.md) | Recipe metadata system, criteria matching, and inheritance |
+| [Bundler Development](contributor/component.md) | Guide for creating new bundlers |
+
+### Integrator Documentation
 
-### Demos
+For engineers integrating Eidos into CI/CD pipelines, GitOps workflows, or larger platforms.
 
 | Document | Description |
 |----------|-------------|
-| [End-to-End Demo](demos/e2e.md) | Complete workflow demonstration (snapshot → recipe → bundle) |
-| [Data Architecture Demo](demos/data.md) | Recipe metadata system walkthrough |
-| [Supply Chain Security Demo](demos/s3c.md) | Verifying SLSA attestations and SBOMs |
+| [API Reference](integrator/api-reference.md) | Complete REST API specification with examples |
+| [Automation](integrator/automation.md) | CI/CD integration patterns |
+| [Data Flow](integrator/data-flow.md) | Understanding recipe data architecture |
+| [Kubernetes Deployment](integrator/kubernetes-deployment.md) | Self-hosted API server deployment |
+| [Recipe Development](integrator/recipe-development.md) | Adding and modifying recipe metadata |
 
 ## Quick Start
 
@@ -150,7 +150,7 @@ curl -sfL -H "Authorization: token $GITHUB_TOKEN" \
   https://raw.githubusercontent.com/NVIDIA/eidos/main/install | bash -s --
 ```
 
-See [Installation Guide](docs/user-guide/installation.md) for manual installation, building from source, and container images.
+See [Installation Guide](user/installation.md) for manual installation, building from source, and container images.
 
 ### Generate Recipe