The problem is that it’s a little hard to act upon advice like “use appropriate tools in a pragmatic and reasonable way”, however true that is

It's even harder to act on terms without a simple pattern language, if only with high-level descriptions for each, maybe more like a glossary. Component: Service: Deployment: ... From that we could merge, coalesce, and diff, with diff being a productive experience :)

Maybe we could do a quick online workshop to come up with some rough consensus (or meaningful disagreement)?

I would do that.

Deal! I’ll follow up via email.

If you don't mind, I recommend that those involved submit their pattern language or glossary for this context beforehand so we don't spend all our time disagreeing about priorities of opinion. We need at least a list of nouns that are in play and in question.

Apologies, I just wanted to start with a small round of people and ask them who they want to include so we don’t end up with an unmanageable size. You’re welcome to join.