List Contact References Are Resolved and Reassigned Later

Context

Contact references belong to CRM and can change through merging. The current manual list API accepts references without a contact read.

Decision

Treat memberships as soft links whose readable facts are obtained at evaluation. CRM invokes the participant to move stored links and discard collisions.

Alternatives Considered

Existence checks provide only a momentary answer. A cross-schema key would couple ownership differently from the recorded implementation.

Consequences

Missing facts become a recipient exclusion rather than invalidating the whole list. Merge reassignment supports surviving identities, while concurrent count accuracy remains to be proved.