Integrate Quick Access product presentation

docs/PLATFORM_CORE_IDEAS.md

@@ -75,6 +75,12 @@ surfaces may hide irrelevant functions, but they never grant access. Users can
 escape a focused mode when policy permits and can always understand why
 something is unavailable.
 
+Configurable product areas organize authorized capabilities around work,
+services, records, communication, meetings, data and institutional
+responsibility. The optional Quick Access rail presents task-local Work,
+Calendar, Messages and Files contributions without merging their owners or
+turning presentation settings into permissions.
+
 ### 8. Evidence and recovery are part of the operation
 
 Intent, exact input versions, approvals, external effects, receipts,
@@ -146,6 +152,11 @@ package coordinates, and schema details are technical provenance. They are
 visible to administrators and in expandable diagnostics, but they are not the
 primary information architecture for ordinary work.
 
+The complete permission-derived tool catalogue remains deliberately available
+to power users. Product areas and Quick Access provide sensible system and
+tenant defaults plus governed user personalization; they do not make familiar
+tools harder to reach merely to conceal modular implementation.
+
 ## Maturity Rule
 
 A repository, route, model, or unit test does not make a capability complete.