>Its very flexible and a good example of the care that Kevin has taken to architect his framework with solid OOP principles.

I'm sure it is. But either I'm not making the connection or you didn't address the concern, but what benefits are there to the developer? For example, if I have the following method:

public bool IsRecordValid()
{
   return name != "";
}

Thats my business rule, now, when I introduce the framework:

1. What will this code look like?
2. Will it be as easy to modify as the existing code?
(Lets say we change the business rule to return name + firstName != "", does the business rule implemented as an object adapt as easily?)
3. What do I gain using the new way and not simply coding the rule in a straightforward manner that all C# developers will understand?

I do see why one would want to implement an interface to make business objects more accessible, but still, thats fairly trivial and doesn't require a framework.