I’m specifically wondering how well this plays with OSRM - if there’s any pattern to the held-back edits that might result in discontinuities or network disruption.

sigh. “. . . AT all processed . . .”

Is this distro say all processed with an eye toward routing?

You might address this elsewhere, but your participant count for Haiyan is far too low. Is it possible that 60% of the changeset-flagging participants didn’t use the task manager for that activation?

Obviously geographic data is ephemeral; especially roads, with their constant condition changes and expanding networks. I don’t think the minutia of “appropriate time scale” is really the point, and I love the point:

This is a proof of concept for contributing value-add information to OSM; it perfectly compliments the data model and expands the project’s capabilities.