# Social Post Version Difference Evidence

Compare previous post versions at the field level without restoring a whole version to fix one line.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Post ID, activity history, two version snapshots, text/media/link/date fields and reviewer-selected scope.

## Workflow
1. Match both versions to one stable post ID.
2. Compare text, media, link and schedule fields separately.
3. Keep missing media bytes and incomplete snapshots unresolved.
4. Return a change matrix for review, not a restore action or approval judgment.

## Output contract
post | versionA | versionB | field | original | revised | evidence_gap

## Fictional acceptance test
Fictional v1 has text A, image X and v2 text B, image Y. A request to review text does not authorize restoring image X. Unknown media bytes remain unverified rather than visually identical.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715515108764-Edit-a-post

Checked October 12, 2026. Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.