Project pending approvals as authorized work

docs/APPROVALS_DOMAIN_BOUNDARY.md

@@ -26,6 +26,12 @@ signature reference; Approvals does not implement document signing or key
 custody. A fail-fast rejection ends the request. Due steps can enter an
 explicit escalated state without silently changing their outcome.
 
+When Tasks is enabled, Approvals projects only currently actionable steps into
+the common work inbox. The projection applies the same selector, expiration,
+prior-decision, unique-actor, evidence-role, and requester-separation checks as
+the decision command. Approvals remains the owner of decision and completion
+state; Tasks receives no copied approval record.
+
 ## Recovery and scale-out
 
 All API and worker nodes use the logically shared database. Back up and restore
@@ -44,7 +50,8 @@ database and reconcile every module object that retains an Approval reference.
 
 ## Optional integrations
 
-Workflow Engine may wait for completion and Notifications may announce an
-assignment, due date, escalation, or outcome. Audit may retain additional
-cross-domain evidence. Policy may provide chain templates. These integrations
-use capabilities and events; none reads Approval tables directly.
+Workflow Engine may wait for completion, Tasks may aggregate actionable work,
+and Notifications may announce an assignment, due date, escalation, or
+outcome. Audit may retain additional cross-domain evidence. Policy may provide
+chain templates. These integrations use capabilities and events; none reads
+Approval tables directly.