Entities

Objects are the things EKOS knows about: tables, services, files, functions, pipelines, people, documents.

An object (called an entity in conversation) has an id, a name, a kind, free-form properties, evidence, and a creation time.

Built-in kinds cover common enterprise things — File, Directory, Table, Column, Dataset, Service, Api, Pipeline, Dashboard, Person, Model, Prompt, Agent, BusinessRule, BusinessConcept, Entity. Analyzers add custom kinds for language- or format-specific things (RustSymbol, PythonModule, Crate, Document, Section, Risk, Rollup, …). Full list: Entity Types.

Identity

The same real thing often appears from several sources — a customers table in SQL, an ORM model in Python, a mention in a wiki. EKOS resolves identity conservatively:

• exact normalized-name duplicates of the same source kind merge;
• fuzzy matches become unconfirmed SameAs relationships awaiting human review — never a silent, irreversible merge;
• cross-system candidates (e.g. an Informix cust_mstr vs. a Postgres customers) come from ekos identity scan and are likewise unconfirmed until reviewed.