The core components: a selected toolkit

Build a small shared vocabulary that a human and an agent can both hold.

Keep commands, events, and queries separate to buy cheap clarity throughout the system.

A handler coordinates one behavior through ports; it does not make the domain decision.

Use an aggregate as the transactional boundary that makes invariants structurally impossible to break.

Separate objects with durable identity from immutable values defined by their attributes.

Put genuine cross-aggregate domain decisions in a domain service.

Ports are interfaces the core owns; adapters are implementation details outside the core vocabulary.

Keep a read shape for answering questions separate from the write shape that guards rules.

Put the vocabulary together on one feature and the flow becomes precise.

Translate features into precise component words so the agent has fewer gaps to guess into.