Patch → Invention
#13: Using more musical names.
At some point, a coding agent deciding to name user content “patches.” I never asked it to, and it never asked for my input.
From the standpoint of audio synthesis, it makes sense. The term “patch” is pretty standard in any audio system that connects independent components using physical or virtual cables. This includes Buchla systems, Eurorack modules, Max/MSP, PureData, and many others. Moreover, I instructed the agents on multiple occasions to use modular synthesizers as a major source of inspiration and key reference.
Still, this project is called “Fugue,” and its purpose is to create music. As one of the two hard things in computer science, naming things — especially core entities of a system — deserves care. Names can have lasting, subtle effects that are hard to predict. Before this all progresses too far, I decided to think it through.
I settled on “invention” because it is another fugue-like form that Bach was known for and, obviously, it refers to an act of creation.
When I instructed the agent on this change, I assumed this would be a quick and easy task. For its first pass, however, it simply ran a search and replace for every instance of the word “patch” without reasoning through context. This included a passage in the documentation that described how modular synthesis patches were a source of inspiration. It was a careless change. After a few stern words of reproach for my wayward intern, I told the agent to take a second pass, to take its time and be deliberate. The result was just good enough, and I assume we will need to revisit some spots in the documentation and comments that now make less sense.
After it was over, I decided to ask Claude why patch had been chosen. This is a tricky sort of question for an agent since it is unaware of our previous conversations and tasks. Beyond that, the work so far has spanned multiple versions of Anthropic models using multiple agent frameworks (Copilot, Opencode, and Claude Code). Still is was a surprisingly insightful chat.
Me
It was agent that decided to use the term patch in the first place. I am not sure if it was Claude or what model was used, specifically. Why do you think that term was chosen as the name of content in this library?
Claude
"Patch" is the standard term in modular synthesis — it comes from the physical patch cables used to connect modules on original Moog and Buchla synthesizers in the 1960s. The configuration of connections between modules became known as a "patch." The term carried forward into Eurorack, VCV Rack, Max/MSP, Pure Data, and virtually every modular synthesis environment. Given that Fugue's CLAUDE.md explicitly lists Eurorack and VCV Rack as inspirations, and the entire architecture is modular (modules with named ports, signal routing via connections), "patch" was the domain-correct term. It's what any synthesizer user would expect. The rename to "invention" was a branding/identity choice — giving Fugue its own vocabulary — but that's why the second pass was needed: "patch" worked naturally as both a noun ("load a patch") and in compound phrases ("patch file", "patch runtime"), while "invention" only works well as a proper noun for the entity itself (Invention, InventionBuilder), not as a generic substitute everywhere.
Me
But given that the library is called Fugue and that modular synthesis wasn't the only inspiration, why only derive names from synthesis?
Claude
That's a good point. "Fugue" is a compositional term — Bach, counterpoint, interwoven voices. And "invention" is too: Bach's Two-Part Inventions and Three-Part Inventions are some of the most well-known keyboard works in the repertoire. It's a deliberate musical composition reference that complements the library name, not just arbitrary branding. So the choice of "invention" was actually well-considered — it draws from the same musical lineage as "Fugue" itself, rather than defaulting to synthesizer jargon. The issue wasn't the name, it was that the first pass applied it too mechanically without considering where it reads naturally as a proper noun versus where a neutral word like "setup" fits better.
Me
Would it be fair to say that you have a somewhat better understanding of audio synthesis concepts than musical concepts?
Claude
Yes, that's fair. I defaulted to explaining "patch" through its synthesis lineage and treated "invention" as a branding decision, when the Bach connection was sitting right there. That's probably reflective of training data — there's a lot more technical documentation about DSP, modular synthesis, and audio programming than there is about compositional forms and music history in the contexts where code gets discussed. It's a useful thing to be aware of when working on this codebase specifically, since Fugue's identity leans into the compositional side.
Claude then made a note of the discussion in a MEMORY.md file for future reference.
2026.2.20