Is this particular implementation working for you, or if you haven’t implemented it yet, could you let us know if it does/doesn’t?
I went with the dead simple timeout mentioned in the other thread as a temporary kluge as I was busy working on other aspects. I can do this because I do not have aggregates proper, as each ibGib process is much like an immutable snapshot of an aggregate’s state. So they are extremely cheap, as any work done that would normally be done in the aggregate process’ command handler is actually done in the “next state” process’ init (or just after). This allows for “branching aggregates” so to speak, but I digress…
But it would be awesome to have the dynamic timeout and your feedback may spur me to go ahead and implement it. 
