pmos-architecture-designer

Defining system boundaries and integration seams requires explicit architecture decisions scoping costly-to-change choices, responsibility ownership, and API/event contracts before builder execution. This ensures implementation handoffs proceed with clear technical prerequisites.

Architecture decision scoping clarifies what is being decided, identifies costly-to-change dependencies, and makes data ownership and platform versus subproject placement explicit. It translates undefined tradeoffs into architecture-ready designs before coding begins.

ADR-ready tradeoff analysis compares alternatives by recording complexity, operational cost, migration cost, testability, and rollback difficulty. It produces explicit decision statements with chosen and rejected options plus known risks for review points.

You need architecture boundary design before coding when facing undefined boundary and integration tradeoffs that are expensive to change later. It forces explicit decisions on platform versus subproject placement, responsibility ownership, and contract seams.

Governing pre-implementation architecture decisions requires satisfying prerequisites for explicit decision statements, context constraints, integration contracts, and follow-up review points. This prevents expensive implicit choices by forcing boundary decisions before implementation begins.

Yes, architecture decision scoping applies to module and service splitting by clarifying which dependencies are external or cross-module. It makes responsibility ownership and data ownership explicit regardless of external dependency presence.