YASSERRMD · YASSERRMD · Jun 9, 2026 · Jun 9, 2026 · Jun 9, 2026
diff --git a/docs/architecture.md b/docs/architecture.md
@@ -1,5 +1,7 @@
 # ClawForge Architecture
 
+![ClawForge control-plane architecture](assets/architecture.png)
+
 ClawForge has two layers:
 
 1. **Agent runtime** — the existing Rust workspace that *runs* agents (gateway,

diff --git a/docs/assets/enterprise-integrations.png b/docs/assets/enterprise-integrations.png
diff --git a/docs/assets/governance.png b/docs/assets/governance.png
diff --git a/docs/assets/government-compliance.png b/docs/assets/government-compliance.png
diff --git a/docs/assets/marketplace.png b/docs/assets/marketplace.png
diff --git a/docs/assets/mcp-governance.png b/docs/assets/mcp-governance.png
diff --git a/docs/assets/observability.png b/docs/assets/observability.png
diff --git a/docs/assets/positioning.png b/docs/assets/positioning.png
diff --git a/docs/assets/registry.png b/docs/assets/registry.png
diff --git a/docs/assets/security-gateway.png b/docs/assets/security-gateway.png
diff --git a/docs/assets/use-cases.png b/docs/assets/use-cases.png
diff --git a/docs/enterprise-integrations.md b/docs/enterprise-integrations.md
@@ -1,5 +1,7 @@
 # Enterprise Integrations
 
+![Enterprise Integrations](assets/enterprise-integrations.png)
+
 ClawForge governs *connections* to enterprise and government systems. The
 integration registry (`clawforge_controlplane::integrations`) tracks every
 connector, who owns it, what it is allowed to do, where its credentials live,

diff --git a/docs/governance.md b/docs/governance.md
@@ -1,5 +1,7 @@
 # Governance Engine
 
+![Governance Engine](assets/governance.png)
+
 The Governance Engine (`clawforge_controlplane::governance`) is the approval
 workflow that decides whether an agent, tool, MCP server, or model is allowed to
 be used. It is the **ServiceNow** layer of the control plane: a human approval

diff --git a/docs/government-compliance.md b/docs/government-compliance.md
@@ -1,5 +1,7 @@
 # Government Compliance Pack
 
+![Government Compliance](assets/government-compliance.png)
+
 The compliance pack (`clawforge_controlplane::compliance`) gives government and
 regulated deployments the controls and evidence to operate agents responsibly:
 PII classification, retention, multi-party approval, audit evidence,

diff --git a/docs/marketplace.md b/docs/marketplace.md
@@ -1,5 +1,7 @@
 # Agent Marketplace
 
+![Agent Marketplace](assets/marketplace.png)
+
 The marketplace (`clawforge_controlplane::marketplace`) is a **verified, internal
 catalogue of reusable agent templates**. Teams publish proven agent blueprints;
 other teams install them as governed, registry-tracked agents — without

diff --git a/docs/mcp-governance.md b/docs/mcp-governance.md
@@ -1,5 +1,7 @@
 # MCP Governance
 
+![MCP Governance](assets/mcp-governance.png)
+
 The MCP registry (`clawforge_controlplane::mcp`) governs the Model Context
 Protocol servers an organisation exposes to its agents — the same discipline the
 agent registry applies to agents. The Security Gateway consults agent

diff --git a/docs/observability.md b/docs/observability.md
@@ -1,5 +1,7 @@
 # Observability
 
+![Observability](assets/observability.png)
+
 The observability layer (`clawforge_controlplane::observability`) is the
 **Splunk** of the control plane. Agents emit append-only `ExecutionEvent`s; the
 dashboard `AgentMetrics` summary is computed on demand from those events, so the

diff --git a/docs/product-positioning.md b/docs/product-positioning.md
@@ -1,5 +1,7 @@
 # ClawForge — Product Positioning
 
+![ClawForge product positioning](assets/positioning.png)
+
 ## One-line
 
 **ClawForge is the enterprise & government control plane for AI agents:

diff --git a/docs/registry.md b/docs/registry.md
@@ -1,5 +1,7 @@
 # Agent Registry
 
+![Agent Registry](assets/registry.png)
+
 The Agent Registry (`clawforge_controlplane::registry`) is the single source of
 truth for every agent an organisation runs. Governance, the security gateway,
 and observability all key off the records stored here.

diff --git a/docs/security-gateway.md b/docs/security-gateway.md
@@ -1,5 +1,7 @@
 # Security Gateway
 
+![Security Gateway](assets/security-gateway.png)
+
 The Security Gateway (`clawforge_controlplane::gateway`) is the enforcement
 point: **every agent action is checked before execution**. It is deny-by-reason
 — an action is allowed only if no check objects.

diff --git a/docs/use-cases.md b/docs/use-cases.md
@@ -1,5 +1,7 @@
 # Use Cases
 
+![Governed agent lifecycle](assets/use-cases.png)
+
 How the control-plane modules combine into end-to-end workflows.
 
 ## The general flow