A Visible LinkedIn Repost Lost Its Source-Post Link: Freeze Amplification Claims

A LinkedIn repost can remain visible after the relationship to its source post becomes unavailable in your records. Treat that gap as an evidence failure, not a reason to guess the source from similar wording, an author name, or a screenshot.

Pause downstream claims tied to the missing edge. That includes copied attribution, comment context, performance notes, reporting rows, and outreach decisions that cite the source post. Keep the retained repost and its existing record intact while you investigate.

LinkedIn's Posts API documents a reshare context with a direct `parent` and a derived `root`. Those fields describe the relationship that a recovery needs to establish, but they do not replace your own retained record of what was previously linked. LinkedIn Posts API

Which source post belongs to the visible repost?

Start with the repost record, not a search for a convenient original. Capture its post ID or URN, author, visible text, publication state, retained URL, saved timestamps, and any earlier export that named a parent or root.

Then gather candidate source records from the same approved archive or authorized API access. Compare a candidate only against evidence that existed before the link disappeared: a stored parent ID, a root ID, a permalink, an export row, a content hash, an author hash, or a timestamped review record.

LinkedIn documents post IDs as share or UGC post URNs and describes `reshareContext.parent` as the direct parent of a reshare. If an authorized retrieval returns a parent and root that agree with the retained proof, record the match. If the proof conflicts or is absent, leave the source relationship unresolved. LinkedIn post schema

• Do not use a text match alone as proof of a source relationship.
• Do not replace the visible repost with a newly created repost to make reporting look complete.
• Do not overwrite the original incident record. Add a dated recovery entry instead.

What should the recovery ledger contain?

Use one row per detached repost. The ledger separates what was observed before the incident from what was fetched or verified during recovery. That separation makes an uncertain match visible to the reviewer.

The final release field should remain pending until a reviewer can trace the restored edge from the repost record to the source record and back to every dependent claim.

Which records must be frozen while provenance is missing?

Freeze the claim, not the whole program. A comment may still exist, and a repost may still be visible, but any statement that connects those records to a particular original post needs a verified source edge.

Review author attribution, copied claims, comment extracts, qualifications based on the original context, engagement summaries, and any dashboard row that rolls the repost into source-post reporting. LinkedIn documents separate retrieval surfaces for posts, social actions, social metadata, and organization share statistics. Keep each record on the surface that supports it.

For example, the social actions documentation describes likes and comments attached to a specified share or post. It does not establish that activity on a retained repost belongs to a guessed source post. LinkedIn social actions API

• Author claim: pause copied attribution until the source author is verified.
• Comment claim: pause context or qualification claims until the comment's target record is verified.
• Reporting claim: flag source-level totals as incomplete until the edge and each metric record are retested.

How do you restore the edge without changing the evidence?

Restore the smallest thing that is missing: the relationship between the retained repost and the verified source. Preserve the repost ID, source ID, prior-link proof, retrieval timestamp, reviewer name, and outcome. Do not rewrite historical text to conceal uncertainty.

If the authorized post response contains a matching `reshareContext.parent`, record that direct parent. Record `root` separately when supplied because LinkedIn describes it as the greatest ancestor and a read-only value derived from the parent. A root match can support lineage review, but it does not turn an unresolved direct-parent match into a confirmed one.

Retest after the write or record update. Retrieve the repost again, inspect the restored relationship, reopen each frozen dependent record, and release only the items whose supporting source is now explicit. LinkedIn's social metadata documentation identifies comment-state and comment-summary fields for a specified entity, which can help scope a fresh check of the verified record. LinkedIn social metadata API

Does restored provenance give permission to contact commenters?

No. Provenance answers which source record supports a claim. It does not create consent, a relationship, or a reason to message a person who reacted or commented.

Keep outreach decisions separate from the recovery ledger. LinkedIn's User Agreement says members must have one account in their real name and must not share or transfer an account. It also states that people can share content with different audiences and visibility choices. Follow the relevant permissions, policies, and your own consent-based outreach rules. LinkedIn User Agreement

For Well Met's work, a comment-led outreach sequence starts with real daily comments and a warm connection request. It does not treat a repaired data relationship as contact permission.

When is the recovery ready for release?

Release a row only when the repost and source IDs are recorded, the prior-link proof is preserved, the restored relationship is verified, every dependent claim has been retested, and a reviewer has approved the ledger entry.

Keep metrics narrowly scoped. LinkedIn's organization share statistics documentation describes fields such as clicks, comments, impressions, likes, and shares for organization records. It also distinguishes organization statistics from sponsored activity. Do not copy source-level metrics onto a repost, or combine records, unless the reporting definition and supporting records permit it. LinkedIn organization share statistics