Inside a bounded context

Question and use cases

Public contracts, domain rules, use cases, adapters, endpoints, and tests stay physically visible.

Use this module map when creating a vertical slice or reviewing misplaced code.

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: Identify public contracts before entering private implementation details.
2. Step 2: Trace a use case through endpoint, application slice, domain, and adapter ports.
3. Step 3: Treat tests as boundary evidence across these responsibilities.

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 MODULE 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: Contracts, domain rules, application slices, infrastructure adapters, endpoints, and tests remain physically distinct.

Architectural meaning: Physical separation keeps public API, policy, orchestration, technology, protocol, and evidence independently navigable.

Review action: Can a maintainer find request, handler, validator, and tests by feature?

Relationship 2

Source fact: A vertical slice keeps request, handler, validator, and nearby policy code easy to navigate.

Architectural meaning: Feature-local slices reduce the number of unrelated folders a maintainer must traverse to understand one use case.

Review action: Does an endpoint contain business branching?

Relationship 3

Source fact: Endpoints and adapters depend on application-facing contracts, not the reverse.

Architectural meaning: Inward-facing contracts prevent endpoints and adapters from becoming the source of business rules.

Review action: Does an adapter define policy that belongs in domain or application code?

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.

• Can a maintainer find request, handler, validator, and tests by feature?
• Does an endpoint contain business branching?
• Does an adapter define policy that belongs in domain or application code?

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 boxes are sibling responsibilities inside one boundary, not independent deployable services.

• 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: Does an endpoint contain business branching?

Boundary 2

Avoid generic Services folders that hide use-case ownership.

• 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: Does an adapter define policy that belongs in domain or application code?

Source verification and regeneration

The primary verification entry point is .ai/constraints/architecture-rules.md. 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