Source Key

What It Models

A source key links an external producer’s record identity to its Rhythm destination. Recurring deliveries use that link to find an existing record, and dependent datasets use it to resolve references. The mapping remains useful after the originating job is retired.

Identity and Attributes

The key combines workspace, producer, record category and external identity. The row keeps the destination, delivery revision, producer-written version and job attribution. Staff do not maintain these links through an editing screen.

Relationships

Keyed jobs consult and update mappings; migration reconciliation reads them through the owning service. Multiple runs can share the same mappings. Job attribution is retained as text without a foreign key, allowing mappings to survive job retention.

Invariants

A successful item commits its destination and mapping together. Existing-key locking and revision comparison protect ordinary repeat deliveries. They leave a first-delivery race: two jobs can create separate destinations and the mapping can end on the last writer.

How It Is Stored and Shared

CRM and Platform each store their mappings under workspace row security. Their application roles may delete mappings, queue entries and submission-ledger rows according to the engine grants. Reconciliation coverage follows the implemented record surfaces; Membership has no mapping store. No custom-field capability is declared for the mapping itself.

Open Design Questions

New-key concurrency needs a protection mechanism. Duplicate detection for imported contacts remains a product choice, and lexical revision ordering requires producer care. Platform custom records and associations still lack producer-key reconciliation endpoints.