Onboarding guide

Phase 1b - Functional Group Taxonomy

This is the primary axis of the guide. Every one of the 5,512 distinct first-party type nodes from 00-inventory.md is assigned to exactly one functional group - its primary home: the capability or cross-cutting concern it most exists to serve. A type used across many groups (e.g. Result<T>, the entity base) lives in the one foundational group that owns it and is cross-linked from everywhere else.

Two axes work together. The top level (these groups, and the order of group-NN-*.md chapters) is functional. The ordering inside each group is by dependency Level (the longest-path layering computed in 00-dependency-manifest.md): within a chapter you meet a type only after the first-party types it depends on. Membership tables below are therefore sorted ascending by Level, then by name.

Group ordering runs roughly topologically over groups: foundational, widely-depended-on concerns first (Result -> domain blocks -> querying -> events -> CQRS -> ...), then the ASP.NET/UI/ Aspire edges, then the MMCA.ADC business modules that build on all of it, and finally the test infrastructure. Because MMCA.ADC consumes the MMCA.Common packages, Common-owned groups precede the ADC capabilities. Where a type must reference a first-party type whose home group appears later, that forward reference is allowed (functional cohesion can outrank strict progressive disclosure) and is cross-linked in the chapter.

Design notes (boundary decisions worth stating up front)

• Cycles are kept whole. The 13 dependency cycles (SCCs) from the manifest are never split across groups. Notably the ApplicationDbContext <-> AuditSaveChangesInterceptor <-> DomainEventSaveChangesInterceptor <-> DataSourceModelCacheKeyFactory cycle lives wholly in G07 Persistence, even though the domain-event interceptor conceptually belongs to events (G04) - it is cross-linked. The DDD aggregate nav-cycles (Event/Session/Speaker/Category) live in G17 Conference Domain.
• Soft-delete / audit / privacy is taught, not isolated. Rather than a thin group that would fragment the entity bases and the DbContext cycle, the data-lifecycle concern is taught where its machinery lives: the markers + audit fields + PiiAttribute + IAnonymizable in G02, the audit interceptor + soft-delete query filter + anonymization in G07, and GDPR export/erasure use cases in G23 Identity. ([Rubric S8, S30])
• ADC is grouped by bounded context (vertical slice), not by layer. Each ADC module spans Domain->Application->Infrastructure->API->UI; the large Conference module is split into five chapters (G17-G21) by layer for size, smaller modules (Engagement, Identity) are one chapter each. ADC implementations of Common patterns (a specific navigation populator, validator, mapper) stay in their module group and cross-link back to the Common pattern group.
• The Common UI framework is kept cohesive (G15). Auth/navigation/notification UI services under MMCA.Common.UI.* stay together as reusable UI building blocks and cross-link to the capability groups (G08/G10/G11), rather than being scattered.
• Notifications is one capability (G10) spanning Common Domain/Application/Infrastructure/API/ Shared plus the thin MMCA.ADC.Notification module host.
• Tests (G25). All *.Tests / *.IntegrationTests / *.E2E.Tests projects, the reusable MMCA.Common.Testing[.E2E|.UI] bases, and the component Gallery harness form one group. Per the TESTS note, individual [Fact]s are not sectioned; the chapter walks the reusable bases/ fixtures/builders and the architecture-fitness tests, and rolls the rest up by project. The full per-class list remains in 00-inventory.md. This is a logged exception.

The groups (ordered)

Reconciliation: 2375 production types across 27 groups + 3137 test/testing types in G25 = 5512 (matches the inventory's distinct-node count). No type appears twice; none dropped.

Group membership

G01 - Result & Error Handling

group-01-result-error-handling.md | 16 types | The Result/Error railway that every operation returns instead of throwing; pagination result shapes.

G02 - Domain Building Blocks (Entities, Value Objects, Aggregates)

group-02-domain-building-blocks.md | 36 types | The DDD primitives: entity/aggregate base classes, audit fields, value objects + invariants, domain markers, attributes, identifier aliases.

G03 - Querying: Specifications, Filtering & the Entity Query Service

group-03-querying-specifications.md | 42 types | Composable read-side: the Specification pattern, dynamic filtering/sorting/paging, and the generic entity query pipeline.

G04 - Domain & Integration Events + Outbox Dual-Dispatch

group-04-events-outbox.md | 38 types | Event contracts, the domain-event dispatcher, the transactional outbox/inbox, and the in-process + broker message buses.

G05 - CQRS: Commands, Queries & the Decorator Pipeline

group-05-cqrs-pipeline.md | 61 types | The command/query handler abstraction and the cross-cutting decorator pipeline (logging, transaction, caching, feature-gate, idempotency) wrapping it.

G06 - Validation

group-06-validation.md | 22 types | The FluentValidation-based validation contracts and failure mapping that gate commands before they execute.

G07 - Persistence & EF Core

group-07-persistence-ef-core.md | 181 types | The single SQLServerDbContext over the abstract ApplicationDbContext, interceptors, repositories, specifications evaluation, data-source routing (database-per-service), conventions, value generators, encryption, factories and design-time.

G08 - Authentication & Authorization

group-08-auth.md | 172 types | JWT/JWKS dual-fetch token validation, current-user/claims, password hashing, cookie sessions, and policy/authorization plumbing.

G09 - Caching

group-09-caching.md | 9 types | The cache abstraction and its decorator-driven, invalidation-aware integration into the query pipeline.

G10 - Notifications (Push + In-App Inbox + Email)

group-10-notifications.md | 59 types | The notification subsystem: push (SignalR), the in-app inbox, email sending, recipient providers, and the thin ADC Notification module host.

G11 - Navigation Metadata & Populators (EF-decoupled eager loading)

group-11-navigation-populators.md | 12 types | INavigationMetadata/INavigationPopulator and the loader that hydrate cross-container/cross-source relationships without EF Include coupling (ADR-002).

G12 - API Hosting, Middleware, Idempotency & DTO/Contract Mapping

group-12-api-hosting-mapping.md | 92 types | The ASP.NET Core edge: controller bases, middleware, startup, model binders, JSON converters, feature management, idempotency, correlation, and manual DTO/request mapping.

G13 - gRPC & Inter-Service Contracts

group-13-grpc-contracts.md | 7 types | Typed gRPC clients/servers, interceptors, Result-over-the-wire, and the ServiceContract marker for synchronous inter-service calls (ADR-007).

G14 - Module System, Composition & Configuration

group-14-module-system-composition.md | 90 types | IModule discovery + Kahn-ordered ModuleLoader, the DI composition roots, assembly markers, data-source/database attributes, and options/settings binding.

G15 - Common UI Framework (MudBlazor components, theme, base pages)

group-15-common-ui-framework.md | 195 types | Reusable Blazor building blocks: the data-grid list page base, theme, common pages/services, and UI extensions shared by every consumer app.

G16 - Aspire Orchestration & Service Defaults

group-16-aspire-orchestration.md | 63 types | The Aspire AppHost wiring, ServiceDefaults, warmup, telemetry and security helpers that compose and run the distributed app locally and in Azure.

G17 - ADC Conference - Domain Model & Module Contracts

group-17-conference-domain.md | 112 types | The Conference bounded context: Event/Session/Speaker/Category/Question aggregates, their domain events and invariants, plus the Shared identifiers/DTOs/integration-event contracts.

G18 - ADC Conference - Application & Use Cases

group-18-conference-application.md | 364 types | Conference CQRS handlers, validators, DTOs, specifications, the Sessionize import, and the session-selection decision-support analytics.