code review planning

[Marvin S. Addison]

> It would also help if you understood the dichotomy between PolicyRules and
> Permit/Deny Rules and also the similar feeling, but completely orthogonal
> dichotomy between context based rules and value based rules.  Nearly all of
> complexity in the filtering implementation springs from the need to flatten
> these two orthogonal dimensions into a single one.

It seems that this paragraph is embodied in the Matcher component; it 
consolidates both concerns in a single component. Could you explain a 
bit further why it's valuable or necessary to consolidate these two 
orthogonal (and admittedly related) concerns?

I believe part of my befuddlement may be due to naming. Matcher seems to 
be a strategy pattern for application of policy, and the mixed language 
"policy" and "rule" is further confusing.

Thanks,
M