[Epic] Deliver reproducible sanctions and embargo screening with human review #2

Open
opened 2026-07-28 00:58:10 +02:00 by zemion · 0 comments
Owner

Outcome

Implement the domain capability specified by the product user story. Screening assists governed decisions; it never presents fuzzy matching as a legal conclusion.

Boundary

Risk Compliance owns normalized list records, subject snapshots, screening runs, candidate explanations, review dispositions, exceptions, freshness/reconciliation, and policy gates. Connectors owns source acquisition. Dataflow may normalize and compare tabular data but does not own legal dispositions. Audit, Policy, Records, Notifications, and consuming modules integrate through versioned capabilities.

Release Plan

  1. Immutable source/list snapshot model and synthetic fixture ingestion.
  2. Deterministic normalization and candidate matching with explainable evidence.
  3. Reviewer queue and dispositions with separation of duties.
  4. Freshness, rescreening, exceptions, and explicit consumer gates.
  5. Approved live-source connector rollout and operational acceptance.

Release Gate

All acceptance criteria in the product story remain binding. Live data is blocked until authoritative sources, licensing, privacy/retention, thresholds, reviewer authority, and consuming contexts are approved; synthetic implementation work may proceed immediately.

Connector work: GovOPlaN/govoplan-connectors#10
Dataflow foundation: GovOPlaN/govoplan-dataflow#1

## Outcome Implement the domain capability specified by [the product user story](https://git.add-ideas.de/GovOPlaN/govoplan/issues/12). Screening assists governed decisions; it never presents fuzzy matching as a legal conclusion. ## Boundary Risk Compliance owns normalized list records, subject snapshots, screening runs, candidate explanations, review dispositions, exceptions, freshness/reconciliation, and policy gates. Connectors owns source acquisition. Dataflow may normalize and compare tabular data but does not own legal dispositions. Audit, Policy, Records, Notifications, and consuming modules integrate through versioned capabilities. ## Release Plan 1. Immutable source/list snapshot model and synthetic fixture ingestion. 2. Deterministic normalization and candidate matching with explainable evidence. 3. Reviewer queue and dispositions with separation of duties. 4. Freshness, rescreening, exceptions, and explicit consumer gates. 5. Approved live-source connector rollout and operational acceptance. ## Release Gate All acceptance criteria in the product story remain binding. Live data is blocked until authoritative sources, licensing, privacy/retention, thresholds, reviewer authority, and consuming contexts are approved; synthetic implementation work may proceed immediately. Connector work: https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/10 Dataflow foundation: https://git.add-ideas.de/GovOPlaN/govoplan-dataflow/issues/1
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-risk-compliance#2
No description provided.