Solution/behaviour patterns as a discipline

There are design patters that describes common approaches for code organization, so when we see a factory we know it is a factory. In UX (user experience) they have patterns too, and that why when we see checkbox or radio buttons we know what is the difference between them. Architectural patterns have a wider scope then just design patterns and are more concentrated around high level components relations, at least as I can see it. But when client comes to you and starts describing his problem you are proposing some possible solutions of it, and it goes before any architecture. And that what causes an interest for me - catalogue of solutions for different problems. Is there any movement in the world that tries to consolidate such things under one roof like architects do with design patterns?

I'll give an example of "staging" as I know it:

Lets say from client initial description you see that they need to version their data one way or another and allow precise control of what will is/will be used in production system. E-Commerce system can allow to edit products, prices, discounts, etc. and in the end, ensuring that everything is ready, switch data that WAS in production with new version. Many people know it as "staging".

So, we have a name of solution with is known to at least some people, and it is not a design pattern or architectural pattern. It what you propose to your client as possible solution of their problem when it fits. And I would lie to see more of them with names and descriptions.