Tor could use a publish/subscribe abstraction
Many places in our codebase, we have a function "foo_has_occurred()" that is called whenever foo happens, and which dispatches into many other semi-unrelated modules. These functions tend to be fairly huge modularity violations, and create many surprising edges in our module callgraph. Using a publish/subscribe pattern would be the usual way to enforce these divisions.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information