How to deal with dynamic rules in a stream

I am using the nools rule engine and have a need to modify rules on the fly without affecting the integrity of the rule engine.

So far, I've used a standard "master" action group to store my default rules and use a specific action group to store company-owned rules. But if the company wants to change / add / remove rules, I will need to re-create the whole stream. I couldn't find something about this in the documentation. For me, deleting the stream (which will contain the rules for all my companies) and re-creating it seems to work a lot for crud rules. Because of this, I began to think that perhaps the flow would be a better strategy for the company, but still, if they want to change the rules, the flow itself must be removed and added again, but with new rules, changed rules and without deleted rules. The problem is that rules can be changed / removed / added on the fly.

My questions:

• How do other rule engines deal with crud dynamic operations on rules?
• Should I use a stream for each company?
• Is there a way to add / remove / change flow rules dynamically in nools?
• Is there a better machine-style solution for this?

Any help would be appreciated.

thank