[Epic] Deliver the governed datasource catalogue and lifecycle #1

Open
opened 2026-07-28 12:48:18 +02:00 by zemion · 0 comments
Owner

Outcome

Provide one provider-neutral, tenant-governed data layer that Dataflow,
Workflow, Reporting, Risk Compliance, and domain modules can consume without
importing connector implementations or retaining credentials.

Boundary

  • Datasources owns source identity, visibility, live/cached/static mode,
    staging, immutable materializations, frozen states, schema/fingerprints,
    provenance, and bounded reads.
  • Connectors owns external protocols, endpoints, credentials, discovery,
    source-side filtering/pushdown, and provider health.
  • Dataflow owns transformations and lineage.
  • Workflow owns orchestration, approvals, retries, and module handoffs.

First Slice

  • Package, module manifest, permissions, migration, uninstall guard, and WebUI route.
  • Tenant-isolated live, cached, and static datasource catalogue.
  • Bounded JSON/CSV staging and promotion.
  • Append-only materializations, current state, and explicit frozen states.
  • Schema versions, content fingerprints, provenance, and bounded preview.
  • Connector origin adapter and Dataflow capability consumer.
  • Focused composition test from Connector through Datasources to Dataflow.
  • Production storage and concurrency hardening.
  • Quality, schema compatibility, approval, retention, and policy gates.
  • Module-output publication and Workflow lifecycle integration.

Architecture: https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/DATASOURCE_AND_DEFINITION_GRAPH_ARCHITECTURE.md

## Outcome Provide one provider-neutral, tenant-governed data layer that Dataflow, Workflow, Reporting, Risk Compliance, and domain modules can consume without importing connector implementations or retaining credentials. ## Boundary - Datasources owns source identity, visibility, live/cached/static mode, staging, immutable materializations, frozen states, schema/fingerprints, provenance, and bounded reads. - Connectors owns external protocols, endpoints, credentials, discovery, source-side filtering/pushdown, and provider health. - Dataflow owns transformations and lineage. - Workflow owns orchestration, approvals, retries, and module handoffs. ## First Slice - [x] Package, module manifest, permissions, migration, uninstall guard, and WebUI route. - [x] Tenant-isolated live, cached, and static datasource catalogue. - [x] Bounded JSON/CSV staging and promotion. - [x] Append-only materializations, current state, and explicit frozen states. - [x] Schema versions, content fingerprints, provenance, and bounded preview. - [x] Connector origin adapter and Dataflow capability consumer. - [x] Focused composition test from Connector through Datasources to Dataflow. - [ ] Production storage and concurrency hardening. - [ ] Quality, schema compatibility, approval, retention, and policy gates. - [ ] Module-output publication and Workflow lifecycle integration. Architecture: https://git.add-ideas.de/GovOPlaN/govoplan/src/branch/main/docs/DATASOURCE_AND_DEFINITION_GRAPH_ARCHITECTURE.md
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-datasources#1
No description provided.