[Roadmap] Deliver governed dataflows, search, and established-tool integration #19

Open
opened 2026-07-29 15:43:23 +02:00 by zemion · 2 comments
Owner

Outcome

Track the agreed implementation sequence that turns the monthly-processing and sanctions-screening user stories into executable capabilities while preserving optional module boundaries.

Ordered work

  1. Document the integration maturity model and canonical external-reference contract.
  2. Turn the monthly workflow and sanctions screening into executable golden-flow fixtures with sample inputs and expected outputs.
  3. Resolve govoplan-dataflow#14 by making validators, executors, and compilers registry-driven.
  4. Add typed expressions, composite/parameterized templates, schema propagation, and quality/reconciliation operators.
  5. Deliver govoplan-search with PostgreSQL first and an optional OpenSearch adapter second.
  6. Build OpenProject as the first full connector, followed by a Znuny/OTRS-compatible service-desk adapter and MediaWiki/BlueSpice.

Third-party analytical execution engines and the Arrow execution adapter in govoplan-dataflow#15 are deliberately outside this sequence for now.

Tracking

  • Monthly flow: govoplan#8
  • Sanctions screening: govoplan#12
  • Dataflow registry debt: govoplan-dataflow#14
  • Dataflow reuse/governance: govoplan-dataflow#12
  • Search epic: govoplan-search#1
  • Integration epic: govoplan-connectors#11

Each child issue remains open until its own acceptance criteria are met; this issue records ordering and cross-repository status.

Architecture reconciliation (2026-07-31)

External references, registry-driven Dataflow internals, typed execution boundaries, PostgreSQL Search, golden flows, and the Workflow Engine/editor split are now implemented foundations. Remaining work should be read from the child issues and from GovOPlaN/govoplan#29, especially provider source-authority declarations, the governed data/register catalogue, target performance/recovery evidence, optional OpenSearch, and production connector acceptance. Do not reopen completed steps as greenfield work.

## Outcome Track the agreed implementation sequence that turns the monthly-processing and sanctions-screening user stories into executable capabilities while preserving optional module boundaries. ## Ordered work 1. Document the integration maturity model and canonical external-reference contract. 2. Turn the monthly workflow and sanctions screening into executable golden-flow fixtures with sample inputs and expected outputs. 3. Resolve `govoplan-dataflow#14` by making validators, executors, and compilers registry-driven. 4. Add typed expressions, composite/parameterized templates, schema propagation, and quality/reconciliation operators. 5. Deliver `govoplan-search` with PostgreSQL first and an optional OpenSearch adapter second. 6. Build OpenProject as the first full connector, followed by a Znuny/OTRS-compatible service-desk adapter and MediaWiki/BlueSpice. Third-party analytical execution engines and the Arrow execution adapter in `govoplan-dataflow#15` are deliberately outside this sequence for now. ## Tracking - Monthly flow: `govoplan#8` - Sanctions screening: `govoplan#12` - Dataflow registry debt: `govoplan-dataflow#14` - Dataflow reuse/governance: `govoplan-dataflow#12` - Search epic: `govoplan-search#1` - Integration epic: `govoplan-connectors#11` Each child issue remains open until its own acceptance criteria are met; this issue records ordering and cross-repository status. ## Architecture reconciliation (2026-07-31) External references, registry-driven Dataflow internals, typed execution boundaries, PostgreSQL Search, golden flows, and the Workflow Engine/editor split are now implemented foundations. Remaining work should be read from the child issues and from [GovOPlaN/govoplan#29](https://git.add-ideas.de/GovOPlaN/govoplan/issues/29), especially provider source-authority declarations, the governed data/register catalogue, target performance/recovery evidence, optional OpenSearch, and production connector acceptance. Do not reopen completed steps as greenfield work. <!-- codex-institutional-governance-data-integration-2026-07-31 -->
Author
Owner

Codex State: progress

Summary

  • Steps 1 and 2 are pushed: canonical integration contracts plus executable monthly and sanctions golden flows.
  • Steps 3 and 4 have first substantial slices: registry dispatch, typed safe expressions, conversion/replacement, quality/reconciliation, schema propagation, and parameterized pinned subflows.
  • Step 5 has a working PostgreSQL/SQLite Search baseline and shell UI; OpenSearch remains #3. Step 6 now has concrete connector work packages.

Next / Blocked

  • Continue Dataflow complexity decomposition (#14), complete Search ingestion lifecycle (#2), then start OpenProject connector #12.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Steps 1 and 2 are pushed: canonical integration contracts plus executable monthly and sanctions golden flows. - Steps 3 and 4 have first substantial slices: registry dispatch, typed safe expressions, conversion/replacement, quality/reconciliation, schema propagation, and parameterized pinned subflows. - Step 5 has a working PostgreSQL/SQLite Search baseline and shell UI; OpenSearch remains #3. Step 6 now has concrete connector work packages. ### Next / Blocked - Continue Dataflow complexity decomposition (#14), complete Search ingestion lifecycle (#2), then start OpenProject connector #12. Suggested status label: `status/in-progress`
Author
Owner

Status reconciliation — 2026-09-08

The next-step list in comment 15990 is superseded. Dataflow #14 is closed with registry dispatch/decomposition (69509d5); Dataflow #12 is closed with governed reusable/subflow definitions, current authorization, provenance and reviewed rebase (c1111c6, v0.1.20). Search #2 and Search #1 are closed: the PostgreSQL/SQLite baseline (a156e3d, Core 920e3c9) and durable ingestion/operator/query path (1bb3381, Core 7117673) are implemented. The 0.1.45 focused gate also passed the monthly-data and sanctions-review/rescreening fixtures.

Remaining ordered work belongs to Search #3 (optional OpenSearch), Connectors #12 (OpenProject), Connectors #11 (provider integrations), and named target/browser/operational acceptance under #8 and #12. Keep this roadmap open; do not restart completed foundations or treat fixture checks as production-provider approval.

<!-- govoplan-backlog-reconciliation-20260908-v1 --> ## Status reconciliation — 2026-09-08 The next-step list in comment 15990 is superseded. [Dataflow #14](https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/14) is closed with registry dispatch/decomposition (`69509d5`); [Dataflow #12](https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/12) is closed with governed reusable/subflow definitions, current authorization, provenance and reviewed rebase (`c1111c6`, v0.1.20). [Search #2](https://git.add-ideas.de/GovOPlaN/govoplan-search/issues/2) and [Search #1](https://git.add-ideas.de/GovOPlaN/govoplan-search/issues/1) are closed: the PostgreSQL/SQLite baseline (`a156e3d`, Core `920e3c9`) and durable ingestion/operator/query path (`1bb3381`, Core `7117673`) are implemented. The 0.1.45 focused gate also passed the monthly-data and sanctions-review/rescreening fixtures. Remaining ordered work belongs to [Search #3](https://git.add-ideas.de/GovOPlaN/govoplan-search/issues/3) (optional OpenSearch), [Connectors #12](https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/12) (OpenProject), [Connectors #11](https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/11) (provider integrations), and named target/browser/operational acceptance under #8 and #12. Keep this roadmap open; do not restart completed foundations or treat fixture checks as production-provider approval.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#19