Framework building-block map

Question and use cases

Six responsibility groups help locate a concern before choosing a project or package.

Use this matrix to find the framework building block that owns a concern before choosing a package.

Use the diagram during design review, incident diagnosis, code walkthroughs, and onboarding. It intentionally omits classes and projects unrelated to the focused question, so read it together with the source entry point and related topic pages.

This page covers only the named responsibilities and relationships; consult the relevant module documentation for capabilities not shown here.

Reading path

1. Step 1: Read rows as responsibility families, not deployment units.
2. Step 2: Read columns from policy and contracts toward adapters and generators.
3. Step 3: Use governance cells to see how architecture rules are enforced.

Do not skip arrow direction, numbering, or group titles: they express dependency or time direction, execution order, and responsibility boundaries. If the diagram differs from current source or accepted architecture decisions, correct the generated catalog immediately.

Legend and notation

This is a CAPABILITY MATRIX diagram. Use that form to understand the layout, then test your interpretation against the source facts below.

Key relationships and design meaning

Relationship 1

Source fact: Domain and application projects define policies and ports; infrastructure projects implement technology adapters.

Architectural meaning: Separating policy ownership from adapter implementation keeps technology projects replaceable and domain decisions discoverable.

Review action: Which project owns the contract and which project implements it?

Relationship 2

Source fact: Source generators cover DI, endpoints, modularity, persistence metadata, and query shapes.

Architectural meaning: Generators make repetitive wiring and metadata compile-time artifacts while leaving business behavior in ordinary code.

Review action: Can compile-time generation replace runtime discovery?

Relationship 3

Source fact: Architecture tests and governance generators enforce dependency boundaries.

Architectural meaning: Automated governance converts architecture conventions into failing evidence before a dependency violation reaches production.

Review action: Which test or generator prevents boundary erosion?

Design review questions

Answer each question when reviewing or implementing a related change. If code, tests, or an ADR cannot support the answer, do not decide from the diagram alone.

• Which project owns the contract and which project implements it?
• Can compile-time generation replace runtime discovery?
• Which test or generator prevents boundary erosion?

How to use the answers

1. Identify the single owner of the capability or rule.
2. Confirm that dependency, call, or event direction does not reverse ownership.
3. Capture the conclusion with an automated test or repeatable command.

Boundaries and common mistakes

Boundary 1

The matrix groups responsibilities, not NuGet package dependency direction.

• Do not infer: A connector in the diagram does not mean every implementation uses synchronous calls, a shared transaction, or shared data ownership.
• Review requirement: Can compile-time generation replace runtime discovery?

Boundary 2

Place a concern by ownership and policy before selecting a technology project.

• Do not infer: A connector in the diagram does not mean every implementation uses synchronous calls, a shared transaction, or shared data ownership.
• Review requirement: Which test or generator prevents boundary erosion?

Source verification and regeneration

The primary verification entry point is src/Framework project inventory. Inspect it and its direct references before regenerating diagram assets and pages.

# Regenerate bilingual SVG, standalone HTML, and documentation pages
npm run diagrams

# Check locale pairs, references, safety attributes, accessibility, and canvas bounds
npm run verify:diagrams

# Confirm that generation changed only the intended diagrams and pages
git diff -- scripts/diagrams diagram-sources public/diagrams src/content/docs

# Verify internal links, MDX structure, and professional depth gates
npm run verify:docs
npm run audit:docs-depth

Change-completion checklist

• Responsibilities, order, states, and relationships match current source.
• Every new element helps answer this page’s question instead of turning the diagram into an inventory.
• Arrows have explicit direction and semantics without implying nonexistent synchronous or transactional guarantees.
• Chinese and English titles, labels, facts, and boundaries remain semantically equivalent.
• The diagram remains readable on narrow screens, in fullscreen, and while zoomed, with no overlap or overflow.
• Relevant architecture tests, integration tests, or verification commands have run.
• If a long-lived constraint changed, its ADR or architecture documentation is updated.

Continue reading

• Architecture overview
• All architecture diagrams
• Platform modules