diff --git a/docs/Chapter_40_Compliance_and_Standards.md b/docs/Chapter_40_Compliance_and_Standards.md
index 0909436..0c436ff 100644
--- a/docs/Chapter_40_Compliance_and_Standards.md
+++ b/docs/Chapter_40_Compliance_and_Standards.md
@@ -33,6 +33,10 @@ For years, AI Red Teaming was an ad-hoc activity. But with the passage of the **
Think of these frameworks as "Attack Graphs." If a standard requires X, we attack X to prove it's missing.
+
+ 
+
+
### 40.2.1 NIST AI RMF (Risk Management Framework)
NIST uses a lifecycle approach: **Map, Measure, Manage, Govern**.
@@ -70,6 +74,10 @@ Regulation is not uniform. The Red Teamer must know which geography applies.
We don't just "look around." We follow a rigorous audit script.
+
+ 
+
+
### 40.3.1 The "Evidence-Based" Approach
An auditor doesn't trust; they verify.
@@ -443,6 +451,10 @@ print(dashboard.generate_report())
### 40.9.2 Risk Scoring Automation
+
+ 
+
+
```python
from dataclasses import dataclass
from enum import Enum
diff --git a/docs/assets/Ch40_Flow_AuditCycle.png b/docs/assets/Ch40_Flow_AuditCycle.png
new file mode 100644
index 0000000..26bb71b
Binary files /dev/null and b/docs/assets/Ch40_Flow_AuditCycle.png differ
diff --git a/docs/assets/Ch40_Logic_RiskClass.png b/docs/assets/Ch40_Logic_RiskClass.png
new file mode 100644
index 0000000..9a8d4b7
Binary files /dev/null and b/docs/assets/Ch40_Logic_RiskClass.png differ
diff --git a/docs/assets/Ch40_Map_RegLandscape.png b/docs/assets/Ch40_Map_RegLandscape.png
new file mode 100644
index 0000000..30ff283
Binary files /dev/null and b/docs/assets/Ch40_Map_RegLandscape.png differ