Domain-based Refactor

#5: Finally, an easy task.

Sometimes, short entries make me happy. After a few long slogs, I finally asked my agent (Claude Sonnet 4.5 in Opencode) to complete a task, and it just… did as requested.

I'd would like to refactor this codebase so it is more organized by domain. A few notes:

- Core shared code can either be in the top-level `src` directory or nested in one named something like `core`.
- Files should be small and focused.
- There should be a `modules` directory for modular components.
- Within the `modules` directory, individual modules can either be simply a file named after the module (`osc.rs`) or in a direct named for it (`osc`). I would generally prefer all modules to follow the same pattern. So, if it seems like modules will generally need to be defined in more than one file, use the directory approach
- Names should be simplified. Most things no longer need a `Modular` prefix.

Please come up with a plan for cleaning up the code with the above points in mind.

It is the sort of thing I imagine is relaxing for a generative AI model — just moving stuff around in a logical manner. Kind of like an experienced musician practicing scales. It becomes a sort of meditation.

#5: Domain-based Refactor

2026.1.29