Skip to main content

Default Plugin ER Diagram

This shows how the default plugin's tables (default_plugin_*) clip onto the core. The two core tables shown (workspace, workflow_execution) are integration points only; the full core model is the Core ER Diagram. It's the concrete illustration of the plugin data-model pattern any plugin follows.

Orientation​

  • Core vs. plugin: workspace and workflow_execution are core; everything else is plugin-owned.
  • The invariant, visualized: every foreign key points from a plugin table to a core table (or to another plugin table) — no core table references a plugin table. The core is unaware of the plugin.
  • default_plugin_thing holds the entity-level pointers active_workspace_id and final_workspace_id (both → workspace, nullable) plus the is_deleted soft-delete flag.
  • default_plugin_workspace is the entity↔workspace join table, with is_deleted / is_archived and a unique (thing, workspace) pair. Core workspaces are never hard-deleted; plugin-level deletion/archival lives here.
  • default_plugin_output and default_plugin_input hold per-workspace results and append-only operator input.

The business rules governing these tables live in the Plugin Developer package; the authoritative schema is the plugin's migrations.