Reconcile product inputs and prove durable work handoffs

docs/PLATFORM_CORE_IDEAS.md

@@ -61,6 +61,12 @@ next responsible action, reason, deadline, consequence, and completion
 evidence. Workflow Engine coordinates machine and human transitions; focused
 views guide people through the relevant platform surfaces.
 
+Tasks owns explicit work items and the unified work inbox. Workflow Engine owns
+process execution and resumable handoffs. Notifications attract attention, and
+domain modules retain their business objects. These boundaries prevent an
+inbox, workflow, or notification from becoming a second copy of institutional
+state.
+
 ### 7. Views reduce complexity without changing authority
 
 The interface is a task- and role-sensitive projection of installed
@@ -84,6 +90,11 @@ records who entered information, for whom, from which source, with which
 attestation, and how the affected person receives a usable receipt and
 correction path.
 
+Responsive, mobile, desktop, and embedded launch surfaces are additional ways
+to enter the same governed context, not separate products with weaker authority
+or evidence. Common task-local actions may open in bounded overlays while their
+owning modules retain validation, policy, and persistence.
+
 ### 10. Successful configurations are portable products
 
 Modules are ingredients. A usable product is a signed configuration package
@@ -106,6 +117,10 @@ deployment tiers.
 | Data and integration | Connectors, datasources, dataflow, search, external references, provider health, and reconciliation |
 | Runtime and assurance | Module composition, operations, deployment, recovery, security evidence, and signed packages |
 
+Collected product ideas and normalized actor outcomes are preserved in the
+[Product Input Register](PRODUCT_INPUT_REGISTER.md). They enter implementation
+only through a named journey, package, or explicit discovery issue.
+
 ## Canonical Distinctions
 
 The platform must not collapse these pairs:
@@ -170,4 +185,3 @@ institutional journey and can answer:
 6. How can it operate with an external owner without losing autonomy?
 7. How will a person discover and complete it without learning the module
    graph?
-