Reconcile product inputs and prove durable work handoffs

docs/REFERENCE_JOURNEY_PROGRAM.md

@@ -46,9 +46,11 @@ and archive-neutral package simulation. Forms Runtime, Cases, and Decisions
 expose exact, permission-rechecked source revisions for explicit filing, and
 all three contribute metadata-only native Search projections that can be
 rebuilt from authoritative state. The executable fixtures prove those native
-transitions without claiming archival custody. The journey still needs
-resumable user handoffs, pinned-composition reconstruction evidence, and one
-target-tested archive profile.
+transitions without claiming archival custody. A persisted Workflow Engine
+handoff is now reloaded through the Tasks aggregation surface and remains
+visible until the authoritative Workflow transition completes. The journey
+still needs pinned-composition reconstruction evidence and one target-tested
+archive profile.
 
 ## Why this sequence
 
@@ -124,6 +126,14 @@ journey needs and supplies contracts shared by all five stages.
     Module manifests state `contract_only`, `partial`, `enforced`, or
     `not_applicable` adoption with evidence; supported maturity is blocked until
     every applicable dimension is enforced.
+11. **Durable human work.** Tasks aggregates explicit work and module-owned
+    attention items; Workflow Engine persists process state and handoffs;
+    Notifications attracts attention; Views focuses the relevant surfaces.
+    Leaving or refreshing the browser never becomes the only record that work
+    remains unfinished.
+12. **Task-local tools.** Mail, Postbox, Templates, Files, and other common
+    actions may contribute bounded launch surfaces with return context. The
+    shell and Workflow compose them without copying their data or validation.
 
 ## Documentation contract for every reference stage