Module responsibility map

Question and use cases

Responsibility belongs to bounded contexts; people and teams can change without moving the boundary.

Use this context map to assign capability ownership and design collaboration across boundaries.

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 each area as a stable business capability, not a current team name.
2. Step 2: Locate the owner of data and invariants before identifying consumers.
3. Step 3: Follow collaboration through contracts, ports, and events.

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 CONTEXT MAP 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: Identity, shared platform services, content flow, business services, and connectors have distinct bounded-context ownership.

Architectural meaning: Distinct capability ownership gives data, invariants, and contract approval a clear home even when delivery spans teams.

Review action: Who approves a contract change?

Relationship 2

Source fact: Cross-context collaboration happens through contracts, ports, or integration events.

Architectural meaning: Explicit collaboration mechanisms expose coupling and allow consumers to evolve without sharing private storage.

Review action: Can a consumer avoid direct access to the owner’s storage?

Relationship 3

Source fact: The capability boundary remains stable even when team assignments change.

Architectural meaning: Stable context boundaries protect the architecture from short-lived reporting-line or staffing changes.

Review action: Would a staffing change leave the capability boundary intact?

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.

• Who approves a contract change?
• Can a consumer avoid direct access to the owner’s storage?
• Would a staffing change leave the capability boundary intact?

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 diagram is a capability map, not an organization chart or current staffing record.

• 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 a consumer avoid direct access to the owner’s storage?

Boundary 2

Do not move a domain rule merely to follow a temporary team boundary.

• 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: Would a staffing change leave the capability boundary intact?

Source verification and regeneration

The primary verification entry point is src/Platform bounded-context 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