[Feature] Define govoplan-dataflow module #189

Closed
opened 2026-07-06 20:26:28 +02:00 by zemion · 2 comments
Owner

Imported from the GovOPlaN module and integration planning discussion.

Durable context: Gitea wiki page Repo-docs-GOVOPLAN-MODULE-ROADMAP in govoplan-core.

Define a module for connecting datasources to transformations, BI, exports, and reports.

Scope questions:

  • pipeline modeling
  • scheduled runs
  • validation and error handling
  • lineage/provenance
  • handoff to reports, dashboards, and published sources
<!-- codex-module-roadmap:dataflow-bi-module --> Imported from the GovOPlaN module and integration planning discussion. Durable context: Gitea wiki page `Repo-docs-GOVOPLAN-MODULE-ROADMAP` in `govoplan-core`. Define a module for connecting datasources to transformations, BI, exports, and reports. Scope questions: - pipeline modeling - scheduled runs - validation and error handling - lineage/provenance - handoff to reports, dashboards, and published sources
zemion added this to the GovOPlaN Module Roadmap milestone 2026-07-06 20:26:28 +02:00
Author
Owner

The dedicated repository and implementation epic now exist: GovOPlaN/govoplan-dataflow#1. The initial module is being implemented with a canonical graph, constrained SQL compiler, bounded preview, and graphical editor. Close this definition issue once the manifest, migration, API, and WebUI first slice are pushed.

The dedicated repository and implementation epic now exist: https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/1. The initial module is being implemented with a canonical graph, constrained SQL compiler, bounded preview, and graphical editor. Close this definition issue once the manifest, migration, API, and WebUI first slice are pushed. <!-- codex-dataflow-repo-created-2026-07-28 -->
Author
Owner

Codex State: done

Summary

  • The Dataflow boundary is now defined and implemented in the dedicated GovOPlaN/govoplan-dataflow repository.
  • Detailed implementation state and follow-up work moved to govoplan-dataflow#1 through #10; Connectors owns source access, Reporting owns presentation/export, Workflow owns orchestration, and Risk Compliance owns sanctions semantics.

Verification

  • Module manifest contract scan, dependency-boundary scan, core smoke, and WebUI product builds pass with Dataflow enabled.
## Codex State: done ### Summary - The Dataflow boundary is now defined and implemented in the dedicated GovOPlaN/govoplan-dataflow repository. - Detailed implementation state and follow-up work moved to govoplan-dataflow#1 through #10; Connectors owns source access, Reporting owns presentation/export, Workflow owns orchestration, and Risk Compliance owns sanctions semantics. ### Verification - `Module manifest contract scan, dependency-boundary scan, core smoke, and WebUI product builds pass with Dataflow enabled.`
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-core#189
No description provided.