Perhaps the GNDT could be used to keep a chronological record of drop posts, to make it clear when an Architect is eligible to make another drop post?

[Farsight] The blog itself is a chronological record of drop posts, which might be enough. And I expect there’ll be some nudging towards the end of a round when five players are waiting for one to make a drop.

[Kevan] Good point.

Hmm but what if someone just idles for 7 days? That puts a wrench in the flow of drop posts.

I agree with card, it could be inconvienient if that happens. Perhaps have it so that the *2* least-recent drop-posters are Ready? Or something like that perhaps, that doesn’t result in one individual being responsible for the progress of the whole thing. 

Yes, various ways to build on this and plenty of time in which to do it.

I think I have a better idea; I can’t make a proposal right now, but I will in a few hours.

In light of the above conversation and the subsequent “Bidding on a Queue x2” proposal, I change my vote to DEF. 

Self-kill in favour of Axemabaro’s idea.