Core concepts
Eidos File
Section titled “Eidos File”An Eidos File is a SQLite application file with canonical metadata and data
objects. Its Runtime maps those objects to typed tables, fields, records,
relations, formulas, and saved views. A .eidos extension alone does not make
an arbitrary SQLite database a valid Eidos File.
Runtime
Section titled “Runtime”Runtime owns logical meaning: query, filter, sort, Formula, Lookup, Relation, conversion, revision, mutation, and validation behavior. A host must call Runtime instead of reimplementing those rules in UI code or raw SQL.
Host and Adapter
Section titled “Host and Adapter”A host is the environment around Runtime. The browser handles file permission and recovery; Lite handles folders, local processes, and native file dialogs; CLI Serve handles one local file over HTTP. Adapters connect Runtime to SQLite and platform capabilities without changing data semantics.
In Eidos Lite, a Space is an ordinary folder chosen by the user. It can contain several Eidos Files and other files. Space describes a desktop working context, not a new database format.
Shared UI
Section titled “Shared UI”@eidos.space/eidos-file-ui supplies the editor shared by Web, Lite, and CLI
Serve. Grid, Gallery, Kanban, record editing, query controls, and theme roles
are shared implementations.
Graft, history, and Sync
Section titled “Graft, history, and Sync”Graft provides version history for SQLite-backed files and Spaces. Eidos Lite can connect that local history to an optional authenticated remote. Local files remain usable while offline or signed out.
For exact ownership rules, read the specification suite.