Transactional deletion with dependent events

Context

Links can connect native owners to Platform records. Removal policy must remain transactional across that database boundary.

Decision

Endpoint deletion applies link policy in the deleting transaction, bounds custom-record cascades to depth ten and records dependant deletion facts before their originating record.

Alternatives Considered

Removing only permitted members of a cascade: Partial deletion would leave relationships and register content inconsistent with the chosen policy. Cascading into native records: Platform has no authority to delete CRM’s contact or organization aggregates. Removing links after an endpoint commits deletion: A restriction would be discovered too late to prevent the endpoint removal.

Consequences

Endpoint owners call database functions within the removal transaction. A lock or policy refusal in a reached dependant stops every deletion effect. Cross-service cascades do not consult the optional direct-store external deletion check.