The rulebase level stuff is essentually what you get when you use a
cache/map - no issues or questions there, and you are probably right. It
should be possibly by just loading different versions of the rulebase into a
named cache. The question is what do we need to add to the tool to support
For our purposes, we'd likely want to version an entire 'set' of rules
(ruleset or more likely: rulebase), so that each set could be tested before
deployment as a unit, for the simplicity therein - if there were a
significant performance/load/memory difference in applying versions at the
rule
