Resolve Shared Details on Read

Context

A shared contact point is a reference, while a copy is a local snapshot. Read-time resolution keeps live references aligned without repeatedly rewriting their contacts.

Decision

Live organization links resolve contact-point values during reads; removing the source converts dependent details into disconnected snapshots with origin, time and reason in the same transaction.

Alternatives Considered

Copy every source edit into all linked contacts. The retired flowdown design repeatedly rewrote contacts and obscured the difference between a deliberate copy and a live link.

Treat source removal as an ordinary copy. Readers would lose the warning that the organization withdrew that contact point.

Consequences

Source removal changes that contract: the database preserves the last value as a disconnected snapshot needing review. Calendar ineligibility instead leaves the reference unresolved. The console’s review choices use general contact patches, with the dedicated API distinction recorded separately.

Source value edits do not rewrite live linked contacts; source removal does disconnect and version them. Region work follows organization address events. Disconnected values require human resolution and have no dedicated reminder.