EKOSdocs
Docs / Concepts Learn

Compiled Knowledge

What compilation adds on top of raw observation: recovered structure, resolved identity, derived rollups and risks.

Raw observation says a file exists. Compiled knowledge says this file defines a class that extends that one, and 14 modules depend on it.

Beyond per-source recovery, compilation derives:

  • Concentration risks — any object with three or more real DependsOn dependents becomes a Risk object. Observed only, with no inferred severity.
  • Subsystem rollups — hierarchical summaries of modules and crates.
  • Data lineage links — from sources through transformations to sinks, and from each SQL routine to the tables it reads and writes and the routines it calls.
  • Schema history — each migration script's changes linked to the tables they alter, and tickets linked to the change sets, code and docs that name them.
  • Write behaviour — per table: whether updates always move its update timestamp, and every way its rows can be deleted (application code, users, cascading keys, purges), each with a citation.
  • Conflicts — where two sources (two files, or the code and the live database) disagree about one fact, both claims are kept as a ConflictingEvidence item.
  • Reference integrity — every name that resolves to nothing or to several objects, written at commit to an integrity index outside the ledger and reported by ekos check refs (table, JSON or SARIF, with baselines).
  • Architecture knowledge — crate topology, roles (LLM-classified, stored as reviewable claims), an evidence-coverage score, drift over time.
  • Optional descriptions — LLM-written overviews (ai_overview, ai_usage) grounded in evidence and stored as properties, opt-in via [llm-description].

Anything an LLM produced is marked as such; deterministic and inferred knowledge are never mixed silently.