The Cable Asks
Before you reach for a patch cable, something has already happened: you've formed an idea about relationship. This oscillator's pitch, shaped by that envelope's contour. That LFO's shape, narrowing the filter's opening on the downbeat. The cable doesn't create the relationship — it tests whether the relationship is real.
This is why experienced patchers work slowly at the start and quickly later. The first few cables are commitments that determine what questions remain askable. Route your one envelope straight to the VCA and you've answered a question before you've asked it: you've decided that envelope controls amplitude, full stop. Leave the envelope unrouted a moment longer and you keep open the possibility that it controls pitch, or filter cutoff, or the rate of something else entirely.
A patch point — any jack, input or output — is not a socket waiting to be filled. It is a position in a signal argument. The output of an oscillator is a statement: here is a periodic voltage. An FM input on a second oscillator is a standing question: what should modulate my frequency? The cable is the answer you're proposing. Like any answer, it can be wrong, or merely uninteresting, or surprisingly right.
Voltage is the language all of this happens in, and that fact matters here: because every signal is just voltage, any output can, in principle, answer any input's question. A gate can go to a CV input. An audio-rate oscillator can modulate rather than sound. The patch bay doesn't enforce grammar — you do, through the questions you choose to ask.
This has a practical consequence. When a patch stops working — when it sounds dead or collapsed or unexpectedly chaotic — the right diagnostic move is to retrace the questions, not hunt for the broken cable. Ask: what was each connection supposed to argue? Where did the logic break? A patch is an essay written in signal flow, and like any essay, it can lose its argument halfway through without a single sentence being grammatically wrong.