module-boundary-design

To define module boundaries, you must list explicit modules with their names, responsibilities, non-responsibilities, dependencies, dependency directions, and integration seams. This replaces implicit folder layouts with formalized architecture to eliminate ambiguity.

The AC-002 format standardizes architecture planning by documenting explicit module lists, responsibilities, dependencies, dependency directions, and integration seams. This format formalizes inputs, outputs, and integration points across multiple modules.

Identify module responsibilities by listing each module's name, its specific functions, and its non-responsibilities. You then map dependencies and their directions to formalize integration seams for architecture planning and design reviews.

The best way to formalize integration points is applying the AC-002 format during architecture planning. This converts implicit folder layouts into explicit domain-focused module boundaries, documenting dependencies and integration seams.

You need to formalize module boundaries when architectural ambiguity impacts maintainability. Defining explicit dependencies, non-responsibilities, and integration seams replaces confusing folder-driven layouts with cohesive, domain-focused architecture.

Yes, explicit module boundaries support future extension points for evolving architectures. By documenting clear inputs, outputs, and integration seams, you establish a flexible foundation that accommodates architectural growth and dependency changes.