T-RKG Explorer

An enterprise record collects attributes from many systems. A privacy flag sits in the CRM, the listing status sits in the ERP, the jurisdiction travels with the record. Regulatory conflicts appear only when those attributes are put together. Change a record below and see what T-RKG finds, and what each system sees on its own.

One record, five systems

Teal regulations require the record to be kept. Plum regulations require it to be deleted on request. Lines between regulations are conflicts.

How to reason

The record itself

Always visible to the record's home system.

Customer data system

Owned by Salesforce CRM.

Financial system

Owned by SAP ERP.

Source systems feeding one record, the regulations that apply to it, and conflicts between them

Conflicts

    Why a regulation applies

    A legal hold, followed through relationships

    These 11 records are a real neighbourhood from the synthetic corpus. Place a hold on the email in the middle and watch it spread along typed relationships. Which relationships carry the hold depends on the matter's policy.

    Propagation policy
    Records connected by attachment, thread, derivation and reference relationships