Build with Eidos
Use the CLI for process automation, Runtime for typed data access, and the shared React package for an Eidos editor. Direct metadata-table access and SQL generation are not supported integration APIs.
| Build | Use | Provides |
|---|---|---|
| Script or Agent automation | eidos CLI | Stable JSON process boundary with atomic mutations and validation |
| Node application working with one file | @eidos.space/eidos-file/node-sqlite | Built-in node:sqlite with Runtime-owned semantics |
| Browser application | @eidos.space/eidos-file/browser | SQLite WASM stays in a Dedicated Worker |
| React viewer or editor host | @eidos.space/eidos-file-ui | Shared UI consumes only RuntimeClient and HostServices |
| Independent compatible implementation | Eidos Specifications | Normative format, behavior, adapter, and interaction contracts |
Runtime quickstart Create, mutate, validate, and reopen a file with Node's built-in SQLite.
Runtime and host boundaries Understand which layer owns data meaning, platform behavior, and presentation.
React UI package Compose the standard viewer or editor without giving React direct SQLite access.
Custom saved views Preserve open view metadata and register trusted React renderers.
Public packages
Section titled “Public packages”@eidos.space/eidos-file and @eidos.space/eidos-file-ui are MIT-licensed.
The repository and first-party applications remain under AGPL v3.