Knowledge Schema
Object kinds, relationship kinds and record fields.
ObjectKind
Built-in: File, Directory, Table, Entity, Service, Api, BusinessRule, BusinessConcept, Dataset, Column, Pipeline, Dashboard, Person, Model, Prompt, Agent, Unknown. Otherwise Custom(String) — serialized as the bare string. Every custom kind an analyzer emits is declared in ekos_kir::custom_kinds::REGISTRY (for example View, Procedure, Trigger, JavaType, JavaMethod, ModelTable, SchemaChangeSet, Ticket, WriteBehaviour, ConflictingEvidence), with whether it is keyed by structure — a keyed kind is never an identity-merge candidate.
Objects read from a live database carry the property origin: live.
Apache Ossie models found in a project's sources become OssieModel, OssieDataset and OssieMetric objects, each keyed by its file (RFC 0245). At commit, an OssieDataset is linked to its table by a DependsOn edge with the property link: ossie_source. See Apache Ossie.
RelationshipKind
ForeignKey, Calls, Extends, DependsOn, OwnedBy, Contains, References, CoupledWith, Unknown, or Custom(String).
Records
| Record | Fields |
|---|---|
KirObject |
id, name, kind, properties, evidence[], created_at |
KirRelationship |
id, kind, from, to, properties, evidence[], created_at, valid_from?, valid_until? |
KirEvidence |
id, location, fragment, confidence, created_at |
CkmObject |
id, name, kind, properties, primary_description?, evidence[] (by confidence), source_artifact_ids[] |
LedgerEntry |
id, entry_type, payload, written_at |
| Stored fact | entity, attr, pos?, value |
Full semantics: Knowledge Model. Types are defined in ekos/crates/kir/src/lib.rs and ekos/crates/semantic/src/lib.rs.