dotnet-architecture (decision hub)

Decide the shape, then load the one style you chose. Per-style depth lives in references - load exactly the ones your decision selects:

• Layered internal structure -> references/clean-architecture.md
• Feature-sliced internal structure -> references/vertical-slice.md
• Rich domain (aggregates, invariants) -> references/ddd.md (additive - layers onto clean or vsa, does not replace it)
• Distinct bounded contexts in one deployable -> references/modular-monolith.md
• Independently deployed/scaled boundaries -> references/microservices.md

Pick one, then commit

• One internal style per codebase (or per module). Clean and vertical-slice side by side means neither - a reader can't predict where anything lives.
• In an established codebase the existing architecture wins. Match it exactly; never introduce a 'better' second pattern.
• Greenfield is a deliberate choice. Load one style reference and build to it.

Decide on two axes (plus one additive)

Topology - how many deployables, where the boundaries are. Default to the least distributed thing that works: