Obligations travel with the record
A client record carries consent, retention and jurisdiction constraints. When it is copied into a workflow store or an index, those constraints apply there too. Naming them in the integration specification prevents a quiet expansion of exposure.
Make inheritance visible in the contract
Each integration specification should state what the source permits, how long the receiving system may hold the data and who may see it. Written down, these become testable conditions rather than assumptions held by one person.
Re-test after every change
Permissions drift as roles change and sources are re-scoped. Periodic access review, run against the same criteria each time, is what keeps inherited governance true rather than historical.