feat: enforce shared UI foundations and pin reference journey

docs/architecture/QUICK_ACCESS_AND_PRODUCT_AREAS.md

@@ -41,12 +41,15 @@ The first production-shaped slice is implemented:
 - the expanded left rail groups classified destinations while retaining
   Dashboard and every authorized unclassified destination under More tools.
 
-The remaining rollout is classification rather than a missing boundary: other
-user-facing modules must announce their product areas and future bounded tools,
-reference journeys need browser accessibility evidence, and richer active-object
-context should be added only through a separately versioned launch-context
-contract. Until classification is complete, authorized unclassified routes
-remain visible rather than disappearing.
+The baseline classification is now manifest-declared for every ordinary
+user-facing module and enforced by the workspace manifest check. A separately
+versioned launch-context contract carries bounded active-object, acting,
+temporal, View and return references into full-page Quick Access fallbacks;
+Cases publishes the first active-object reference. The remaining rollout is to
+add useful bounded tools and active-object publishers only where a maintained
+journey benefits, and to extend browser evidence to a pinned reference
+composition. Authorized global and technical routes remain visible through
+their dedicated shell entry or **All available tools**.
 
 ## Quick Access Boundary
 
@@ -150,6 +153,25 @@ Familiar product nouns such as Calendar, Mail or Files may remain directly
 pinned. The objective is not to hide every module name; it is to prevent
 repository topology from determining a person's workflow.
 
+The initial module classification is deliberately outcome-oriented:
+
+| Product area | Contributing user-facing modules |
+| --- | --- |
+| Work | Approvals, Projects, Tasks, Workflow |
+| Services and Cases | Cases, Forms, Forms Runtime, Portal |
+| Records and Documents | Files, Records, Templates |
+| Communication | Campaigns, Distribution Lists, Mail, Notifications, Postbox |
+| Meetings and Decisions | Calendar, Committee, Scheduling, Voting |
+| Data and Assurance | Dataflow, Datasources, Reporting, Risk Compliance |
+| People and Responsibility | Address Book, IDM, Organizations |
+
+Dashboard, Search, Documentation and Quick Access remain global shell
+affordances. Access, Administration, Audit, Encryption, Identity Trust,
+Operations, Policy, Tenancy and Views remain administrative or platform
+surfaces available through their dedicated entry point or **All available
+tools**. The manifest-shape check enforces both this explicit exception set and
+the shared label, icon, description and ordering of every canonical area.
+
 ## Full Access And Provenance
 
 The existing permission-derived module rail remains available as **All