From 5d4a2b62ca04c7c5e66454a51bac22d7a44fc5c6 Mon Sep 17 00:00:00 2001 From: Jacobus Geluk Date: Tue, 2 Dec 2025 02:11:20 +0000 Subject: [PATCH] feat(docs): add DIKW to EKGF section to enable reuse page - Add 'From DIKW to EKGF: Making Knowledge Executable' section - Explain how EKGF Method extends DIKW model with operational dimension - Include DIKW revised diagram showing path to executable knowledge - Add image asset (dikw-revised.svg) to docs/assets/ - Remove old screenshot files that are no longer needed - Fix merge conflict markers in enable-reuse.md --- ...6-3498e6aa-895d-4e60-9b3a-87f775e1e172.png | 0 ...1-8748f67b-039b-41e8-9ca3-3a1823e1cb9a.png | 0 ...2-ccca9932-bf28-4541-a1aa-d1bf017c173d.png | 0 ...9-c031983d-701b-4ba7-9325-c89fe113e92c.png | 0 docs/assets/dikw-revised.svg | 674 ++++++++++++++++++ docs/objective/enable-reuse.md | 56 +- 6 files changed, 702 insertions(+), 28 deletions(-) delete mode 100644 assets/Screenshot_2025-12-01_at_23.34.46-3498e6aa-895d-4e60-9b3a-87f775e1e172.png delete mode 100644 assets/Screenshot_2025-12-01_at_23.39.31-8748f67b-039b-41e8-9ca3-3a1823e1cb9a.png delete mode 100644 assets/Screenshot_2025-12-01_at_23.44.02-ccca9932-bf28-4541-a1aa-d1bf017c173d.png delete mode 100644 assets/Screenshot_2025-12-01_at_23.45.59-c031983d-701b-4ba7-9325-c89fe113e92c.png create mode 100644 docs/assets/dikw-revised.svg diff --git a/assets/Screenshot_2025-12-01_at_23.34.46-3498e6aa-895d-4e60-9b3a-87f775e1e172.png b/assets/Screenshot_2025-12-01_at_23.34.46-3498e6aa-895d-4e60-9b3a-87f775e1e172.png deleted file mode 100644 index e69de29b..00000000 diff --git a/assets/Screenshot_2025-12-01_at_23.39.31-8748f67b-039b-41e8-9ca3-3a1823e1cb9a.png b/assets/Screenshot_2025-12-01_at_23.39.31-8748f67b-039b-41e8-9ca3-3a1823e1cb9a.png deleted file mode 100644 index e69de29b..00000000 diff --git a/assets/Screenshot_2025-12-01_at_23.44.02-ccca9932-bf28-4541-a1aa-d1bf017c173d.png b/assets/Screenshot_2025-12-01_at_23.44.02-ccca9932-bf28-4541-a1aa-d1bf017c173d.png deleted file mode 100644 index e69de29b..00000000 diff --git a/assets/Screenshot_2025-12-01_at_23.45.59-c031983d-701b-4ba7-9325-c89fe113e92c.png b/assets/Screenshot_2025-12-01_at_23.45.59-c031983d-701b-4ba7-9325-c89fe113e92c.png deleted file mode 100644 index e69de29b..00000000 diff --git a/docs/assets/dikw-revised.svg b/docs/assets/dikw-revised.svg new file mode 100644 index 00000000..be993821 --- /dev/null +++ b/docs/assets/dikw-revised.svg @@ -0,0 +1,674 @@ + + + + + + + + + + + + + + + + + + + +Information + + + + + + + +Knowledge + + + + + + + +Data + + + + + + + +Behavior + + + + + + + +Reusable Use Case + + + + + + + +Composable Enterprise + + + + + + + +Wisdom + + + + + + + +i.e. Human and Agentic Understanding + + + + + + + +DIKW Model — Revised + + + + + + + +✅  + + + + + + + +❌ + + + + + + + +The Path to Executable Knowledge \ No newline at end of file diff --git a/docs/objective/enable-reuse.md b/docs/objective/enable-reuse.md index b5090ff7..a1b25970 100644 --- a/docs/objective/enable-reuse.md +++ b/docs/objective/enable-reuse.md @@ -77,34 +77,6 @@ This is the crucial difference: Method captures *the behaviour itself* — executable, governed, and reusable across domains — without necessarily writing code at all. -``` mermaid -flowchart LR - - A[Data] --> B[Information] - - B --> C[Knowledge] - - C --> D[Behaviour] - - D --> E[Reusable Use Case] - - E --> F[[Composable Enterprise]] - - - - style A fill:#ffffff,stroke:#000000,stroke-width:2px - - style B fill:#ffffff,stroke:#000000,stroke-width:2px - - style C fill:#ffffff,stroke:#000000,stroke-width:2px - - style D fill:#ffffff,stroke:#000000,stroke-width:2px - - style E fill:#ffffff,stroke:#000000,stroke-width:2px - - style F fill:#000000,stroke:#ffffff,stroke-width:2px,color:#ffffff,font-weight:bold -``` - In this sense, a **Use Case** in the EKG is just as real and reusable as a software package in the JavaScript or Python ecosystems. Each can be discovered, installed, versioned, extended, and composed — @@ -114,6 +86,34 @@ spanning data, logic, and meaning. That's why **reuse** is not a side effect of the EKG. It's the *reason the EKG exists.* +### From DIKW to EKGF: Making Knowledge Executable + +The well-known **DIKW Model** (Data → Information → Knowledge → Wisdom) +has guided information management for decades. +But it assumes that *Wisdom naturally follows from Knowledge* — as if +understanding automatically produces action. +In practice, enterprises rarely reach that state because the bridge from +*knowing* to *doing* is missing. + +The **EKGF Method** extends this model by adding the **operational +dimension**: +knowledge becomes **behaviour**, behaviour becomes **reusable**, and +reuse powers **composability**. +This is the *Path to Executable Knowledge* — where understanding turns +into governed, shareable, and actionable intelligence. + +The diagram below visualises this shift — showing how the EKGF Method +transforms the classic DIKW hierarchy into a living model of executable, +reusable knowledge. + +![DIKW Model Revised – Path to Executable Knowledge](../assets/dikw-revised.svg) + +Traditional DIKW ends at understanding. +The EKGF Method continues by modelling behaviour, packaging it as reusable +use cases, and feeding it back into a composable enterprise — closing the +loop between data, knowledge, and operational wisdom. + +>>>>>>> e8ff454 (feat(docs): add DIKW to EKGF section to enable reuse page) ## The Role of the Use Case Tree (UCT) In the EKGF Method, the **Use Case Tree (UCT)** is the mechanism that