I did this a bit differently. Instead of just fixing the gap, I opted to whip up a potential "destination" rig. But since the rack space is really constrained (2 x 88 [not 89!] hp), what I wound up doing is to shrink things down across the board so that you can get a lot closer to a true generative rig.
I tried to keep as much as was possible here, but several devices got chucked out in the process. One of the first to go was the buffered mult; since you'd use the VCOs separately(ish) in generative work, and also because it stole 4 hp, it became unnecessary here...and tbh, in a small build like this, mults in general should be avoided as they rob space from function. Use inlines instead.
Top row: Starts with the P/S, of course...then the Disting, followed by the quantizer (I presume this is for quantizing modulation curves, which is a basic generative technique), then all four sources. After these, one of the Veils (I resized both to the new model) for level control before filtering with the Ripples. Then I placed the Xfader after this, as it offers an interesting opportunity to set up autopanning. The Doepfer mixer is next, then there's all of the effects modules, followed by a Happy Nerding OUT. Now, the reason for that specific output module (aside of the transformer isolation) is that it fixes several problems. For one thing, it gives you a headphone preamp. But much more importantly, it has a second input pair...which then allows you to split the mixer's output between the Verb and the Monsoon, and then you can fly one of those in over the other via the second input. Also, the ganged stereo controls here are definitely easier to balance than the separate controls on the Doepfer passives.
Bottom row: A 2hp Nse first, because there weren't any noise sources for the Marbles to play with. Then the Marbles itself got smushed down to a Pachinko...same module, more or less, minus a few hp that gets used elsewhere. And one of those places is the Quad LFO next to it; to really have a decent generative setup, you NEED extra utility LFOs to provide modulation curves that other modules can reprocess. Maths, Veils, and then a little Frap 321, which allows you to attenuate, INVERT, combine, add offsets, etc. It's pretty much a modulation mangler, allows you to generate more complex modulation results. Then a dual ASDR is after this, giving you a couple of 4-stage envelopes for your audio chain, etc. Then the cryptic-looking thing that's next is a dual window comparator...and THIS is definitely the missing link for generative work. Comparators generate gates under specific voltage input conditions...so, say, an LFO is patched into one and the comparator's threshold is set for 3.5V. The comparator will output a gate each time the LFO's output exceeds this, meaning that you can also use your modulation sources as on/offs for signals that are thruputted through VCAs. But this is no normal comparator, but a WINDOW comparator...meaning that it has TWO thresholds, and you can get gates and triggers when the input is below both, between both (the "window") and above both. This way, you can derive several possible signal states from one single modulation source...and of course, since you have TWO here, well... Anyway, speaking of derivation...the next thing is exactly that, a Derivator. This module also fires off gates...but this time, they're dependent on the direction of the CV that's being inputted. So on this, you have gate-outs for "rising", "falling", any sort of movement at all, or "steady". Now, if you're wondering "why all these effin' GATES?"...the next module answers this. Yep, a Boolean logic module...but this one's a lot more capable than the original Ladik one, as ALL of the gates are usable simultaneously. So, with all of the gate outputs based on CV/mod behavior, you can then take "steady" gates and use the Boolean module and combine everything in those, and get a WILD panoply of possible off/on activity. And to make that even more bonkers, the thing after the Boolean module is a dual probabilistic pulse skipper...so you can actually have random(ish) dropouts in your controlling gate signals. Coupled with logic, like here, that's a potent module. And then the clock divider ends things up.
Now, look closer. You'll notice that, in my build, there are a lot of modules that depend on other modules...and not necessarily the SAME modules each time. For instance, you could use the Skipper for the Minibrute's clock output, keeping things in the modular in pace...except for those odd little "hiccups" that also cause their own strange things to happen, or you could just as easily use one channel of it to randomly "suppress" control gates from the Booleans, and so on. THIS is how you do generative...it's not a matter of "patch A to B and turn knob" at all, but a system that contains LOADS of complex possibilities depending on how it's patched, plus in this case, you have to factor in the Minibrute that's being augmented by the build. IMHO, this does that pretty well. But no, it doesn't use everything you have presently AND it uses some things you don't have on hand. Like I said, it's a "possible end-result" build. Hopefully it's of SOME help.