Skip to content

eka-quick-ref_en.md

Latest commit

 

History

History
95 lines (69 loc) · 5.26 KB

eka-quick-ref_en.md

File metadata and controls

95 lines (69 loc) · 5.26 KB
Raw

EKA Quick Reference

Executable Knowledge Architecture - Formal Definition, Roadmap, and Maturity Levels

One-page reference for practitioners, architects, and knowledge engineers.

1. Formal EKA Definition

$$\large\boxed{EKA = ( K, \ \ R, \ \ \Theta, \ \ \Phi, \ \ \Gamma)}$$

Component Name Description
$K$ Knowledge Graph Nodes (entities/individuals) + edges (semantic relationships), conforming to an ontology
$R$ Reasoning & Rules OWL inference rules, SWRL, or custom logic that derives new facts
$\Theta$ Triggers Semantic events, SPARQL queries, time schedules, or state changes that intiate execution
$\Phi$ Execution Actions API calls, workflow invocations, alerts, database updates, or external system commands
$\Gamma$ Governance SHACL constraints, access control policies, audit trails, and semantic integrity rules

2. EKA Implementation Roadmap (Six Layers)

Layer Artifact Tool Example EKA Component
1. Diagramming Conceptual sketches Draw.io, Visio, whiteboard (informal input)
2. Meta-Model Structural rules ArchiMate, UML class diagrams Requirements for $K$ and $\Gamma$
3. Ontology OWL ontology (classes, properties, restrictions) Protégé $R$ (Reasoning) + $\Gamma$ (constraints)
4. RDF Serialization RDF/XML, Turtle, OWL/XML Protégé export, RDFlib, Noesemantics Portability format for $K$
5. Knowledge Graph Pupulated graph with individuals and inferences Neo4j, GraphDB, Stardog $K$
6. Executable Intelligence Event-driven actions and decisions EKA runtime, customer orchestrator $\Theta$ + $\Phi$

3. EKA Maturity Levles (L0 - L3)

Level Name Characteristics $K$ $R$ $\Theta$ $\Phi$ $\Gamma$ Typical Use Case
L0 Semantic Modeling OWL ontology only, no graph, no execution $\color{red}\mathbf{\times}$ $\color{green}\checkmark$ $\color{red}\mathbf{\times}$ $\color{red}\mathbf{\times}$ Partial Learning, academic, exploration
L1 Knowledge Graph Ontology + populated, queryable graph $\color{green}\checkmark$ $\color{green}\checkmark$ $\color{red}\mathbf{\times}$ $\color{red}\mathbf{\times}$ Partial Enterprise knowledge repository
L2 Reactive Knowledge L1 + triggers and notifications $\color{green}\checkmark$ $\color{green}\checkmark$ $\color{green}\checkmark$ Partial $\color{green}\checkmark$ Compliance monitoring, alerting
L3 Executable Intelligence (full EKA) L2 + autonomous actions + full governance $\color{green}\checkmark$ $\color{green}\checkmark$ $\color{green}\checkmark$ $\color{green}\checkmark$ $\color{green}\checkmark$ Autonomous AI, digital twins, closed-loop systems

Note: L2 uses $\Phi$ to trigger notification or human-in-the-loop actions, L3 fully automates $\Phi$.

4. Quick Rules of Thumb

If you have... Then you are at... But you are NOT yet EKA unless...
Only an OWL file (Protégé) L0 ---
Ontology + graph database (queried manually) L1 You have triggers ($\Theta$) and actions ($\Phi$)
Triggers that send alerts/emails L2 Actions are fully automated, not requiring human intervention
Automated actions invoked by semantic conditions L3-Full EKA ---

5. EKA vs. Related Concepts

Concepts Relationship to EKA
OWL Reasoner (Pellet, HermiT) A component or $R$, not the whole EKA
Knowledge Graph (Neo4j, GraphDB) The $K$ layer - necesary but not sufficient
Rule Engine (Drools, DMN) Can implement parts of $R$ and $\Phi$
Semantic Web Stack EKA extends it with an explicit execution layer ($\Theta$, $\Phi$)
TOGAF / ArchiMate EKA can serve as the semantic automation pillar

6. EKA Readiness Checklist

Use this checklist to assess any semantic project against the EKA framework.

  • $K$ - Knowledge Graph: Populated graph with individuals and relationships?
  • $R$ - Reasoning: Inferred relationships automatically derived?
  • $\Theta$ - Triggers: Conditions (queries, events, time) defined?
  • $\Phi$ - Actions: Automatic API calls, workflows, or alerts configured?
  • $\Gamma$ - Governance: SHACL validation, access control, and audit enabled?

Scoring:

  • 0-2 checks: Semantic Project (not yet EKA)
  • 3-4 checks: Reactive Knowledge System (L2)
  • 5 checks: Full EKA Implementation (L3)

7. Core Principle (Memorize This)

Knowledge is not only represented - it is executed!

An EKA system does not just answer "What is true?" (ontology + graph).

It also answers "What should be done automatically, based on what is true?" (triggers + actions + governance).

Last Updated at 2026-05-30