Database schema explorer

Explore the PostgreSQL control-plane schema produced by every checked-in SQLx migration. Search by table, column, or PostgreSQL type; narrow the inventory by domain; then follow declared foreign keys through the relationship map.

Catalog snapshot, not a live database console

The explorer reads a committed catalog snapshot generated from a disposable PostgreSQL 16 database. It contains structure only—no operator data, credentials, row counts, or query access. Runtime truth remains the database reached by DATABASE_URL.

DATABASE public loading catalog… migration —

find

all ledger work discovery config identity alerts

— tables — columns — foreign keys — indexes

Preparing table detail…

relationship map Declared foreign keys

Select a node to inspect its columns and dependencies.

Persistence domains

Domain	Tables	Contract
Execution ledger	batch_execution_record, execution_observations, execution_artifacts, provenance_events	Durable intent, external evidence, immutable artifacts, and audit history
Distributed work	jobs, job_claim_history, worker_instances, daliuge_deployment_profile	Claims, leases, fencing, placement, and deployment policy
Discovery	source_registry, archive_metadata	Source enrollment, claims, signatures, and normalized archive facts
Project configuration	project_configs, project_config_wasm	Versioned project specifications and content-addressed extensions
Identity	users, token_blacklist	Operator identities and revoked access tokens
Alerting	alert_rules, notification_channels, alert_deliveries	Alert policy, delivery targets, and delivery outcomes

The relationship map shows PostgreSQL foreign-key constraints only. provenance_events.execution_id is deliberately an indexed audit correlation field rather than a foreign key, so provenance can outlive or describe records without introducing a deletion dependency.

Refresh the snapshot

Whenever a migration changes schema, regenerate the explorer data before committing:

make db-schema
git diff -- boilerplate_docs/assets/data/database-schema.json

The exporter starts a disposable postgres:16-alpine container, applies the migrations in filename order, reads pg_catalog, validates the JSON, and removes the container. Set BEAMPIPE_DOCKER_CONTEXT when the desired Docker engine is not the current context.