Integrate Quick Access product presentation

docs/PRODUCT_EXPERIENCE_AND_MODULE_BOUNDARIES.md

@@ -15,6 +15,8 @@ contributions.
 
 Implementation is tracked in
 [Core #283](https://git.add-ideas.de/GovOPlaN/govoplan-core/issues/283).
+The accepted configurable product-area and task-local tool design is defined
+in [Quick Access And Product Areas](QUICK_ACCESS_AND_PRODUCT_AREAS.md).
 
 ## Current Exposure Inventory
 
@@ -80,6 +82,22 @@ The default shell should prioritize:
 4. pinned user destinations;
 5. administration and technical module inspection when authorized.
 
+The baseline product areas are Work, Services and Cases, Records and
+Documents, Communication, Meetings and Decisions, Data and Assurance, and
+People and Responsibility. They are configurable system/tenant defaults and
+Views projections, not hard-coded repository groups. Empty areas disappear;
+single-destination areas may link directly; familiar tools may remain pinned.
+
+The complete permission-derived module rail remains available as **All
+available tools**. Its ability to scroll is useful and is not itself the
+product defect. The defect is requiring people to infer a task or outcome from
+repository topology.
+
+Task-local Work, Calendar, Messages and Files tools may be contributed to the
+optional `govoplan-quick-access` rail. Messages composes Mail, Postbox and
+future governed chat presentation without merging their channel semantics or
+state.
+
 A module route remains a valid deep link. A product area may combine links and
 owner-rendered surfaces from several modules. When a required contribution is
 absent, the area explains the missing outcome rather than rendering a broken
@@ -106,6 +124,12 @@ hiding operational truth.
 
 ## Migration
 
+Core's product-area and Quick Access contracts, the optional Quick Access
+module, the first five providers and immutable View presentation revisions are
+implemented. The migration below now concerns broader classification and
+product-language adoption; it is not a prerequisite for safely enabling the
+first rail slice.
+
 ### Slice 1: inventory and aliases
 
 - classify every route, navigation item, widget, setting, search object, and
@@ -119,6 +143,8 @@ hiding operational truth.
 - make work areas and configured packages the default navigation;
 - move the complete module catalogue to administration and an optional power-
   user surface.
+- implement the configurable Quick Access rail through Core-mediated
+  contributions, system/tenant/user resolution and View/Policy ceilings.
 
 ### Slice 3: composite journeys