module-partitioning

What problem does it solve?

After domain scan, partition the source corpus into modules by allocating source file references to per-module index files. No classes, no anchors — only module boundaries and file references to the source that belongs to each. Supports an Unallocated bucket for pending decisions and a Rejected bucket for out-of-scope context. Modules are flat by default and nested only when the source itself supports a sub-module. Use when the user asks to "partition the source", "allocate context to modules", "draw module boundaries", or needs a defensible scope cut before any class-level modeling.

Core Features & Use Cases

• Flat module structure by default with clear criteria for when to nest.
• Allocation rules that map source files to modules, unallocated, or rejected, using a source-driven independence test.
• Outputs: a root module-partitioning index and per-module references to source files.

Quick Start

Run the module-partitioning workflow on your workspace to generate the root index and per-module references.