Repository navigation
v2.0.0
Eunomia 2.0
A new foundation: SurrealDB 3.3, a database per org, background jobs, stronger auth, and uploaded documents. Update from Settings → Updates. Your data is moved and verified automatically, and the old data is kept for rollback.
Upgrading
- Automatic database upgrade. On update, SurrealDB 2.x data is backed up (encrypted), copied, imported into 3.3 and verified table by table. The old volume is never modified, so rollback is always possible. This happens on
docker compose upitself, so it works even if you skip 1.4.2 (recommended but not required). - One-time move into an org. A 1.x install becomes one org with its own database, and every existing user becomes a member. Record ids, logins and agent tokens keep working.
- Installer 1.8.0 installs 2.0 fresh, or upgrades an existing install when re-run.
New
- Documents. Upload text, Markdown, JSON, CSV and text-based PDFs (UI or MCP
document_*tools). They're stored in SurrealDB's built-in file buckets (optionally on S3), split into passages, embedded, added to the entity graph, and downloadable as the original file. Backups include them. - A database per org, with its own database user. The server runs hardened, with an explicit function allow-list.
- Background job queue with leases, retries and a scheduler leader, replacing the old sync loop.
- Auth: scoped, vault-restricted and expiring tokens; MCP OAuth 2.1; signup modes; admin-only updates and HTTPS.
- Debuggable by agents: stable error codes with trace ids, failure capsules and
replay, JSON logs and optional OpenTelemetry. - Nightly encrypted backups that are refused unless per-table row counts match, plus restore drills.
- Memory improvements from 1.4.1 are carried over:
- org vaults are searched by default;
- outdated facts are marked superseded;
- entities can be found by the text of their facts, and possible duplicates are flagged;
- Pocket calls feed the entity graph.
Fixed in review
- The 1.x→2.0 move now keeps stored Pocket recordings.
- The Pocket migration runs on the hardened server.
- A failed upgrade's rollback never points the app at the temporary copy.
- A memory edit and its stale summary are saved atomically.
- Link-only connector changes are no longer dropped.
- Vault clone and merge are all-or-nothing.
- The migration lock can't be stolen mid-run.
- The server refuses an empty
ENCRYPTION_KEY, and replaces any database password that was derived from one. - Exactly-once job claims are tested across processes.
- Re-uploading a document never shows both versions.