EdictumDatabase Model
Current high-level data model for edictum-api.
AI Assistance
Right page if: you want the current high-level persisted entities in edictum-api. Wrong page if: you want the retired tenant/bundle schema map from the old server stack. Gotcha: the current backend is workspace-based and the old console schema map is not authoritative.
This page is intentionally high level. The current backend is edictum-api,
and the authoritative schema lives in that repo’s current migrations.
Current Top-Level Entities
| Entity | Purpose |
|---|---|
| Workspaces | Scope human and agent data |
| API keys | Workspace-scoped agent credentials |
| Rulesets | Versioned policy/ruleset documents |
| Decision events | Runtime decisions emitted by agents |
| Workflow snapshots | Latest workflow/run state per agent session |
| Approvals | Pending and resolved human decisions |
| Agents | Registered agent identities and activity summaries |
| Audit events | Operator-facing audit timeline |
| Notification channels | Telegram, Slack, Discord, and webhook config |
What Changed
The retired docs described bundle/composition tables and older tenant-local auth tables from the old server stack. That is not the current public schema map.
If you need exact current fields or query behavior, use:
- API Reference
- the current
edictum-apimigrations and handlers
Last updated on