Architecture Guidance

Priorities

Preserve authoritative ownership, inward dependencies, explicit resource lifecycles, and traceable workflows using the least structural machinery that makes them clear. Hide implementation details, expose obligations, and make composition explicit. DDD building blocks are tools, not a checklist. A responsibility does not imply its own directory, file, type, interface, representation, or runtime hop. Small size does not excuse infrastructure coupling or misplaced rules; large size does not justify forwarding layers without behavior.

Load the applicable language practices skill before committing to language-specific organization or implementation decisions. Load dependency-approval before selecting a new dependency. If required guidance is unavailable, report the gap before making the affected decision; do not invent its policy.