EKOSdocs
Docs / Concepts Learn

Knowledge Compiler

EKOS applies the compiler model to enterprise knowledge: deterministic passes over an intermediate representation.

A language compiler and EKOS have the same shape:

A language compiler compared with the EKOS knowledge compiler
A language compiler compared with the EKOS knowledge compiler
Compiler idea EKOS equivalent
Source files Observation artifacts (content-addressable)
Parser / analyzer Recovery passes: one analyzer per source kind
Intermediate representation KIR — typed objects, relationships, evidence
Symbol resolution Identity resolution (ekos resolve)
Output format CKM — the Canonical Knowledge Model
Linking / emitting Commit to the append-only ledger
Diagnostics Coded warnings, e.g. SQL001 — Error Codes

Why the analogy matters

  • Deterministic passes can be cached, tested and trusted. Each pass declares its dependencies and a version; a changed pass invalidates only what it produced.
  • An IR decouples sources from consumers. A Pentaho step, a SQL SELECT, a view and a stored procedure all compile into one shared Transformation IR (Source, Filter, Join, Aggregate, Calculate, Sink, Unmapped), so legacy ETL can be diffed against a new pipeline.
  • Errors are data. What cannot be parsed becomes Unmapped evidence, never a silent gap.

See Compilation Pipeline.