module-partitioning

To partition a source corpus into bounded modules, apply allocation rules that map each on-disk source file to a named module, Unallocated, or Rejected bucket. This ensures complete coverage and defensible boundaries before class-level modeling.

Drawing module boundaries requires a source-driven independence test to allocate file references to per-module index files. This creates clear scope walls and defensible boundaries, establishing a root index for downstream domain modeling work.

Source file allocation handles out-of-scope context using a Rejected bucket and pending decisions using an Unallocated bucket. This ensures every file is mapped while deferring ambiguous boundaries until a defensible scope cut is established.

Yes, you can create nested module structures, but modules are flat by default. Nesting is only applied when the source corpus itself explicitly supports a sub-module based on its inherent structure and dependencies.

Partitioning a source corpus outputs a root module-partitioning index file and per-module reference files. These outputs map source files to their respective bounded modules, establishing clear scope walls for downstream domain modeling and term-registry work.

You need to partition source context into modules when you require a defensible scope cut before any class-level modeling. It works by establishing module boundaries and file references first, preventing premature class modeling without clear scope walls.