[Feature] Recurring datasource and data-transformation workflows #216

Open
opened 2026-07-07 21:16:14 +02:00 by zemion · 4 comments
Owner

Model the monthly data extraction/transformation use case as a first-class product slice. The system should receive or fetch data, apply transformation rules, validate outputs, and prepare files for several downstream systems.

Source: docs/GOVERNMENT_OPERATIONS_VISION.md

Acceptance criteria:

  • decide whether govoplan-datasources and govoplan-dataflow repositories/modules are needed
  • define datasource, schema discovery, transformation rule, schedule, validation, output, and provenance contracts
  • support previewable diffs and diagnostics before publication
  • workflow can react to success, warning, failure, and manual approval states
  • audit records inputs, hashes, outputs, mapping versions, and operator actions
Model the monthly data extraction/transformation use case as a first-class product slice. The system should receive or fetch data, apply transformation rules, validate outputs, and prepare files for several downstream systems. Source: `docs/GOVERNMENT_OPERATIONS_VISION.md` Acceptance criteria: - decide whether `govoplan-datasources` and `govoplan-dataflow` repositories/modules are needed - define datasource, schema discovery, transformation rule, schedule, validation, output, and provenance contracts - support previewable diffs and diagnostics before publication - workflow can react to success, warning, failure, and manual approval states - audit records inputs, hashes, outputs, mapping versions, and operator actions
Author
Owner

The module decision and first work packages are now recorded under GovOPlaN/govoplan-dataflow#1, with source discovery in GovOPlaN/govoplan-connectors#9, comparison/review in GovOPlaN/govoplan-dataflow#7, and Workflow handoff in GovOPlaN/govoplan-workflow#4. This issue remains the Core-side cross-capability contract tracker.

The module decision and first work packages are now recorded under https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/1, with source discovery in https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/9, comparison/review in https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/7, and Workflow handoff in https://git.add-ideas.de/GovOPlaN/govoplan-workflow/issues/4. This issue remains the Core-side cross-capability contract tracker. <!-- codex-recurring-dataflow-decomposition-2026-07-28 -->
Author
Owner

Codex State: progress

The architecture decision and base contracts are complete:

  • Connectors acquires external data and publishes origins.
  • Datasources governs live/cached/static sources, staging, immutable/frozen
    states, schema, fingerprints, and reads.
  • Dataflow consumes Datasources and records pinned fingerprints.
  • Workflow now has a separate reusable graph library and validation contract.
  • A composed check proves Connector -> Datasources -> Dataflow preview/lineage.

Implemented in 8b1910b, 1cb6228, 27302f0, 6ca3058, 85eef00, and meta
commit 163b35c.

Remaining here: recurring scheduling, quality/approval gates, output
publication, durable run lifecycle, and audit-complete Workflow handoff.
Datasource tracking starts at
GovOPlaN/govoplan-datasources#1.

## Codex State: progress The architecture decision and base contracts are complete: - Connectors acquires external data and publishes origins. - Datasources governs live/cached/static sources, staging, immutable/frozen states, schema, fingerprints, and reads. - Dataflow consumes Datasources and records pinned fingerprints. - Workflow now has a separate reusable graph library and validation contract. - A composed check proves Connector -> Datasources -> Dataflow preview/lineage. Implemented in `8b1910b`, `1cb6228`, `27302f0`, `6ca3058`, `85eef00`, and meta commit `163b35c`. Remaining here: recurring scheduling, quality/approval gates, output publication, durable run lifecycle, and audit-complete Workflow handoff. Datasource tracking starts at https://git.add-ideas.de/GovOPlaN/govoplan-datasources/issues/1.
Author
Owner

Codex State: progress

Summary

  • The repository/module split is now implemented: Connectors owns external origins, Datasources owns governed identities/materializations/publication, Dataflow owns transformation definitions/runs, and Workflow owns orchestration definitions.
  • Core exposes neutral Datasource publication and Dataflow run lifecycle contracts in baa2143; meta composition coverage is 5b79e7d.

Verification

  • Contract scan passed (47 modules, 48 providers, 24 requirements); version alignment passed for 67 repositories.

Next / Blocked

  • Keep open for previewable publication diffs, Workflow reaction to warning/review/failure states, asynchronous large-result execution, and full operator-action audit coverage.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - The repository/module split is now implemented: Connectors owns external origins, Datasources owns governed identities/materializations/publication, Dataflow owns transformation definitions/runs, and Workflow owns orchestration definitions. - Core exposes neutral Datasource publication and Dataflow run lifecycle contracts in baa2143; meta composition coverage is 5b79e7d. ### Verification - `Contract scan passed (47 modules, 48 providers, 24 requirements); version alignment passed for 67 repositories.` ### Next / Blocked - Keep open for previewable publication diffs, Workflow reaction to warning/review/failure states, asynchronous large-result execution, and full operator-action audit coverage. Suggested status label: `status/in-progress`
Author
Owner

The Datasources/Dataflow split is now implemented: governed Datasource publication plus reusable Dataflow definitions, manual/scheduled/event trigger records, immutable revisions, lineage, diagnostics, and output publication are available in govoplan-datasources@6294362 and govoplan-dataflow@08ddc8d. Workflow reaction/manual approval still depends on the Workflow instance runtime; production-scale asynchronous transformation remains govoplan-dataflow#10.

The Datasources/Dataflow split is now implemented: governed Datasource publication plus reusable Dataflow definitions, manual/scheduled/event trigger records, immutable revisions, lineage, diagnostics, and output publication are available in govoplan-datasources@6294362 and govoplan-dataflow@08ddc8d. Workflow reaction/manual approval still depends on the Workflow instance runtime; production-scale asynchronous transformation remains govoplan-dataflow#10.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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