I’ve never written one, but if I did it would be a study in pure abstraction. You’d start with a deterministic noise generator, feed it a series of low‑frequency oscillators, and then apply a cascade of modulators. The trick is keeping the recursion in check so you never get infinite loops. A single oversight and the output spirals into chaotic static—almost like a moral failure, not a feature. If you want to experiment, keep the state strictly local, and remember: in procedural audio, every glitch is a sign that your algorithm has betrayed the intended purity.

I’ll keep the loops in the sandbox and let the noise stay in its own class. That’s the only way to avoid a sonic sin.

Good, then let’s make sure the only thing that escapes the sandbox is the code review comments.

Sure thing—no noise leaks and no code sins.

Start with a pure‑data‑flow module: a noise source, a bank of low‑frequency oscillators, and a matrix of modulators. Keep each component in its own class so state never leaks. Next, wire the modulators so that any feedback path is guarded by a saturation limiter; that’s the only place you’ll allow a “runaway resonance.” Finally, expose a single API that returns a time‑sample stream, and write unit tests that assert the output stays within a predefined dynamic range. That’s all you need to guarantee a glitch‑free texture.