[Feature] Propose govoplan-dataflow module for pipelines, BI, and source publication #198

Closed
opened 2026-07-06 21:50:06 +02:00 by zemion · 1 comment
Owner

Created from the GovOPlaN module and integration planning list on 2026-07-06.

  • Source item: dataflow module / connect datasources / BI / consume sources -> become source
  • Proposed owner: govoplan-core
  • Routing rationale: govoplan-dataflow does not exist locally; the concept crosses datasources, reporting, connectors, and publication.
  • Related wiki: core Repo-docs-GOVOPLAN-MODULE-ROADMAP after the wiki sync.

Acceptance criteria:

  • Define dataflow ownership: ingestion, transformation, validation, scheduling, lineage, publication, and audit events.
  • Specify how consumed sources can become governed GovOPlaN sources for APIs, reports, RSS, exports, or downstream systems.
  • Decide whether this needs a new govoplan-dataflow repository after datasource boundaries are clear.
<!-- codex-module-roadmap-fingerprint:023175d47596dafce2b3848b --> Created from the GovOPlaN module and integration planning list on 2026-07-06. - Source item: `dataflow module / connect datasources / BI / consume sources -> become source` - Proposed owner: `govoplan-core` - Routing rationale: `govoplan-dataflow` does not exist locally; the concept crosses datasources, reporting, connectors, and publication. - Related wiki: core `Repo-docs-GOVOPLAN-MODULE-ROADMAP` after the wiki sync. Acceptance criteria: - [ ] Define dataflow ownership: ingestion, transformation, validation, scheduling, lineage, publication, and audit events. - [ ] Specify how consumed sources can become governed GovOPlaN sources for APIs, reports, RSS, exports, or downstream systems. - [ ] Decide whether this needs a new `govoplan-dataflow` repository after datasource boundaries are clear.
zemion added this to the Module And Integration Roadmap milestone 2026-07-06 21:50:06 +02:00
zemion added the
type
feature
codex/ready
labels 2026-07-07 23:09:10 +02:00
zemion added the
priority
p2
status
triage
labels 2026-07-08 02:14:58 +02:00
Author
Owner

Resolved by docs/MODULE_BOUNDARY_DECISIONS.md.

Decision: do not create govoplan-dataflow yet. Start with workflow/reporting/connectors. A dataflow module becomes justified only when first-class ingestion, transformation, validation, scheduling, lineage, publication, audit events, reruns, and source-to-source workflows emerge as repeated contracts that do not belong to existing modules.

The first monthly extraction/transformation package should prove the boundary before a repository is created.

Resolved by `docs/MODULE_BOUNDARY_DECISIONS.md`. Decision: do not create `govoplan-dataflow` yet. Start with workflow/reporting/connectors. A dataflow module becomes justified only when first-class ingestion, transformation, validation, scheduling, lineage, publication, audit events, reruns, and source-to-source workflows emerge as repeated contracts that do not belong to existing modules. The first monthly extraction/transformation package should prove the boundary before a repository is created.
zemion added the
source/module-roadmap
label 2026-07-10 19:48:24 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#198
No description provided.