architect

Bounded contexts partition the system into well-defined domains with explicit ownership, clarifying interfaces and reducing drift between design and implementation. This mapping defines clear boundaries for data flow delineation and cross-context handoffs.

Contract-based architecture design defines explicit input, output, and error shapes for cross-context interactions to ensure design fidelity before implementation. You need it when system design requires strict integration contracts and clear ownership delineation across multiple bounded contexts.

Generating an architecture document requires translating feature requirements into bounded contexts, explicit contracts, and stack-aware references. This process produces architecture artifacts that guide downstream implementers and surfaces open questions requiring stakeholder decisions prior to coding.

Yes, this architecture design approach works without writing code by enforcing design discipline and producing architecture documents instead of implementations. It focuses entirely on system design artifacts, data flow delineation, and surfacing open questions for stakeholder input.

The best way to surface open questions during system design is translating feature requirements into bounded contexts and explicit contracts, which identifies missing decisions requiring stakeholder input. This surfaces gaps in integration contracts and cross-context handoffs before implementation starts.

You should avoid bounded context mapping when feature requirements lack sufficient clarity for domain partitioning, or when system design scope does not involve complex cross-context interactions. Without explicit integration contracts and data flow delineation needs, the overhead outweighs the benefits.