Reconcile a creator’s published content with a local archive

Why use this

1. A creator’s local idea notes rarely match the titles eventually used in published newsletters or social posts. Marking ideas as used based on title similarity alone can hide unfinished work, while failing to recognize a renamed piece encourages accidental repetition.

2. This job could map published pieces to their local sources before changing the archive. The creator can then distinguish finished ideas, partial reuse and unrelated pieces with similar wording.

Why an agent / simpler alternative

Useful judgment

Recognize substantive overlap across renamed drafts and published material while explaining uncertain matches.

Simpler alternative

Use stable content IDs or a publication spreadsheet when the archive already has consistent metadata.

Unsuitable when

The creator needs deletion or irreversible cleanup before uncertain matches can be reviewed.

Proposed inputs

1. Name

   Published-content export

   Owner

   Creator

   Minimum scope

   Authorized posts, newsletter text, publication dates and canonical links

   Quality check

   Distinguish original posts from reposts and later corrections.

2. Name

   Local archive snapshot

   Owner

   Archive owner

   Minimum scope

   Scoped drafts, idea notes and existing publication metadata

   Quality check

   Preserve note IDs, backlinks and current archive status.

Access and setup — proposed or unknown

Proposed minimum

1. Read selected published records and a local archive copy; preview state changes before moving notes.

Compatibility unknowns

1. Unknown: Threads access, newsletter export quality and Obsidian file conventions.

External actions requiring approval

1. Moving or rewriting notes, changing publication metadata or sharing private drafts.

Expected deliverable and review checks

Proposed artifact

Reconciliation manifest with published link, local candidate, match rationale and proposed archive action.

Critical checks

1. Partial reuse does not automatically mark the whole idea exhausted.

2. Every proposed move preserves recoverable paths and existing backlinks.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   Two drafts share an opening but develop different arguments.

   Why it matters

   A loose match could archive an unpublished idea.

   Proposed response

   Compare the full substance and leave ambiguous candidates active for creator review.

2. Signal

   A renamed note is moved without updating its references.

   Why it matters

   The archive becomes harder to navigate despite appearing tidier.

   Proposed response

   Preview affected backlinks and retain a reversible mapping before any move.

Effort and cost — unknown

Setup work

1. Define publication states and matching criteria for complete versus partial reuse.

Ongoing review

1. Review ambiguous matches and reconcile later edits to published pieces.

Unknowns

1. Unknown: export access, matching effort and archive-maintenance cost.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A synthetic archive contains a renamed published draft, a partially reused idea and an unrelated draft with the same opening.

Acceptance checks

1. Only the complete match is proposed for archival.

2. The partial reuse remains actionable and all candidates retain source links.

Stop conditions

1. Unreviewed deletion or modification of the only archive copy would be needed.

Limits

1. Editorial matching can support organization; it does not establish publication rights or originality beyond the scoped materials.