Attribute link creation from source and outbound evidence, not a blank audit view

A blank customer-visible audit view does not prove that an initial link-creation event is unattributable; the view may intentionally project only a subset of privileged actions. For sender and source attribution, correlate the parent record's creator and external-source fields, resolve the creator through the authoritative identity mapping, and then verify the outbound action in durable message records and correlated creation events. Automated or API paths should carry their own provider or source evidence.

Keep creation, provider acceptance, and handset delivery as separate states. A populated creator and matching source can support who initiated the action, while provider acceptance still does not prove delivery to the recipient device.