Skip to content

Maintainers

This section is for people changing the engine, Studio, docs deploy, or CI — crate names, Rust policy, and review expectations are fair game here.

If you want to use Eelden, start at Consumers. For the commercial shift-left narrative (what leaves the business layer), see Business & sales. Capability claims live on Status — that page wins over any phase narrative in internals/engine-plan.md.

Path

Read these in order when onboarding or reviewing a substantial change:

  1. Build — workspace test, wasm, Studio, docs, CI
  2. Architecture — traits and query pipeline
  3. Contribute — Rust policy and Status honesty
  4. Review process — teaching reviews
  5. Testing — tripwires and maintainer harnesses
  6. Deploy — docs + playground via Tamer
  7. Internals — what stays private vs public

Also useful: Repository layout.

Source of truth

LayerWhere
Public docs (this site)docs/
Agent / design docsinternals/
Agent rulesAGENTS.md
Engine of recordcrates/ cargo workspace

Pre-alpha. Local-first. Stdlib-only Rust engine. Tenant concerns shifted left into the database.