Core ER Diagram
The core (domain-agnostic) data model, reproduced faithfully. Plugin-specific tables are not shown here — see the Plugin ER Diagram for how they clip on.
Orientation
entityis the plugin registry;workspace_statusandworkfloware scoped to an entity type viaentity_id/belongs_to_entity_id.- The workspace carries no FK to any entity object — that relationship is owned by each plugin's join table. Likewise
workflow_executionlinks to the coreworkspace, not to a plugin entity. - The configuration graph —
model,agent,prompt_family/prompt/prompt_version,workflow_config/workflow_agent_assignment,service/service_config_set/service_assignment— is the dependency graph behind the disable cascade. workflow_executioncarries the four immutable snapshots and links toworkflow_execution_log(the per-step, per-cost record) and optionally to itself viaretry_of.- Core workspace rows are never deleted; there are no
is_deleted/is_archivedcolumns here.