Durable Producer Identity Mapping

Context

External producers identify records with their own keys and may replay deliveries.

Decision and Origin

The record transaction writes a durable producer-key mapping with revision and version metadata plus first and last job identifiers that have no job foreign keys. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Add producer identifiers directly to every domain record: Multiple producers need separate revision and version metadata as well as their keys.

Match imports by natural keys: Mutable or ambiguous natural keys do not supply a reliable producer identity.

Consequences

Existing mappings support revision comparison and replay handling.

Record deletion, merge and workspace reset must reconcile mappings.

An unseen producer key can create another record for an existing person.

Existing rows are locked, but concurrent first deliveries can create separate records and replace the winning mapping destination.