[Feature] Publish governed datasets for Reporting and export #8

Closed
opened 2026-07-28 00:58:09 +02:00 by zemion · 2 comments
Owner

Parent: #1

Define versioned output dataset references that Reporting can consume without importing Dataflow internals. Publication records schema, lineage, quality state, access policy, retention, and the exact successful run.

Parent: https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/1 Define versioned output dataset references that Reporting can consume without importing Dataflow internals. Publication records schema, lineage, quality state, access policy, retention, and the exact successful run.
Author
Owner

Codex State: progress

Summary

  • Dataflow outputs are pinned to immutable Datasource materialization references with producer run, fingerprint, schema, provenance, governance snapshot, and deterministic quality validation evidence.
  • Failed governance validation creates no target datasource, materialization, or publication ledger record; successful publication is idempotent and emits terminal transactional evidence.

Verification

  • Connector -> Datasources -> pinned Dataflow publication composition and 79 Dataflow tests passed.

Next / Blocked

  • Keep open for explicit consumer-facing output compatibility/version policy, durable large artifact references, and Reporting-specific consumption verification.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Dataflow outputs are pinned to immutable Datasource materialization references with producer run, fingerprint, schema, provenance, governance snapshot, and deterministic quality validation evidence. - Failed governance validation creates no target datasource, materialization, or publication ledger record; successful publication is idempotent and emits terminal transactional evidence. ### Verification - `Connector -> Datasources -> pinned Dataflow publication composition and 79 Dataflow tests passed.` ### Next / Blocked - Keep open for explicit consumer-facing output compatibility/version policy, durable large artifact references, and Reporting-specific consumption verification. Suggested status label: `status/in-progress`
Author
Owner

Codex State: done

Summary

  • Reporting can now pin an exact successful Dataflow run and consume only its immutable Datasource materialization without re-execution or reparameterization.
  • The consumer contract pins pipeline revision and definition hash, rechecks both Dataflow authority and current Datasource access, verifies source fingerprints, and returns run/publication/materialization/governance provenance.

Changed Files

  • src/govoplan_dataflow/backend/dataset_output.py
  • tests/test_dataset_output.py

Verification

  • Dataflow: 79 passed.
  • Reporting: 12 passed, including public report execution against an exact published run.
  • Full focused platform check passed.

Next / Blocked

  • Large-output object storage remains tracked by Datasources #3 rather than this consumer contract.
## Codex State: done ### Summary - Reporting can now pin an exact successful Dataflow run and consume only its immutable Datasource materialization without re-execution or reparameterization. - The consumer contract pins pipeline revision and definition hash, rechecks both Dataflow authority and current Datasource access, verifies source fingerprints, and returns run/publication/materialization/governance provenance. ### Changed Files - `src/govoplan_dataflow/backend/dataset_output.py` - `tests/test_dataset_output.py` ### Verification - `Dataflow: 79 passed.` - `Reporting: 12 passed, including public report execution against an exact published run.` - `Full focused platform check passed.` ### Next / Blocked - Large-output object storage remains tracked by Datasources #3 rather than this consumer contract.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-dataflow#8