I’d like to know what the planned UI is for the Creditor. One feature that would be useful would be to know how much Cred you would generate from completing certain tasks, so you know if you want to undertake them. This would be a tool that helps with transparency and understanding of how Cred flows. To be clear, this would not allow everyone to add nodes willy nilly, it would be part of the UI available to everyone, that would update with the actual Creditor, but not change the Contribution Graph of the project.
I’d love to hear a more in-depth explanation of your idea of local governance power. I feel like it would involve setting up nodes for all past contributions in order to be accurate in how much weight each contributor’s vote would have in a project. For example, a lot of my top Cred activity comes from props and didathing, on Discord. If the props/didathings were all about things I did for Community Cultivation, they would need to be manually linked, or else I would have little voting power in a trunk where I’ve been quite active.
Whose responsibility would it be to make sure contributions not caught by the plugins are added to the Contribution Graph? This person wouldn’t have to actually add them, but just make sure they are added. This could be the responsibility of the person who feels they “created” that node, such as the person who did a great job presenting a meetup. I personally feel that relying on the person who made the contribution to make sure it is added would create the least extra work for others.
In regards to docs, I would love to make sure that varying levels of contribution could be recognized. For example, there’s authoring, co-authoring, in-depth reviews where you write part of the doc, jams, and basic GitHub reviews. This is one of the holes I see in our current system, and something made rather difficult on GitHub. Definitely a need that could be filled by the Creditor. 
Have you considered using LB’s How to Start a New Project in SourceCred post to tackle some of the more nitty-gritty details, such as governance?
Also, I found this writing accessible, although I definitely skimmed through the software bit. Thanks for asking for feedback and modeling accessible writing on a complex topic 