All 22 views are checked against current code or architecture rules and ship as independent bilingual SVG assets with full-screen zoom and source pointers. Open a card for the large view, verified facts, and common misreadings.
Core Architecture
System Overview
Runtime hosts, framework building blocks, representative platform modules, and external dependencies
View full pageModule Dependencies
Representative bounded contexts, Contracts boundaries, and reverse-dependency red lines
View full pageModule Dependency Stack
Protocol enters through the host and dependencies point toward use cases, domain contracts, and adapter ports; separate persistence models are explicit exceptions
View full pagePipelines & Flows
Mediator Behavior Order
The complete, fixed registration order of all fourteen composition-root pipeline behaviors
View full pageAuth & Authorization
Three-scheme authentication and the unified authorization decision service
View full pageEvent-Driven Architecture
CAP Outbox pattern for transactional event publishing
View full pageInfrastructure
Persistence Adapter Composition
SqlSugar or EF Core owns writes while Dapper complements query-oriented reads
View full pageAudit Categories, Tables, and Retention
Seven logical audit categories mapped to six base-table groups, sharding schedules, and default retention periods
View full pageLifecycle & Flows
Request Lifecycle
The full middleware order from ForwardedHeaders to endpoint dispatch, including tenant impersonation, output cache, and request timeouts
View full pageCAP Event Publish Sequence
Transactional outbox pattern with CAP dispatcher for reliable event publishing
View full pageTracker Item Lifecycle
The six TrackerItemStatus states and every transition permitted by TrackerItemTransitionRules
View full pageApplication Startup Sequence
API host boot sequence from WebApplicationBuilder to health-check ready
View full pageDomain & Data
Domain Entities and Persistence Exceptions
The default unified aggregate-root hierarchy and the explicit-asymmetry rule for separate persistence models
View full pageMulti-Tenant Resolution Chain
Eight-step priority-ordered chain of responsibility for tenant resolution
View full pageCommand and Query Responsibilities
Commands and queries enter the same fourteen-behavior chain, then use write and read ports respectively
View full pageExpected Failures and Unexpected Exceptions
Business failures remain Result data; only genuinely unexpected faults reach the exception handler
Structure & Organization
Building Blocks Responsibility Matrix
Major framework building blocks positioned by infrastructure, application, cross-cutting, and core responsibility
View full pageModule Internal Structure
Nested containment structure within a module showing layers and boundaries
View full pageDependency Injection Tree
DI registration hierarchy across the four composition root groups
View full pageModule Responsibility Map
Capability ownership follows bounded contexts instead of temporary organization structure
View full pageHost Technology Stack
Six-layer technology stack from HTTP endpoints down to external resources
View full pagePersistence Adapter Responsibilities
The adapters share application contracts but write providers and query adapters have different runtime roles
View full pageDesign system
All diagrams follow the same visual design system:
| Token | Value | Usage |
|---|---|---|
| Paper | #f5f5f5 | Warm white-smoke background |
| Ink | #2d3142 | Primary text and strokes |
| Accent | #eb6c36 | Focal elements (max 2 per diagram) |
| Muted | #4f5d75 | Secondary text and default arrows |
| Link | #2e5aa8 | HTTP/API calls, external systems |
Related
- Architecture overview — detailed prose documentation
- Modular monolith — module governance system
- Vertical Slice — internal module structure