[Developer Question] Is it possible to adjust the ‘current_tags’ object usi

I am working for a client that uses a tag for the different manufacturers of their products. Each product will only have one manufacturer tag. On their collections page, they have a sidebar that shows all the Manufacturer names with a {{ tag | link_to_add_tag: tag }} URL. Now the problem is when users are selecting more than one manufacturer tag, it will return no results since its searching for products that have both manufacturer tags.So, what we need is either:

A) A way to filter the products with tags using OR logic rather than AND. So a user can select multiple manufacturer tags and have it still show results of products that have any of the tags passed.

B) I found some documentation on the 'current_tags' object. What I would want to do is:

User clicks a manufacturer tag

Check if any manufacturer tag is in current_tags

If any manufacturer tag is, remove it

Add the manufacturer tag that user clicked in Step 1

This would mean users would have their first manufacturer tag forcibly removed, thus not allowing them to stack the tags.

Does any of this make sense?
Is there an easier way to do this?

Is Robotic Process Automation the Future?

I think RPA is independent as it's about automation. Which is fine if you're a factory drone. But it doesn't work for today's generation of workers, who are used to being treated with a little more respect to feel empowered about doing a job they believe in.
The real future of better process management is making it mainstream i.e.
Easy for anyone to model and run with it, with no consultants/IT/pain involved.

Easy for anyone to track it and do it within either a UI or a tool they already use for hours every day - e.g. chat apps

Easy to get pre-canned process improvement insights through machine learning tech to help show and fix bottlenecks.

Conversational - i.e. it's not robotic but feels like a human conversation - the way people actually work today.

Showing simple, real use cases - and elevated pain to 5 years ago. An example is the gig economy - since a large %ge of people do temp/flexible jobs now and it's increasing, it's even more important now to both define and track work in a simple, agile way.

The above are critical. Without any one of them - we're just back to the tired and dead BPM of today.