Docs / Plugins Build
Plugin Architecture
The extension points EKOS actually has, and how they map to source, compiler, knowledge and query plugins.
EKOS has traits, not a dynamic plugin loader: you write a Rust crate and build an ekos binary that includes it. The seam is EkosExtension (RFC 0149); the public binary is simply main_with(Extensions::none()).
| Plugin kind | Mechanism | Trait / hook |
|---|---|---|
| Source | new connector | Observer (observation-sdk), via EkosExtension::observers |
| Compiler | new analysis | CompilerPass, via EkosExtension::recovery_passes; SQL dialects via SqlDialectParser |
| Knowledge | post-commit enrichment | EkosExtension::after_commit over the committed ledger |
| Query | new MCP tools | EkosExtension::mcp_tools + call_mcp_tool; mcp_tool_is_scoped |
| Commands | whole CLI command groups (RFC 0191) | commands, command_classes (a catalogue class per leaf), run_command |
| Console pages | extra workspace tabs in the web console (RFC 0198/0207) | console_pages: panels, views and actions declared as data over the extension's own catalogue commands |
| Workflow | steps of the operator workflow (RFC 0213) | workflow_steps |
| Identity | the binary's own name and version | binary |
| Provider | LLM or embedding backend | LlmProvider, EmbeddingProvider |
The first public extension is EKOS Lakehouse (its own repository, alexeyban/ekos-lakehouse), which adds commands, console pages and workflow steps this way.
Why traits and not dynamic loading
Determinism and auditability. A statically linked extension is versioned with the binary, its logic_version is part of the build fingerprint, and the ledger records which pipeline wrote what.
Constraints
- Extension crates depend on public crates; public crates never depend on extensions.
after_commitfutures are notSend(#[async_trait(?Send)]).- Extension MCP tools are read-only: they receive the same cached store handle as the built-in read tools.
- An extension command name that is already taken, or a leaf without a catalogue class, is refused at start-up.
- New
Customobject kinds need a row inekos_kir::custom_kinds::REGISTRY.