Happy to work on B(and A?) as it’s already in our roadmap 
For context I’m working on a runtime that runs ink-like programs(VOS) in a server environment(and the browser, embedded hardware and maybe JAM?), the runtime exposes a simple HTTP/WS RPC API used to call functions of any of the installed WASI(wink) programs.
The reason A and B could tackled simultaneously is that our governance API will be another wink program that simply interacts with a virtual filesystem(hidden away by the wink macro), I plan to use matrix as a decentralized eventually-consistent encrypted storage exposed to wink programs as a filesystem(allows DAOs and their members to share private “files”/state), git can be another(even easier to implement) virtual filesystem.