Reconcile product inputs and prove durable work handoffs

docs/STRATEGY_STATUS.md

@@ -7,6 +7,7 @@
 | Reconciled on | 2026-08-06 |
 | Source scope | Local workspace manifests, source inventory, focused journey checks, signed release evidence, and live Gitea issue state |
 | Stable direction | [Platform Core Ideas](PLATFORM_CORE_IDEAS.md) and [Connected Governance Platform Roadmap](CONNECTED_GOVERNANCE_PLATFORM_ROADMAP.md) |
+| Collected product input | [Product Input Register](PRODUCT_INPUT_REGISTER.md) |
 | Delivery source | Gitea issues |
 
 This is the only prose source for current cross-product status. It is a
@@ -15,8 +16,8 @@ evidence remain authoritative for specific maturity claims.
 
 ## Portfolio Snapshot
 
-- 65 source module manifests were loadable and architecture-declared.
-- 47 modules declared `vertical_slice`; 18 declared `scaffold`.
+- 66 source module manifests were loadable and architecture-declared.
+- 48 modules declared `vertical_slice`; 18 declared `scaffold`.
 - No module declared `reference_ready`, `supported`, or `lts`.
 - The live portfolio had 133 open issues, including 39 priority-P1 items.
 - 117 open issues had no milestone, so issue labels do not yet express a
@@ -30,19 +31,20 @@ document.
 
 ## Interface And Contract Evidence
 
-The 2026-08-05 source inventory found:
+The 2026-08-06 source inventory found:
 
-- 1,247 UI fields and 1,220 UI actions;
-- 7,929 stable interface declarations with no duplicate IDs;
-- 39 frontend routes and 872 backend endpoints;
+- 1,307 UI fields and 1,291 UI actions;
+- 8,157 stable interface declarations with no duplicate IDs;
+- 43 frontend routes and 920 backend endpoints;
 - no public WebUI surfaces missing runtime declarations;
 - no stale runtime route declarations;
 - no unclassified endpoint without a static UI reference;
-- all 1,247 fields with a resolvable F1 context; 1,087 remain candidates for
+- all 1,307 fields with a resolvable F1 context; 1,143 remain candidates for
   richer field-specific content beyond page/module fallback;
 - German (`de`) as the complete reference locale and no used key missing from
   the required German or English catalogs;
-- 260 module information-governance dimensions classified as `contract_only`.
+- 3 module information-governance dimensions classified as `enforced`, 1 as
+  `partial`, and 260 as `contract_only`.
   This is an honest platform-wide baseline, not a claim that temporal,
   purpose, retention, and institutional-context adoption is complete.
 
@@ -70,24 +72,28 @@ Voting, Decisions, Portal, Postbox, and Audit have an executable service-to-
 decision fixture. Public and invitation intake can retain Files-backed
 evidence; Forms submissions, Cases, and formal Decisions can be explicitly
 filed as exact eAkte source revisions and reconstructed through permission-
-rechecked native Search projections. Browser-complete assisted intake,
-resumable work guidance, production identity and delivery, a named archive
-profile, and target evidence remain.
+rechecked native Search projections. A durable Workflow Engine handoff now
+survives session restart and appears through the Tasks work inbox until the
+authoritative transition completes. Browser-complete assisted intake, broader
+work projections and escalation, production identity and delivery, a named
+archive profile, and target evidence remain.
 
 ### Governed data and assurance
 
 Connectors, Datasources, Dataflow, Reporting, Search, Policy, Risk Compliance,
 and Workflow provide source governance, immutable snapshots, transformation,
 quality, semantic reporting, and provenance foundations. The monthly-data and
-sanctions journeys still need real connectors, complete interactive
-reconciliation, publication/export, and guided handoff evidence.
+sanctions compositions now prove immutable connector snapshots, pinned
+Dataflow publication, Risk Compliance review, and rescreening in process. The
+journeys still need target connector profiles, complete interactive
+reconciliation, governed export/delivery, and browser-level handoff evidence.
 
 ## Material Gaps
 
 | Gap | Consequence | Next proof |
 | --- | --- | --- |
 | No reference-ready product package | The platform cannot yet make a bounded supported-product claim | Complete one named target composition and evidence bundle |
-| Human-work spine incomplete | Users still navigate modules and remember unfinished work | Task/work inbox, resumable guided journey, deadlines and handoffs |
+| Human-work spine is only an MVP | Tasks aggregates explicit work plus Workflow, Approval, and unread Postbox projections, but broad domain coverage, deadline escalation, assignment lifecycle, and focused product UX remain | Extend source providers through the three reference journeys and prove overdue/reassignment behavior in browser tests |
 | Records/eAkte target integration incomplete | Native lifecycle, retention, holds, approval, recovery, and transfer simulation are implemented, but real custody is not proved | Target-test one archive/xdomea profile and complete the assisted reference journey |
 | Cross-cutting governance adoption uneven | Historical and purpose-sensitive behavior varies by module | Enforced adoption declarations and route/query/effect migration |
 | Explicit help/accessibility depth incomplete | German/reference and F1 association gates now pass, but generic fallback remains too common | High-risk German help content and browser/a11y matrix |
@@ -103,9 +109,11 @@ reconciliation, publication/export, and guided handoff evidence.
    sanctions screening.
 4. Complete the browser and resumable-work proof for the digital and assisted
    service-to-decision journey with its existing exact eAkte filing contracts.
-5. Extend native PostgreSQL search coverage from the implemented service-to-
-   decision objects to the communication and monthly-data journeys; keep
-   OpenSearch optional.
+5. Complete native PostgreSQL search coverage for remaining journey-owned
+   objects and prove reauthorization and reindex operations at target volume;
+   keep OpenSearch optional. Communication, Records, service-to-decision,
+   Dataflow, Reporting, Risk Compliance, and Datasource catalogue sources now
+   exist.
 6. Prove one external product connector and one GovOPlaN federation exchange.
 7. Finish multi-host, restore, provider, accessibility, and independent signed
    target evidence before increasing maturity claims.