Reconcile product inputs and prove durable work handoffs

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.