Reconcile product inputs and prove durable work handoffs

packages/govoplan-meta/pyproject.toml

@@ -72,6 +72,7 @@ full = [
   "govoplan-search==0.1.18",
   "govoplan-services==0.1.18",
   "govoplan-soap==0.1.18",
+  "govoplan-tasks==0.1.18",
   "govoplan-templates==0.1.18",
   "govoplan-tickets==0.1.18",
   "govoplan-transparency==0.1.18",

packages/product/governed-communication/README.md

@@ -28,5 +28,7 @@ The artifact remains a `product` package. Promotion to `reference` requires:
   access; and
 - version-pinned user and administrator documentation.
 
-Optional Notifications, Portal, Reporting, and Workflow Engine integrations do
-not change the package boundary when absent.
+Optional Notifications, Portal, Reporting, Tasks, and Workflow Engine
+integrations do not change the package boundary when absent. When Tasks is
+present, acknowledgement, reconciliation, and operator intervention remain
+owned by their source modules and are projected into the common work inbox.

packages/product/governed-communication/package.json

@@ -21,6 +21,7 @@
     {"module_id": "notifications"},
     {"module_id": "portal"},
     {"module_id": "reporting"},
+    {"module_id": "tasks"},
     {"module_id": "workflow_engine"}
   ],
   "evidence": [

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

@@ -37,8 +37,10 @@ The artifact remains a `product` package. Promotion to `reference` requires:
   aggregate disclosure; and
 - version-pinned user and administrator documentation.
 
-Optional Connectors, Files, Notifications, and Workflow Engine integrations
-must remain capability-based and absence-safe.
+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
 

packages/product/governed-data-assurance/package.json

@@ -21,6 +21,7 @@
     {"module_id": "connectors"},
     {"module_id": "files"},
     {"module_id": "notifications"},
+    {"module_id": "tasks"},
     {"module_id": "workflow_engine"}
   ],
   "evidence": [

packages/product/service-to-decision/README.md

@@ -33,6 +33,11 @@ values, evidence payloads, Decision reasoning, operative results, and
 conditions are excluded; every candidate is authorized again before it is
 shown.
 
+When Tasks is present, explicit work and source-owned Workflow handoffs appear
+in one resumable inbox with typed account, group, role, function, or assignment
+responsibility. Workflow Engine retains process state and completion commands;
+Tasks retains only explicit tasks and the aggregation surface.
+
 ## Security And Recovery
 
 Every provider is tenant-bound. Missing or conflicting authority fails closed.
@@ -46,9 +51,11 @@ The executable fixture in
 `tests/test_institutional_governance_journey.py` proves SQL-backed Service,
 Case, Party, Mandate, Committee meeting/agendum/vote/minute, and Decision state.
 `tests/test_institutional_service_journey.py` separately proves exact Portal
-Form launch, persisted submission provenance, and idempotent replay.
+Form launch, persisted submission provenance, idempotent replay, and a durable
+Workflow handoff that remains visible through Tasks after the database session
+is reopened and disappears only after the Workflow Engine records completion.
 Module-level Records source tests prove exact Form submission, Case revision,
 and Decision revision filing. Target-environment browser accessibility,
-resumable work guidance, production identity and delivery, a named archive
-profile, and recovery evidence are still required before this product package
-may claim `reference_ready` maturity.
+production identity and delivery, a named archive profile, and recovery evidence
+are still required before this product package may claim `reference_ready`
+maturity.