>>>Reasons for it being in the biz tier:
>>
>>>- domain expert may make relational integrity statements like "if a sales person is fired, move all of their customers to his boss". Clearly this is a business rule.
>
>>This is not referential integrity.
>>This is the contained level ( The level of the information in the data container ) this relation is not a data referentiel relation but a contained information relation the relation is done with any key. Nothing to do with referential integrity
>
>Not sure if I completely follow, could you elobrate?
>

I am not a writer ( even in french ) but I try.

>The definition of referential intergrity is "The rules governing data consistency, specifically the relationships between the primary keys and foreign keys of different tables."
>
>Is this exactly what the customer has expressed, but at a more abstract level?

Not exactly, but thinking about referential intergrity as a more abstract level is the good way.

The rules governing data consistency are on the template level, no live data to make the rules on it, only fields and tags

To preserve consistency you need only to know the name the fields, tags not the data on it. ( ... the relationships between the primary keys and foreign keys of different tables. )

In your example when a person Is fired

Delete all child's that's what me must do to preserve data consistency.

Moving all child's to the Boss must be done of course on the data level but the data can't do it alone the biz layer must order this . ( At the data level we can't move records to another person wich data rule can we apply ? )

Good luck for your certification.