Prepare Social Campaign Handoff

Prepare a social campaign handoff

Repository continuity composition

For repository-scoped work, compose maintain-repository-continuity in Resume mode before selecting work. After an authorized repository change passes domain validation, compose Refresh and Verify immediately before presenting the pull request, and include the reconciled root CONTINUITY.md in the same change. A policy-permitted no-change or exemption result must be documented instead of fabricating an edit.

• Contribute: Input locks, packet digest, review state, exact validation, freshness limitations, and export boundary
• Never claim: That candidate content is approved, exported, posted, scheduled, or published without evidence

Build a reviewable packet without becoming a publisher or a second source of brand/platform truth.

Inputs

Require all three local inputs:

• an approved identity.social-surface-package/v1;
• the exact aether.social-surface-catalog/v1 locked by that package; and
• a user-supplied campaign brief based on campaign-brief.template.json.

Do not request or accept platform credentials, tokens, cookies, scheduler secrets, direct-post instructions, or ad-spend authority. Do not fetch current platform requirements while compiling.

Prepare

python3 scripts/campaign-handoff.py prepare \
  --identity-package "path/to/social-surfaces.json" \
  --catalog "path/to/catalog.v1.json" \
  --brief "path/to/campaign-brief.json" \
  --output "path/to/campaign-handoff.json"

Preparation verifies the Identity and catalog locks, exact selected surfaces, rights/release state, provenance, and closed brief. It emits only draft copy/claims and preserves unknown constraints and freshness requirements.

Review lifecycle

Use the deterministic commands in review-and-export-safety.md. The allowed skill-owned progression is:

draft -> reviewed -> approved-for-export

Approval requires every required checklist item plus a human approval record whose digest matches the exact reviewed packet. The tool may also supersede a packet. It shall refuse a transition to published.

A platform or scheduler adapter may later append a published receipt under its own explicit authorization. That adapter is outside this skill.

Interpret and hand off

• Preserve dimensions, media limits, safe-zone state, source evidence, and null/unknown values exactly.
• Keep user objective, audience, context, candidate copy, and claims labeled by source and review status.
• Do not call a draft or reviewed packet approved.
• Treat approved-for-export as authorization to hand off an immutable file, not authorization to publish it.
• Re-run validation immediately before handoff.

Read campaign-handoff-contract.md when authoring a brief, integrating a consumer, or investigating validation.