diff --git a/src/data/roadmaps/software-design-architecture/content/law-of-demeter@vnLhItObDgp_XaDmplBsJ.md b/src/data/roadmaps/software-design-architecture/content/law-of-demeter@vnLhItObDgp_XaDmplBsJ.md
index 4a63f356b..c30421714 100644
--- a/src/data/roadmaps/software-design-architecture/content/law-of-demeter@vnLhItObDgp_XaDmplBsJ.md
+++ b/src/data/roadmaps/software-design-architecture/content/law-of-demeter@vnLhItObDgp_XaDmplBsJ.md
@@ -1 +1,34 @@
-# Law of Demeter
\ No newline at end of file
+# Law of Demeter
+
+Also called “Principle of Least Knowledge”, it states:
+
+A method should only interact with its immediate dependencies, not deeply nested objects.
+
+## In Practice
+
+- Avoid chaining calls deep into the internals of other objects.
+- Restrict communication to objects you directly manage.
+
+### 🔹 ❌ Bad Example (Violation)
+
+```
+// Controller
+total = order.customer.address.getRegionTaxRate() * order.amount
+```
+
+### 🔹 ✅ Good Example 
+
+```
+// Controller
+total = order.calculateTotal()
+```
+
+## 🔹 Why It Matters
+
+- **Reduces coupling** → fewer dependencies between classes.
+- **Increases maintainability** → changes in one class don’t affect distant classes.
+- **Improves readability** → clear boundaries of responsibility.
+
+## 🔹 Resources
+
+- [@Article: Law of Demeter Explained](https://en.wikipedia.org/wiki/Law_of_Demeter)