Gateseq pattern I indeterminate behavior with no clock

Currently the module sends out a spazzoid burst of triggers when no clock is present instead of having some kind of well defined behavior.

I think it should have an "off state" until the module gets a handful of gates (lets say 4), enough to allow the user to impart some kind of meaningful timing.