Document Type: Specification
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Content repurposing tracking, multi-format content expansion, article-to-social workflows, video-to-content workflows, email adaptation, YouTube description support, affiliate support content adaptation, future mwmscontentbrain.site operational use, and future Content Brain plugin or UI planning
Parent: Content Brain
Last Reviewed: 2026-05-06
Purpose
The Content Brain Repurposing Queue Specification defines the future queue structure used to track approved content assets that should be adapted into additional formats.
This specification exists to prevent good content from being used only once.
The Repurposing Queue will eventually provide a structured view of:
approved source assets
repurposing opportunities
target formats
channel-specific adaptations
content ownership
repurposing priority
claim safety
meaning preservation
review requirements
handoff status
publishing readiness
performance feedback
The goal is to help Content Brain turn one strong asset into multiple useful outputs without creating unsupported claims, duplicate clutter, or disconnected content.
This page is a planning specification only.
It does not activate a plugin, create a database table, build a screen, or interfere with M’s current build work.
Scope
This specification applies to:
future Content Brain repurposing queue design
future mwmscontentbrain.site operational planning
article-to-email adaptation
article-to-social adaptation
article-to-YouTube-description adaptation
article-to-short-form-script adaptation
video-to-article adaptation
video-to-email adaptation
newsletter-to-content adaptation
research-signal-to-content adaptation
affiliate-support-content adaptation
FAQ extraction
trust-section extraction
comparison-snippet extraction
content asset reuse planning
future plugin or UI planning
This specification does not govern:
live plugin development
Supabase implementation
Brain-to-Brain request automation
HeadOffice reporting implementation
Affiliate Brain wiring
Research Brain wiring
Finance Brain wiring
Ads Brain campaign execution
final compliance approval
live publishing authority
M’s current build work
Those remain governed by the relevant Brain, Canon, protocol, standard, or implementation layer.
Core Principle
Strong content should be reused carefully.
Repurposing is not copying and pasting.
Repurposing means adapting an approved source asset into a new format while preserving:
meaning
accuracy
audience fit
intent
claim safety
tone discipline
system purpose
review traceability
The Content Brain Repurposing Queue should answer:
what source asset is being reused
why it is worth repurposing
which format it is becoming
which channel it supports
who owns the adaptation
what risk exists
what approval is required
where the final asset will go
what signal should be watched after use
If the queue cannot answer these questions, the repurposing system is not mature enough.
Governance Role
The Content Brain Repurposing Queue is an operational visibility system.
It does not create authority.
It does not approve offers.
It does not approve campaign changes.
It does not approve compliance-sensitive claims.
It does not authorise publishing by itself.
It only tracks repurposing needs and makes status visible.
Content Brain may use the queue to manage repurposing work, but authority remains with the relevant owner, Brain, or human approval path.
Relationship To MCR
MCR remains the source of truth.
This specification belongs in MCR because it defines the structure and future implementation logic of the repurposing queue.
The MCR version defines:
queue purpose
queue scope
field requirements
status model
repurposing types
risk model
ownership model
review rules
future UI candidate logic
drift protection
mwmscontentbrain.site may later operationalise this queue as a working screen or plugin feature.
Relationship To mwmscontentbrain.site
mwmscontentbrain.site is the likely future home of the operational Content Brain Repurposing Queue.
The future queue may appear as:
a WordPress admin table
a custom Content Brain page
a dashboard panel
a content repurposing task board
a status-based repurposing queue
a Supabase-backed workflow surface
a manual content tracker first
A simple manual version should be used before any plugin or UI build.
MCR To Brain Classification
Destination: Later Plugin Or UI
Reason: Repeated structured interaction, asset reuse tracking, multi-format adaptation planning, status tracking, channel-specific production visibility, and repurposing workflow management
Source Of Truth: MCR
Future Use: Content repurposing tracking screen or queue inside mwmscontentbrain.site
Future Plugin Or UI: Yes
This page should be listed in the Content Brain Copy Map as a future plugin or UI candidate.
Repurposing Queue Function
The Content Brain Repurposing Queue should track the movement of approved content assets into new formats.
The queue should support:
source asset visibility
repurposing opportunity visibility
channel target visibility
format target visibility
priority visibility
owner visibility
risk visibility
review requirement visibility
approval visibility
handoff visibility
blocked work visibility
performance feedback visibility
The queue should not become a dumping ground for random content ideas.
Every repurposing queue item must have a clear source asset, target format, owner, and next action.
Repurposing Queue Item Definition
A repurposing queue item is a single content adaptation task.
A repurposing queue item may represent:
article to email
article to social post set
article to YouTube description
article to short-form script seed
article to FAQ block
article to trust section
article to comparison snippet
article to sales support note
article to affiliate support asset
video transcript to article
video transcript to email
video transcript to social content
newsletter insight to article outline
research insight to content brief
offer brief to FAQ content
webinar or training transcript to content asset
content refresh to new derivative asset
Each queue item should move through a clear status model.
Required Queue Fields
Each Content Brain Repurposing Queue item should include the following fields.
Core Fields
Repurposing Item ID
Source Asset Title
Source Asset URL Or Location
Source Asset Type
Target Asset Title
Target Asset Type
Target Channel
Request Source
Requesting Brain
Supporting Brain
Repurposing Owner
Review Owner
Approval Owner
Priority
Status
Created Date
Updated Date
Target Completion Date
Notes
Source Asset Fields
Source Asset Status
Source Asset Approval Status
Source Asset Owner
Source Asset Date
Source Asset Topic
Source Asset Purpose
Source Asset Audience
Source Asset Intent
Source Asset Funnel Role
Source Asset Risk Level
Source Asset Source Of Truth
Repurposing Purpose Fields
Repurposing Purpose
Business Reason
Audience Reason
Channel Reason
SEO Reason
Affiliate Support Reason
Authority Reason
Trust Reason
Conversion Support Reason
Sales Support Reason
Engagement Reason
Content Efficiency Reason
Target Format Fields
Target Format
Target Platform
Target Destination
Target Audience
Target Awareness Stage
Target Intent
Target CTA Type
Target Tone
Target Length
Target Structure
Target Publishing Owner
Target Handoff Owner
Adaptation Fields
Adaptation Instructions
Sections To Reuse
Sections To Rewrite
Sections To Remove
Sections To Shorten
Sections To Expand
Claims To Preserve
Claims To Avoid
Proof To Preserve
CTA To Adapt
Internal Links To Include
External Sources To Preserve
Format-Specific Notes
Risk Fields
Risk Level
Compliance Sensitivity
Claims Risk
Affiliate Status
Offer Status
Needs Compliance Review
Needs Human Review
Needs Research Verification
Needs Affiliate Brain Review
Needs Conversion Brain Review
Needs Ads Brain Review
Needs Data Brain Review
Needs HeadOffice Review
Output Fields
Draft Location
Final Asset Location
Target Destination
Published URL Where Relevant
Handoff Destination
Approval Notes
Review Notes
Publishing Readiness Status
Repurposing Completion Date
Feedback Fields
Performance Signal To Watch
Review Date After Use
Feedback Destination Brain
Expected Outcome
Observed Outcome
Repurposing Result
Follow-Up Repurposing Opportunity
Lessons Learned
Signal Feedback Notes
Repurposing Source Types
The queue should classify the type of source asset.
Recommended source types:
SEO Article
Authority Article
Pillar Page
Topic Cluster Article
Affiliate Support Article
Pre Sell Article
Comparison Article
Review Support Content
FAQ Content
Trust Support Content
YouTube Video
YouTube Description
Video Transcript
Podcast Transcript
Newsletter Insight
Research Note
Offer Brief
Content Brief
Email Sequence
Social Post Set
Training Transcript
Course Notes
Refresh Task
Repurposing Target Types
The queue should classify the target asset.
Recommended target types:
Email Draft
Newsletter Section
Social Post Set
YouTube Description
Short Form Script Seed
Article Outline
Full Article Draft
FAQ Block
Trust Section
Comparison Snippet
Sales Support Note
Affiliate Support Asset
Internal Knowledge Note
Retargeting Content Idea
Landing Support Section
Content Brief
Topic Cluster Addition
Repurposing Type Model
The queue should support the following repurposing types.
Article To Email
Turns an article, guide, or support page into email content.
Used when:
the article has strong educational value
the audience needs nurturing
the message supports sales or affiliate follow-up
Article To Social
Turns an article into multiple short social posts.
Used when:
the article has strong points, tips, objections, or educational sections
the topic is suitable for awareness or engagement
Article To YouTube Description
Turns a written content asset into a supporting YouTube description.
Used when:
video content needs a clear description
an existing article matches the video topic
the description should support clicks or context
Article To Short Form Script Seed
Turns an article into short-form video script ideas.
Used when:
the article contains sharp hooks, myths, problems, or useful tips
short-form testing may be useful later
Video To Article
Turns a transcript or video idea into a structured article.
Used when:
video content contains useful teaching
the topic deserves searchable written content
the transcript can be cleaned into a quality asset
Video To Email
Turns a video or transcript into follow-up email content.
Used when:
the video supports a customer journey
the material can educate, nurture, or clarify
Newsletter Insight To Content Asset
Turns an approved newsletter intelligence signal into content planning.
Used when:
HeadOffice approves the signal
the insight fits Content Brain
the topic can support authority, SEO, affiliate, or sales content
Research Note To Content Brief
Turns Research Brain findings into a structured content brief.
Used when:
research identifies a topic, problem, audience language, or market signal worth turning into content
Offer Brief To FAQ
Turns an approved offer brief into FAQ content.
Used when:
the offer has repeated objections
the audience needs safe education
Affiliate Brain or Sales Brain needs support
Content Refresh To Repurposed Asset
Turns refreshed content into new supporting formats.
Used when:
a refreshed asset becomes stronger
the content now has reuse value
the update creates new derivative opportunities
Status Model
The Content Brain Repurposing Queue should use a simple status model first.
Recommended status values:
new
classified
source_review
repurposing_briefing
ready_for_adaptation
adapting
in_review
needs_revision
ready_for_approval
approved
ready_for_handoff
handed_off
published_or_used
monitoring
follow_up_needed
blocked
closed
rejected
Status Definitions
New
The repurposing opportunity has entered the queue but has not yet been classified.
Required next action:
classify source asset and target format
Classified
The item has a source asset, target format, priority, and basic purpose.
Required next action:
review source asset suitability
Source Review
The source asset is being checked for approval status, usefulness, accuracy, risk, and reuse suitability.
Required next action:
approve or reject source asset for adaptation
Repurposing Briefing
A short repurposing brief is being created.
Required next action:
complete adaptation instructions
Ready For Adaptation
The item is clear enough to begin repurposing.
Required next action:
begin adaptation
Adapting
The asset is being rewritten, shortened, expanded, reformatted, or transformed into the target format.
Required next action:
complete target asset draft
In Review
The adapted asset is under quality, accuracy, trust, compliance sensitivity, affiliate, conversion, ads, or publishing readiness review.
Required next action:
complete required reviews
Needs Revision
The adapted asset requires changes before approval or handoff.
Required next action:
revise based on review notes
Ready For Approval
The adapted asset has passed review and requires approval from the correct owner.
Required next action:
approval owner reviews
Approved
The adapted asset has been approved for handoff, publishing, or use.
Required next action:
move to destination or handoff
Ready For Handoff
The adapted asset is ready to transfer to another operator, Brain, or publishing environment.
Required next action:
create handoff note
Handed Off
The adapted asset has been sent to the next owner or destination.
Required next action:
confirm receipt or next use
Published Or Used
The repurposed asset is live, sent, posted, scheduled, or otherwise in use.
Required next action:
monitor defined signal
Monitoring
The asset is being watched after use.
Required next action:
review performance after enough signal exists
Follow Up Needed
The asset created another repurposing, refresh, or content opportunity.
Required next action:
create follow-up item where useful
Blocked
The item cannot progress.
Required next action:
resolve blocker
Common blockers:
source asset not approved
unclear source material
unclear target format
unclear owner
unclear destination
compliance risk
claim risk
offer status unclear
platform requirements unclear
approval required
Closed
The item is complete and no further action is required.
Required next action:
record outcome where useful
Rejected
The repurposing should not proceed.
Required next action:
record reason
Priority Model
The queue should use a simple priority model.
Priority values:
Low
Medium
High
Critical
Low Priority
Useful but optional.
May be future social reuse, optional email content, or low-impact adaptation.
Medium Priority
Relevant and useful.
Should be completed when capacity allows.
High Priority
Important to active content production, affiliate support, sales support, or near-term publishing.
Critical Priority
Required for active funnel support, major campaign support, urgent HeadOffice priority, or time-sensitive content reuse.
Critical priority should be used sparingly.
Ownership Model
Every repurposing queue item must have clear ownership.
Minimum ownership fields:
Repurposing Owner
Review Owner
Approval Owner
Next Owner
Repurposing Owner
The person, AI Employee, or process responsible for completing the adaptation.
Review Owner
The person or Brain responsible for reviewing the adapted asset.
Approval Owner
The person or authority responsible for approving handoff, publishing, or use.
Next Owner
The person or system responsible for the next action.
A repurposing queue item without a next owner is structurally weak.
Request Source Model
Repurposing requests may originate from:
Content Brain
HeadOffice
Research Brain
Affiliate Brain
Ads Brain
Conversion Brain
Sales Brain
Customer Brain
Data Brain
Compliance Brain
manual operator request
approved newsletter intelligence
approved opportunity signal
approved campaign support need
content performance review
SEO review
content refresh review
content production review
manual content audit
Each item must record its request source.
If the request source is unclear, status should remain new or blocked.
Review Requirements
Repurposed content should not move to Approved until relevant reviews are complete.
Possible reviews:
Source Asset Review
Adaptation Review
Meaning Preservation Review
Accuracy Review
Quality Review
Tone Review
Platform Fit Review
SEO Review
Trust Review
Compliance Sensitivity Review
Affiliate Status Review
Conversion Support Review
Ads Support Review
Publishing Readiness Review
Human Approval Review
Not every repurposing item needs every review.
The required reviews depend on source asset, target format, risk level, channel, and destination.
Meaning Preservation Rule
Repurposed content must preserve the meaning of the approved source asset.
The system must prevent:
adding unsupported claims
changing the promise
increasing the strength of claims
removing important limitations
changing the intended audience without review
changing the CTA without review
making the content sound more certain than the source supports
If meaning changes, the item requires review before use.
Channel Fit Rule
Each adapted asset must fit its target channel.
Examples:
email must support a clear reader journey
YouTube descriptions must accurately describe the video or supporting content
social posts must be short, clear, and not misleading
short-form script seeds must be hook-driven but claim-safe
affiliate support assets must match the approved funnel stage
sales support notes must match the Sales Brain progression logic
Content Brain should not force one format into another without adaptation.
Approval Rules
Approval is required before:
publishing repurposed content
sending email content
using repurposed content in active affiliate funnels
using repurposed content in paid campaign support
using health claims
using finance claims
using income claims
using legal claims
using testimonials
using guarantees
using scarcity or urgency language
changing affiliate recommendation content
using content in compliance-sensitive environments
The queue may track approval status.
The queue does not grant approval by itself.
Blocking Rules
A repurposing queue item should be marked blocked when progress cannot continue.
Common blocking reasons:
source asset not approved
source asset unclear
source asset outdated
target format unclear
destination unclear
missing owner
missing source material
missing research evidence
missing approval owner
compliance risk
claim risk
offer status unclear
platform requirements unclear
dependency on another Brain
manual review required
operator decision required
The blocked status must include:
blocked reason
next action
next owner
Handoff Rules
When a repurposed content item is handed off, the handoff note should include:
source asset title
target asset title
source asset location
target format
target destination
requesting Brain
intended use
approval status
risk level
review notes
claims preserved
claims avoided
CTA used
feedback signal to watch
next owner
handoff date
Repurposing handoff must preserve context.
A handoff without context creates rework and risk.
Feedback Rules
Every meaningful repurposed content asset should define at least one signal to watch after use.
Possible signals:
email opens
email clicks
YouTube description clicks
social engagement
watch-time support
comment questions
internal link clicks
VSL click assist
conversion assist
reader questions
audience objection signal
content reuse value
follow-up content opportunity
Feedback may route to:
Research Brain
Affiliate Brain
Ads Brain
Conversion Brain
Sales Brain
Compliance Brain
Data Brain
HeadOffice
Content Brain
Queue Views
The future Content Brain Repurposing Queue should support useful views.
Status View
Groups items by status.
Useful for:
repurposing workflow
bottleneck review
adaptation management
Priority View
Groups items by priority.
Useful for:
deciding what to adapt first
protecting high-value reuse opportunities
Source Asset View
Groups items by source asset.
Useful for:
seeing how many outputs one asset is becoming
avoiding duplicate adaptations
Target Format View
Groups items by target format.
Useful for:
batching email, social, YouTube, or script adaptations
Channel View
Groups items by publishing or usage channel.
Useful for:
planning platform-specific production
Brain Source View
Groups items by requesting Brain.
Useful for:
seeing which Brains need repurposing support
understanding cross-brain demand
Risk View
Groups items by risk level or compliance sensitivity.
Useful for:
review planning
avoiding unsafe reuse
Destination View
Groups items by final destination.
Useful for:
publishing planning
handoff management
Blocked View
Shows only blocked items.
Useful for:
operator review
dependency removal
HeadOffice visibility where needed
Future Data Model
This specification does not activate a database table.
If built later, a future data model may include:
content_repurposing_items
content_repurposing_events
content_repurposing_briefs
content_repurposing_reviews
content_repurposing_handoffs
content_repurposing_signal_feedback
This naming is conceptual only.
Any future Supabase or WordPress implementation must follow MWMS Supabase Naming Standard and MWMS Brain-to-Brain Request Protocol where relevant.
Future Minimal Table Concept
If this becomes a database-backed queue later, a simple first table may include:
id
created_at
updated_at
source_asset_title
source_asset_location
source_asset_type
target_asset_title
target_asset_type
target_channel
request_source
requesting_brain
supporting_brain
repurposing_owner
review_owner
approval_owner
priority
status
repurposing_purpose
risk_level
compliance_sensitivity
affiliate_status
offer_status
draft_location
final_asset_location
target_destination
blocked_reason
next_action
next_owner
feedback_signal
review_date
notes_json
This is not an implementation instruction.
It is a future planning concept only.
First Manual Version
The first version of this queue should be manual.
A manual queue may use:
WordPress page table
simple spreadsheet
Notion-style board
Google Sheet
MCR tracking page
mwmscontentbrain.site page later
Manual use should prove:
which fields are actually needed
which statuses are useful
which repurposing types repeat
which views matter
which bottlenecks repeat
which UI would save time
Only after manual use should a plugin or UI be considered.
Minimum Viable Repurposing Queue
The minimum useful repurposing queue should track:
Source Asset Title
Source Asset Location
Source Asset Type
Target Format
Target Channel
Purpose
Priority
Status
Owner
Next Action
Approval Owner
Risk Level
Destination
Feedback Signal
This is enough to start without overbuilding.
Future Plugin Or UI Candidate
The Content Brain Repurposing Queue is a strong future plugin or UI candidate.
Possible future features:
Add Repurposing Item
Select Source Asset
Select Target Format
Create Repurposing Brief
Attach Adapted Draft
Assign Owner
Set Priority
Change Status
Mark Blocked
Request Review
Approve For Handoff
Mark Published Or Used
Create Follow-Up Repurposing Task
Record Signal Feedback
Filter By Source Asset
Filter By Target Format
Filter By Channel
Filter By Brain
Filter By Status
Filter By Priority
Filter By Risk
This should not be built yet.
Manual workflow must prove the need first.
Relationship To Content Brain Copy Map
This page should be listed in the Content Brain Copy Map as:
Page Title: Content Brain Repurposing Queue Specification
Destination: Later Plugin Or UI
Reason: Repeated structured interaction, asset reuse tracking, multi-format adaptation planning, status tracking, channel-specific production visibility, and repurposing workflow management
Source Of Truth: MCR
Future Use: Content repurposing tracking screen inside mwmscontentbrain.site
Future Plugin Or UI: Yes
Relationship To Content Brain Page Registry
This page should be added to the Content Brain Page Registry as:
Page Title: Content Brain Repurposing Queue Specification
Document Type: Specification
Parent Page: Content Brain
Status: Draft
Destination: Later Plugin Or UI
Reason: Future content repurposing tracking system
Source Of Truth: MCR
Future Use: Content repurposing queue planning
Relationship To Content Brain Operating Model
The Content Brain Operating Model defines Content Brain’s role and responsibilities.
This specification defines a future system for tracking repurposing responsibilities as approved source assets move into new formats.
Operating Model = role and boundaries
Repurposing Queue Specification = future asset adaptation tracking surface
Relationship To Content Brain Workflow Map
The Content Brain Workflow Map defines the movement of content work.
The Content Brain Repurposing Queue tracks repurposing movement for approved content assets.
Workflow Map = process
Repurposing Queue = reuse visibility layer
Relationship To Content Brain Content Production Queue Specification
The Content Production Queue tracks new content production.
The Repurposing Queue tracks approved content reuse into new formats.
Production Queue = new content work
Repurposing Queue = derivative content work
The two queues should remain separate to prevent new production work and repurposing work from becoming confused.
Relationship To Content Brain Content Refresh Queue Specification
The Content Refresh Queue tracks improvement of existing content.
The Repurposing Queue tracks adaptation of approved assets into new formats.
Refresh Queue = existing content improvement work
Repurposing Queue = approved asset reuse work
A refreshed asset may later create a repurposing task.
Relationship To Content Brain Content Brief Template
The Content Brief Template defines the planning document before drafting.
Repurposing tasks may require a shorter repurposing brief or adaptation instruction.
Brief Template = new content planning control
Repurposing Queue = derivative content adaptation control
Relationship To Content Brain Publishing Readiness Checklist
The Publishing Readiness Checklist defines the gate before publishing or handoff.
Repurposed content should pass publishing readiness before use where risk exists.
Publishing Readiness Checklist = review gate
Repurposing Queue = status visibility
Relationship To Content Brain Affiliate Funnel Support Map
Affiliate-related repurposing items should record:
related offer
offer status
affiliate support role
funnel stage
claim risk
approval owner
source asset approval status
Affiliate Funnel Support Map = affiliate content use case
Repurposing Queue = tracking system for derivative affiliate support assets
Relationship To Content Brain Content Repurposing Framework
The Content Repurposing Framework defines the principles and logic of repurposing.
The Content Brain Repurposing Queue tracks those decisions operationally.
Content Repurposing Framework = decision and method logic
Content Brain Repurposing Queue = workflow tracking surface
Relationship To Other MWMS Documents
This page must align with:
Content Brain Copy Map
Content Brain Page Registry
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
Content Brain Affiliate Funnel Support Map
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Content Repurposing Framework
Content Brain Content Optimization Framework
Content Brain Content Signal Feedback Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Brain To Brain Request Protocol
MWMS Supabase Naming Standard
MWMS Supabase Task Schema Standard
MWMS Document Structure Standard
MWMS Page Naming Standard
MWMS AI Output Standard Full File Delivery Rule
Drift Protection
The system must prevent:
repurposing work being tracked without source asset
repurposing work entering the queue without purpose
repurposing queue items having no owner
repurposing queue items having no next action
repurposing queue items staying blocked without reason
repurposed content being approved without review
repurposed content being published without approval
affiliate content being repurposed without offer status
compliance-sensitive content being repurposed without risk flag
source claims being strengthened without evidence
source meaning being changed without review
channel-specific requirements being ignored
the repurposing queue becoming a dumping ground
the repurposing queue replacing Brain authority
the repurposing queue granting approval by itself
the repurposing queue being built as a plugin before manual workflow proves the need
the repurposing queue interfering with M’s active build areas
mwmscontentbrain.site becoming a duplicate of MCR
Architectural Intent
The Content Brain Repurposing Queue Specification exists to make future content reuse visible, controlled, and scalable.
Its role is to define the future repurposing queue before implementation so that Content Brain can extract more value from strong assets without creating chaos, repetition, or unsafe claims.
The queue should help MWMS know:
which assets are worth reusing
why they are worth reusing
which formats they should become
who owns the adaptation
what risk exists
what approval is required
what is blocked
what has been handed off
what has been published or used
what signal should be watched after use
The long-term intent is to support a practical operational repurposing queue on mwmscontentbrain.site while preserving MCR as the source of truth.
Final Rule
The Content Brain Repurposing Queue must track approved asset reuse.
It must not create authority.
If a repurposing item has no source asset, no purpose, no target format, no owner, no next action, and no feedback path, it should not enter the queue.
If the queue does not improve content reuse visibility, it should not be built yet.
Change Log
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change: Initial creation of Content Brain Repurposing Queue Specification defining the future content repurposing queue structure, source asset tracking, target format tracking, repurposing types, queue fields, status model, priority model, ownership model, review requirements, meaning preservation rule, handoff rules, feedback rules, future views, minimal queue structure, future plugin or UI candidate logic, and drift protection.
Change Impact Declaration
Pages Created:
Content Brain Repurposing Queue Specification
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Change Log Entry Required:
No