# Source-post verification checklist

Use this checklist with a completed source-post record. A local pass is a planning artifact; it does not prove a live Meta change or authorize launch.

## 1. Local record

- [ ] Page ID, ad-account ID and intended ad context are recorded as strings.
- [ ] Existing-post handoffs include the exact Page post ID. For a composite ID, its Page prefix matches page.id. Planned new-post handoffs keep it blank until creation.
- [ ] The seven canonical creative fields are complete; Build creative fingerprint reproduces creative.fingerprint.
- [ ] Creative fingerprint matches the approved fingerprint and approval evidence names the exact payload.
- [ ] Permission evidence identifies the operator and intended Page/ad account.
- [ ] Duplicate source records and conflicting post IDs are reconciled.
- [ ] Every evidence request keeps its exact supplied wording.

## 2. Post creation

- [ ] If a new unpublished Page post was created, record its exact ID and dated creation receipt. A created/existing status without that receipt Holds.
- [ ] Keep post_created false when creation is only planned.

## 3. Native identity

- [ ] Open a current Ads Manager preview for the intended ad context.
- [ ] Read back the Page ID, post ID and creative fingerprint.
- [ ] Record checked_at and expires_at; refresh an expired preview.
- [ ] Attach the dated native receipt.
- [ ] Keep continuity at intent_only unless continuity.native_evidence exactly links to that current native receipt.

## 4. Separate launch review

- [ ] A separate reviewer checks permission, creative, Page/post identity, destination and current preview.
- [ ] The review occurs after native verification and has a dated receipt.
- [ ] No duplicate source, launch_reviewed blocker or handoff-blocking request remains.

Planning only. No spend, launch or live-account edit is authorized.