Thanks for the question, Rick.
There will be Jenkins level things and CDF level things.
The SIGs that we currently have are Jenkins level entities. In the short term all of them will remain as is. Over time, I think it makes a lot of sense that some SIGs be formed at the CDF level --- for example, advocacy of Continuous Delivery is one project I'd love to see move forward, and it makes a lot more sense to do that at the CDF level than at the Jenkins level. When/if CDF-level SIG happens, it's conceivable that some Jenkins-level SIGs be morphed into CDF-level SIG.
The CDF charter outlines committees that are defined at the CDF level. More/less might get created over time by the decision of the CDF GB.
The same thing with Ambassador. For the short term Jenkins-level ambassador will remain, but I think it also makes sense that the ambassadors be uplifted to the CDF level thing, especially if that makes this program bigger and better resourced. If after a discussion this is determined to be the case, then I think that's what's going to happen.
Ultimately, my understanding is that it's really up to people who are interested in driving things forward to evolve the structure, like how we've been doing it in this project for the past decade. For the most part, it's not like those structures are cast in stone by the current charter. It's a living evolving document that we shape, and what we have right now is "just" a starting point.
Does that help?