govoplan/packages/product/governed-data-assurance/README.md

Governed Data and Assurance Product Package

This package composes Datasources, Dataflow, Reporting, Search, Risk Compliance, Policy, Audit, and Access. Connectors may acquire external data, but Datasources owns the governed catalogue and immutable snapshots; Dataflow owns transformation definitions and runs; Reporting owns measures and presentation; Risk Compliance owns controls, findings, and effectiveness review.

Reference journey

1. Register a typed datasource with source authority, purpose, classification, owner, freshness, and correction policy.
2. Acquire or upload an immutable source state.
3. Execute a versioned flow and retain intermediate materializations and provenance;
4. publish a report or decision input against exact source and flow revisions;
5. link obligation, governed object, risk, control, evidence, finding, corrective measure, and effectiveness review; and
6. search current authorized objects while preserving ownership and access rechecks.

Reference-readiness gates

The artifact remains a product package. Promotion to reference requires:

• a target-tested monthly-data and sanctions-screening fixture with expected outputs and complete provenance;
• database/object-storage backup and restore plus interrupted-run recovery;
• security evidence for datasource credentials, staged data, intermediate states, search documents, and assurance references;
• operator runbooks for stale sources, failed runs, index rebuilds, and graph reconciliation;
• accessibility evidence for the catalogue, graph editors, result inspection, reports, and assurance graph;
• privacy evidence for minimization, purpose, retention, field visibility, and aggregate disclosure; and
• version-pinned user and administrator documentation.

Optional Connectors, Files, Notifications, Tasks, and Workflow Engine integrations must remain capability-based and absence-safe. Tasks may present review and recovery handoffs, but Dataflow and Risk Compliance remain the authoritative owners of run and screening state.

Executable evidence

• tools/checks/check-datasource-composition.py composes Connector snapshots, governed Datasources, queued Dataflow execution, frozen publication, idempotent replay, and recovery evidence.
• govoplan-dataflow/fixtures/golden/monthly-reconciliation pins synthetic monthly inputs, stable reconciliation hashes, reviewed decisions, expected output, source fingerprints, and output hashes.
• tools/checks/check-sanctions-screening-composition.py composes an immutable Connector acquisition, idempotent Risk Compliance import and screening, independent disposition, a cleared gate, changed-source invalidation, and the rescreening queue through the registered versioned capabilities.
• govoplan-dataflow/fixtures/golden/sanctions-screening independently proves the deterministic normalization and matching graph with exact expected output.

These checks use synthetic data and run without network access. They prove the module contracts and durable state transitions; they do not replace the deployment, security, privacy, accessibility, and operator evidence still listed above.