Content Repurposing Automation: Preserve the Source Before Changing the Format

# Content repurposing SOP

Version: 1.0

Owner: Content or marketing operations

Effective date: [YYYY-MM-DD]

Review cadence: [cadence and owner]

## Purpose and scope

Create channel-specific derivative drafts from one approved source while preserving factual meaning, claim provenance, rights, editorial approval and correction control. This procedure does not establish copyright, endorsement or licensing rights and does not permit autonomous publishing.

## Trigger, inputs and prerequisites

- Trigger: source version receives editorial approval for repurposing.
- Inputs: source file/version/hash, claim ledger, citations, quote/rights record, prohibited moves, channel brief, editor and publication destinations.
- Prerequisites: approved voice/claims policy, rights policy, channel requirements, correction/withdrawal route, test cases and publishing permissions.

## Roles

- Source owner: approves the canonical source and supported claims.
- Rights owner: confirms permitted text, image, audio, video and quote reuse.
- Channel editor: approves the actual derivative and publication.
- Operations owner: owns versions, workflow failures and correction propagation.

## Procedure

1. Freeze the approved source version and create a project ID.
2. Extract candidate claims with exact source spans, citations and qualifications.
3. Have the source/rights owners approve reusable claims and media.
4. Create one asset ID from project, source version, channel and brief version.
5. Select only approved claims relevant to that brief.
6. Generate a draft that may compress, reorder or reframe but may not add facts, outcomes or quotations.
7. Validate source references, required labels, prohibited terms, length and duplicate asset keys.
8. Route unsupported sentences, rights gaps and ambiguous qualifications to review.
9. Have the named editor approve the exact copy/media and then approve publication.
10. Store publication ID, URL, source/claim links, reviewer edits and withdrawal path.

## Decisions, exceptions and approvals

- New fact, statistic, product claim or customer result: return to source research and approval.
- Quote: require exact words, attribution and permitted use.
- Source superseded: block new assets and review affected scheduled/published derivatives.
- Rights expired: pause or withdraw every asset using the affected material.
- Partial publication: retry only missing destinations after reconciling existing IDs.
- Publication, correction and withdrawal: named human approval.

## Output and completion

Output one approved channel asset with asset/source/brief versions, claim IDs, citations, rights state, reviewer, publication ID and correction link. A generated draft is not a completed output.

## Measures

Track unsupported-claim rejection rate, editor correction themes, duplicate prevention, publication failures, time in review, claim-withdrawal propagation and assets lacking a source span. Do not use raw asset count as a quality measure.

## Worked example (simulated)

An approved webinar includes an unsourced statistic. The claim ledger marks it unavailable for reuse. A draft introduces the number from model memory, so validation rejects the asset. The corrected draft uses only the supported operating example, and the failure becomes a regression case.

## Revision log

| Version | Date | Change | Approver |
| --- | --- | --- | --- |
| 1.0 | [YYYY-MM-DD] | Adapted from public template | [name/role] |

# Content repurposing workflow blueprint

## Trigger and termination

- Trigger: `{source_id, source_version, approval_id, rights_version}` becomes approved for repurposing.
- Success: approved derivative has a reconciled publication record or an explicitly approved draft-only terminal state.
- Stop: revoked source/rights approval, unsupported claim, invalid channel brief, expired editor authority or owner-issued stop.

## State model

`received -> claim_extraction -> claim_review -> ready -> drafting -> validating -> editorial_review -> publication_approval -> publishing -> published`

Alternatives: `returned`, `rejected`, `withdrawn`, `stopped`, `superseded`. Approval never occurs in the drafting step.

## Data contract

- Source: ID, version, hash, approval and canonical location.
- Claim: ID, text, exact source span, citation, qualification, allowed transformations and approval.
- Rights: material ID, owner/consent, allowed channels, expiry and restrictions.
- Brief: version, channel, audience, format, length, voice, desired action and prohibited moves.
- Asset: ID, source/claim/brief versions, draft, validation results, reviewer, publication IDs and correction state.

## Ordered steps and actors

1. **Trigger:** receive approved source version.
2. **AI (bounded):** extract claims/spans or mark ambiguous.
3. **Human:** approve reusable claims and rights.
4. **Code:** select approved claims for one brief and compute asset key.
5. **AI (bounded):** draft without new facts, quotes or outcomes.
6. **Code:** validate lineage, labels, prohibited terms and duplicate keys.
7. **Human:** edit/approve exact asset and publication.
8. **Code:** publish idempotently and retain effect IDs.
9. **Human + code:** correct or withdraw through linked assets when needed.

## Idempotency, retry and rollback

- Key: `asset:{source_id}:{source_version}:{channel}:{brief_version}:{variant_key}`.
- Key each publish effect by asset/version/destination. Reconcile returned IDs before retry.
- A changed draft creates a new version, not an overwritten approved artifact.
- Rollback pauses scheduled effects and withdraws/replaces published assets through recorded destination IDs.

## Permissions and sensitive data

Drafting reads approved source/claim fields only. Publishing credentials are unavailable to the drafting step. Exclude private customer/personal data from prompts and test with fictitious fixtures. Restrict withdrawal to named editors/owners.

## Exception routes

- Unsupported/ambiguous claim -> source editor.
- Quote or media rights gap -> rights owner.
- Channel-policy failure -> channel editor.
- Partial publish -> operations owner.
- Source correction/withdrawal -> all linked asset owners.
- No owner -> safe stop.

## Acceptance tests

1. Unapproved source cannot trigger drafting.
2. Claim without source span cannot enter a draft.
3. Qualification such as “may” cannot become “will.”
4. Quote without exact text/rights is rejected.
5. Drafting step cannot publish or self-approve.
6. Duplicate event creates no duplicate asset/publication.
7. Partial publish retries only missing destinations.
8. Source withdrawal finds and pauses every linked scheduled asset.

## Audit record

Retain source/claim/rights/brief versions, prompts or generation configuration where appropriate, validations, drafts, edits, approvals, publication IDs, retries, corrections and withdrawal events.