Brain Name: Content Brain
Document Type: Active Operational Workflow
Status: Active Operational Workflow
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, Content Brain Site Content Intelligence Framework, Content Brain Site Content Intelligence Report Template, Content Brain Site Content Intelligence Report Generator Specification, Content Brain Content Briefs, Content Brain SEO Content Briefs, Content Brain Affiliate Content Packs, Content Brain Affiliate Funnel Support, Content Brain Publishing Readiness, Content Brain Internal Linking, Content Brain Refresh, Content Brain Repurposing, Content Brain Publishing Readiness Status Values Framework, Content Brain Source Depth And Evidence Label Framework, Content Brain Offer Evidence Requirements Framework, Content Brain Compliance Routing Needs Framework, Content Brain Human Approval Points Framework, Content Brain Future Fields To Define Later Framework, future Content Brain build readiness planning, future content workflow standardisation, and future Content Brain specification candidate work
Parent: Content Brain
Last Reviewed: 2026-06-08
Content Brain Site Intelligence To Content Brief Workflow
Purpose
The purpose of this page is to define how Content Brain should turn a Site Content Intelligence Report into the correct next content workflow.
This page exists because Site Content Intelligence is only useful if it leads to the right next action.
A Site Content Intelligence Report should not simply list gaps.
It should help Content Brain decide whether to create a content brief, create an SEO brief, create an affiliate product content pack, refresh an existing page, plan internal links, repurpose an asset, route to another Brain, park the work, or avoid creating content altogether.
This page defines the manual workflow between:
Site Content Intelligence
and
Content Brief creation
SEO Brief creation
Affiliate Content Pack creation
Affiliate Funnel Support
Publishing Readiness
Internal Linking
Refresh
Repurposing
Research Brain routing
Search Intelligence Brain routing
Affiliate Brain routing
Compliance Brain routing
HeadOffice review
This page does not authorise build work.
This page does not create plugin instructions.
This page does not create UI instructions.
This page does not create Supabase instructions.
This page does not create Brain Room routing instructions.
This page does not create automation instructions.
This page does not create queue instructions.
This page does not create dashboard instructions.
This page does not create generator instructions.
This page does not create AI Employee instructions.
This page does not create M handoff instructions.
This page is a manual operational workflow only.
Current Status
Current Content Brain status:
Manual Workflow Only
Plugin UI Not Started
No Supabase Work Started
No Brain Room Routing Started
No Automation Started
No Queue Build Started
No Dashboard Build Started
No Generator Build Started
No AI Employee Build Started
No Cross Brain Routing Build Started
M’s Active Build Work Untouched
Current evidence stage:
Manual Workflow Evidence Stage
Current planning stage:
Build Readiness Planning Stage
Current page role:
Active Operational Workflow
Current maturity status:
Workflow usable
Evidence backed
Manual ready
Site aware
Site Content Intelligence Framework created
Site Content Intelligence Report Generator Specification created
Publishing readiness status values created
Source depth labels created
Offer evidence requirements created
Compliance routing logic created
Human approval points created
Future field parking discipline created
Site Content Intelligence Report Template created
Site Intelligence to next workflow routing now requires standardisation
Future UI not authorised
Future generator not authorised
Future queue not authorised
Future M handoff not authorised
This page is a manual workflow page only.
Why This Page Is Needed
Content Brain can now review a site and produce a Site Content Intelligence Report.
However, the report must not become a dead document.
The report should create action.
The report should help answer:
Should we create new content?
Should we refresh an existing page?
Should we avoid duplicate content?
Should we create an SEO brief?
Should we create an affiliate content pack?
Should we support a VSL?
Should we improve internal linking?
Should we repurpose existing content?
Should we route to Research Brain?
Should we route to Search Intelligence Brain?
Should we route to Affiliate Brain?
Should we route to Compliance Brain?
Should HeadOffice approve the next move?
Should the work be parked?
Without this workflow, Site Content Intelligence could create more notes but not better action.
This page turns site intelligence into controlled next-step decisions.
Core Principle
Site Content Intelligence should not automatically create new content.
The first decision after reviewing a site is not:
What new article should we write?
The first decision is:
What is the correct next Content Brain action?
Sometimes the correct next action is a new content brief.
Sometimes it is a refresh.
Sometimes it is internal linking.
Sometimes it is repurposing.
Sometimes it is a research request.
Sometimes it is a compliance review.
Sometimes it is no content.
Sometimes it is HeadOffice review.
Content Brain must choose the right workflow before creating more assets.
Input To This Workflow
This workflow starts with a completed or partial Site Content Intelligence Report.
The report may include:
site purpose summary
source depth label
evidence quality label
content inventory
site voice and tone summary
topic coverage map
content gap list
duplicate or overlap warnings
thin content warnings
refresh opportunities
repurposing opportunities
internal linking opportunities
trust signal summary
affiliate support gap review
offer evidence notes
compliance routing notes
reader journey notes
SEO structure notes
recommended next content assets
pages to avoid creating
site specific content instructions
recommended routing
human approval points
final readiness status
The report does not need to be perfect.
However, it must be clear enough to support a next workflow decision.
Output From This Workflow
This workflow should produce one clear next action.
Possible outputs include:
Create Content Brief
Create SEO Content Brief
Create Affiliate Product Content Pack
Create Affiliate Funnel Support Asset
Use Content Brain Refresh
Use Content Brain Internal Linking
Use Content Brain Repurposing
Use Content Brain Publishing Readiness
Route To Research Brain
Route To Search Intelligence Brain
Route To Affiliate Brain
Route To Compliance Brain
Route To HeadOffice
Park Pending Clarity
Do Not Create Content
Create Shortlist Of Next Content Assets
Create Manual Follow Up Review
The output should name:
the next operational page
the reason
the evidence basis
the blocking issues
the approval point
the expected next deliverable
Workflow Decision Sequence
Use this sequence after completing a Site Content Intelligence Report.
Step 1: Confirm Source Depth
Check the source depth label.
Ask:
Was this a surface review?
Was this a basic site review?
Was this a multi page site review?
Was full page content supplied?
Was source material reviewed?
Was offer page or VSL evidence reviewed?
Is the evidence depth unknown?
If source depth is shallow, do not make strong recommendations.
If source depth is unknown, use caution or route for review.
Possible next status:
Needs Source Review
Parked Pending Clarity
Research Required
Search Intelligence Required
Compliance Review Required
Step 2: Confirm Site Purpose
Ask:
Is the site purpose clear?
Is the audience clear?
Is the business model clear?
Is the primary content role clear?
Is the offer context clear where relevant?
If site purpose is unclear, do not create a content brief yet.
Possible next action:
Park Pending Clarity
Route To HeadOffice
Run deeper Site Content Intelligence review
Step 3: Check For Duplicate Or Overlap Risk
Ask:
Does the proposed content already exist?
Is there a similar page?
Is there a similar intent?
Is there a similar affiliate support role?
Is there a similar FAQ or comparison page?
Would new content create cannibalisation or confusion?
If yes, do not create a new brief immediately.
Possible next action:
Use Content Brain Refresh
Use Content Brain Internal Linking
Merge or expand existing page
Create a differentiated spoke page only if justified
Do Not Create Content
Step 4: Check For Refresh Opportunities
Ask:
Is an existing page outdated?
Is an existing page thin?
Is an existing page missing trust signals?
Is an existing page missing internal links?
Is an existing page off tone?
Is an existing page better to improve than creating something new?
If yes, the next step may be refresh, not new content.
Possible next action:
Use Content Brain Refresh
Route To Compliance Brain if claims are risky
Route To Research Brain if evidence is missing
Use Publishing Readiness after refresh
Step 5: Check For Internal Linking Opportunities
Ask:
Are there missing hub to spoke links?
Are there orphan pages?
Are trust pages disconnected?
Are affiliate support pages disconnected?
Are reader journey links missing?
Are product links too early or too aggressive?
If yes, the next step may be internal linking.
Possible next action:
Use Content Brain Internal Linking
Create internal linking plan
Route to Search Intelligence Brain if search structure needs validation
Route to HeadOffice if site architecture priority is unclear
Step 6: Check For Repurposing Opportunities
Ask:
Is there existing approved content that can be reused?
Can a page become email support?
Can a guide become a checklist?
Can an FAQ become support content?
Can an article become a YouTube description?
Can a framework become client facing content?
If yes, the next step may be repurposing.
Possible next action:
Use Content Brain Repurposing
Check claim strength
Check meaning preservation
Check audience stage
Check compliance risk
Step 7: Check For Content Gaps
Ask:
Is the gap real?
Does it help the reader?
Does it support search usefulness?
Does it support trust?
Does it support affiliate education?
Does it support internal linking?
Does it support publishing readiness?
Does it support a campaign?
Does it support a known business goal?
If the gap is real, decide which kind of content is needed.
Possible next action:
Create Content Brief
Create SEO Content Brief
Create Affiliate Product Content Pack
Create Affiliate Funnel Support Asset
Route To Research Brain
Route To Search Intelligence Brain
Route To Affiliate Brain
Route To Compliance Brain
Step 8: Check For Search Intent
Ask:
Is the content primarily search driven?
Does the topic need SERP validation?
Is search intent unclear?
Could there be keyword cannibalisation?
Does the topic cluster need validation?
If yes, do not treat Content Brain as Search Intelligence Brain.
Possible next action:
Create SEO Content Brief only if search context is sufficient
Route To Search Intelligence Brain if validation is needed
Park SEO work until validation is complete
Step 9: Check For Affiliate Offer Dependency
Ask:
Does the content support an affiliate offer?
Does it support a VSL?
Does it support a bridge page?
Does it support a product review or comparison?
Does it support buyer objections?
Does it require offer evidence?
If yes, check offer evidence before content planning.
Possible next action:
Use Content Brain Affiliate Content Packs
Use Content Brain Affiliate Funnel Support
Route To Affiliate Brain
Route To Research Brain
Route To Compliance Brain
Park until offer evidence is complete
Step 10: Check For Compliance Risk
Ask:
Are there claims?
Are they sensitive?
Are they supported?
Is there affiliate disclosure risk?
Is there VSL claim risk?
Is there urgency or scarcity risk?
Is there misleading curiosity risk?
Is there ad to page mismatch risk?
If yes, do not proceed as normal content.
Possible next action:
Route To Compliance Brain
Needs Claim Softening
Needs Evidence Before Compliance
Ready For HeadOffice Review
Do Not Use Until Reviewed
Step 11: Check For Human Approval Points
Ask:
Does this need public use approval?
Does this affect an affiliate campaign?
Does this affect a bridge page?
Does this affect paid traffic?
Does this affect future build readiness?
Does this require HeadOffice direction?
If yes, record the approval point before continuing.
Possible next action:
Ready For HeadOffice Review
Approved For Manual Planning
Approved For Drafting
Approved For Publishing Review
Do Not Approve
Step 12: Choose The Next Operational Page
Select only one primary next operational page where possible.
Possible choices:
Content Brain Content Briefs
Content Brain SEO Content Briefs
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
Content Brain Publishing Readiness
Content Brain Internal Linking
Content Brain Refresh
Content Brain Repurposing
Content Brain Workflow
If more than one applies, choose the upstream blocker first.
Example:
If content needs both SEO brief and Search Intelligence validation, route to Search Intelligence first.
If content needs both affiliate pack and offer evidence, resolve offer evidence first.
If content needs both refresh and compliance review, identify claim risk before final refresh approval.
Decision Outcomes
Use the following decision outcomes.
Outcome 1: Create General Content Brief
Use when:
site purpose is clear
audience is clear
content gap is real
content is not primarily SEO driven
content is not strongly affiliate dependent
claim risk is low
existing content does not already solve the need
Next page:
Content Brain Content Briefs
Required notes:
site tone summary
audience stage
content purpose
existing pages to link
pages to avoid duplicating
source depth
approval point
Outcome 2: Create SEO Content Brief
Use when:
content gap has search intent
topic appears useful for search
site has relevant topic structure
no obvious duplicate exists
Search Intelligence validation is complete or not required yet
Next page:
Content Brain SEO Content Briefs
Required notes:
search intent
topic cluster
existing related pages
cannibalisation risk
source depth
Search Intelligence requirement
approval point
Outcome 3: Create Affiliate Product Content Pack
Use when:
site supports an affiliate offer
offer evidence is strong enough for planning
content pack is needed for education, trust, FAQs, objections, comparisons, or VSL support
affiliate support gaps are clear
Next page:
Content Brain Affiliate Content Packs
Required notes:
offer evidence status
VSL context
claim risk
affiliate disclosure needs
reader awareness stage
support content gaps
approval point
Outcome 4: Create Affiliate Funnel Support Asset
Use when:
content must support a specific funnel stage
problem awareness, solution awareness, product education, trust, pre sell, objection handling, or VSL preparation is needed
Next page:
Content Brain Affiliate Funnel Support
Required notes:
funnel stage
reader state
offer evidence status
CTA fit
claim risk
approval point
Outcome 5: Refresh Existing Page
Use when:
existing content should be improved instead of creating new content
page is outdated, weak, thin, duplicated, risky, or misaligned
Next page:
Content Brain Refresh
Required notes:
page to refresh
refresh trigger
source depth
claim risk
internal links needed
publishing readiness status
approval point
Outcome 6: Plan Internal Links
Use when:
site intelligence identifies missing or weak internal links
reader journey needs stronger pathways
hub and spoke structure needs improvement
affiliate or trust support pages need better connection
Next page:
Content Brain Internal Linking
Required notes:
source page
target page
link purpose
reader journey role
risk notes
approval point
Outcome 7: Repurpose Existing Content
Use when:
existing approved content can be safely reused
meaning can be preserved
claim strength will not increase
audience stage remains appropriate
Next page:
Content Brain Repurposing
Required notes:
source asset
target format
meaning preservation risk
claim strength risk
approval point
Outcome 8: Route To Research Brain
Use when:
facts are missing
claims need evidence
audience evidence is weak
comparison facts are unclear
source material is missing
scientific or factual support is required
Next Brain:
Research Brain
Required notes:
research question
claim needing evidence
source depth
content decision blocked
Outcome 9: Route To Search Intelligence Brain
Use when:
search intent is unclear
SERP fit matters
keyword cannibalisation may exist
topic cluster search value is unclear
SEO opportunity needs validation
Next Brain:
Search Intelligence Brain
Required notes:
search question
target topic
existing page conflict
SEO decision blocked
Outcome 10: Route To Affiliate Brain
Use when:
offer logic is unclear
offer suitability is uncertain
affiliate funnel role is unclear
commission or network context matters
offer should possibly be parked
Next Brain:
Affiliate Brain
Required notes:
offer name
offer evidence status
content dependency
decision needed
Outcome 11: Route To Compliance Brain
Use when:
claim risk exists
disclosure risk exists
VSL claim risk exists
urgency or scarcity risk exists
misleading curiosity risk exists
ad to page match risk exists
Next Brain:
Compliance Brain
Required notes:
claim category
content asset
risk reason
source depth
desired review
Outcome 12: Route To HeadOffice
Use when:
priority is unclear
strategic direction is needed
cross brain authority is unclear
public risk exists
campaign impact exists
future build readiness is involved
Next Brain:
HeadOffice
Required notes:
decision needed
options
risk
recommendation
Outcome 13: Park Pending Clarity
Use when:
site purpose is unclear
audience is unclear
source depth is too weak
offer evidence is missing
priority is unclear
content type is unclear
approval owner is unclear
Next status:
Parked Pending Clarity
Required notes:
what is unclear
what must be clarified
who should clarify it
Outcome 14: Do Not Create Content
Use when:
content would duplicate existing material
content is too thin
claim risk is too high
offer evidence is too weak
content would not help the reader
site does not need the asset
the idea is not worth pursuing now
Next status:
Do Not Use
or
Do Not Create Content
Required notes:
reason
better action
approval owner if needed
Site Intelligence To Brief Handoff Template
Use this template when a Site Content Intelligence Report becomes a content brief.
Site Intelligence To Brief Handoff
Source Report:
Site Reviewed:
Source Depth Label:
Evidence Quality Label:
Recommended Next Operational Page:
Content Asset Recommended:
Reason This Asset Is Needed:
Existing Pages To Use:
Pages To Avoid Duplicating:
Content Gap Being Solved:
Audience Stage:
Site Tone Notes:
Internal Link Notes:
Offer Evidence Status:
Compliance Routing Needed:
Human Approval Required:
Approval Scope:
Recommended Next Step:
Do Not Include:
Notes:
Site Intelligence To SEO Brief Handoff Template
Use this template when the next step is SEO Content Briefs.
Site Intelligence To SEO Brief Handoff
Source Report:
Site Reviewed:
Target Topic:
Search Intent Assumption:
Search Intelligence Required:
Existing Related Pages:
Cannibalisation Risk:
Topic Cluster Role:
Hub Or Spoke Role:
Content Gap Being Solved:
Internal Link Opportunities:
Evidence Quality:
Compliance Risk:
Human Approval Required:
Recommended Next Step:
Notes:
Site Intelligence To Affiliate Content Pack Handoff Template
Use this template when the next step is Affiliate Content Packs.
Site Intelligence To Affiliate Content Pack Handoff
Source Report:
Site Reviewed:
Offer Name:
Affiliate Network:
Vendor:
Offer Evidence Status:
VSL Context Known:
Primary Promise:
Mechanism Known:
Proof Evidence Status:
Affiliate Support Gap:
Reader Awareness Stage:
Needed Content Assets:
Claims To Avoid:
Compliance Routing Needed:
Disclosure Review Needed:
Human Approval Required:
Recommended Next Step:
Notes:
Site Intelligence To Refresh Handoff Template
Use this template when the next step is Refresh.
Site Intelligence To Refresh Handoff
Source Report:
Site Reviewed:
Page To Refresh:
Refresh Trigger:
Current Issue:
Recommended Refresh Type:
Source Depth Label:
Evidence Quality Label:
Claim Risk:
Offer Evidence Needed:
Internal Links Needed:
Publishing Readiness Status:
Human Approval Required:
Recommended Next Step:
Notes:
Site Intelligence To Internal Linking Handoff Template
Use this template when the next step is Internal Linking.
Site Intelligence To Internal Linking Handoff
Source Report:
Site Reviewed:
Source Page:
Target Page:
Link Purpose:
Reader Journey Role:
Topic Cluster Role:
Trust Support Role:
Affiliate Support Role:
Risk Notes:
Search Intelligence Required:
Human Approval Required:
Recommended Next Step:
Notes:
Site Intelligence To Repurposing Handoff Template
Use this template when the next step is Repurposing.
Site Intelligence To Repurposing Handoff
Source Report:
Site Reviewed:
Source Asset:
Target Format:
Repurposing Purpose:
Audience Stage:
Meaning Preservation Risk:
Claim Strength Risk:
Compliance Routing Needed:
Human Approval Required:
Recommended Next Step:
Notes:
Site Intelligence To Brain Routing Template
Use this template when the next step is another Brain.
Site Intelligence To Brain Routing
Source Report:
Site Reviewed:
Recommended Brain:
Reason For Routing:
Decision Needed:
Evidence Available:
Evidence Missing:
Source Depth Label:
Risk Level:
Content Decision Blocked:
Recommended Output From Receiving Brain:
Human Approval Required:
Notes:
Workflow Status Values
Use the following status values for this workflow.
Ready For Content Brief
Meaning:
Site intelligence is strong enough to create a general content brief.
Ready For SEO Brief
Meaning:
Site intelligence supports SEO brief creation, and Search Intelligence is either not required yet or has been addressed.
Ready For Affiliate Content Pack
Meaning:
Site intelligence and offer evidence are strong enough for affiliate content pack planning.
Ready For Refresh
Meaning:
Existing page improvement is the correct next step.
Ready For Internal Linking
Meaning:
Internal linking plan is the correct next step.
Ready For Repurposing
Meaning:
Existing content can be safely adapted after review.
Needs Research Brain
Meaning:
Evidence is missing or claims require verification.
Needs Search Intelligence Brain
Meaning:
SEO or SERP validation is needed.
Needs Affiliate Brain
Meaning:
Offer logic or affiliate strategy is unclear.
Needs Compliance Brain
Meaning:
Claim, disclosure, platform, or policy risk requires review.
Needs HeadOffice
Meaning:
Strategic direction or approval is required.
Parked Pending Clarity
Meaning:
The next step cannot be chosen yet.
Do Not Create Content
Meaning:
New content should not be created.
Common Mistakes To Avoid
Do not turn every content gap into a new content brief.
Do not create a new SEO brief when an existing page should be refreshed.
Do not create affiliate support content without offer evidence.
Do not create VSL support content without claim review.
Do not route search questions to Content Brain when Search Intelligence is needed.
Do not route evidence questions to Content Brain when Research Brain is needed.
Do not treat Site Content Intelligence as final compliance review.
Do not treat a template output as approval.
Do not use vague status language.
Do not skip human approval points.
Do not send planning pages to M.
Do not start build work from this workflow.
Relationship To Site Content Intelligence Report Template
The Site Content Intelligence Report Template creates the report.
This workflow decides what to do after the report.
The report answers:
What does the site show?
This workflow answers:
What should Content Brain do next?
Relationship To Content Brain Content Briefs
Use Content Brain Content Briefs only when the Site Content Intelligence Report shows that new general content is the correct next action.
Do not use Content Briefs when the better action is refresh, linking, repurposing, research, search validation, affiliate review, compliance review, or HeadOffice review.
Relationship To Content Brain SEO Content Briefs
Use Content Brain SEO Content Briefs only when search content is the correct next action and search uncertainty is low enough to proceed.
If search intent, SERP fit, or cannibalisation risk is unclear, route to Search Intelligence Brain first.
Relationship To Content Brain Affiliate Content Packs
Use Content Brain Affiliate Content Packs only when affiliate support content is needed and offer evidence is strong enough for planning.
If offer evidence is missing, route to Affiliate Brain, Research Brain, Compliance Brain, or HeadOffice first.
Relationship To Content Brain Refresh
Use Content Brain Refresh when an existing page should be improved instead of creating new content.
This is especially important when site intelligence finds overlap, outdated pages, thin pages, or weak trust pages.
Relationship To Content Brain Internal Linking
Use Content Brain Internal Linking when the main issue is page relationship, reader journey, hub and spoke structure, or link support.
Do not treat internal linking as SEO only.
Relationship To Content Brain Repurposing
Use Content Brain Repurposing when existing approved content can be reused safely.
Do not repurpose claim-sensitive content without source depth and compliance review.
Relationship To Publishing Readiness
Publishing Readiness should check outputs before they leave Content Brain.
This workflow may recommend a next content step, but it does not approve public use.
Relationship To Human Approval Points
This workflow must identify human approval points before work moves forward.
If approval scope is unclear, use Ready For HeadOffice Review or Parked Pending Clarity.
Relationship To Future Report Generator
This workflow may later support a future Site Content Intelligence Report Generator by defining how the report output should connect to downstream Content Brain workflows.
This page does not authorise that generator.
Relationship To Future Fields
This workflow may reveal useful future fields, such as:
Recommended Next Operational Page
Recommended Next Brain
Content Decision Outcome
Workflow Status
Routing Reason
Human Approval Required
These are future field candidates only.
They are not approved database fields.
Relationship To M Handoff
This page is not an M handoff pack.
Do not give this page to M as implementation instructions.
M should not build from this page.
This page may later support future technical specifications if HeadOffice approves that maturity step.
Drift Protection
This workflow prevents:
site intelligence reports becoming dead documents
content gaps turning into automatic content creation
duplicate content creation
refresh opportunities being ignored
internal linking opportunities being missed
repurposing opportunities being ignored
affiliate content being created without offer evidence
compliance risk being bypassed
search validation being skipped
research gaps being ignored
human approval points being skipped
future generators being planned without downstream workflow logic
future fields being created too early
M receiving premature implementation instructions
Recommended Next Step
Use this workflow after the next Site Content Intelligence Report is created.
Do not build UI.
Do not build queues.
Do not build dashboards.
Do not build generators.
Do not build AI Employees.
Do not create Supabase fields.
Do not create database schema.
Do not create M handoff instructions.
Registry update:
Deferred until end of day batch update.
Pending registry entry:
Content Brain Site Intelligence To Content Brief Workflow
Status:
Active Operational Workflow
Version:
v1.0
Parent:
Content Brain
Expected page count impact:
Previous expected page count:
49 pages
New expected page count:
50 pages
Change Impact Declaration
Pages Created:
Content Brain Site Intelligence To Content Brief Workflow
Pages Updated:
None immediately
Pages Renamed:
None
Pages Deleted:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry at end of day batch update
Canon Version Update Required:
No
Architecture Version Update Required:
No
Manual Workflow Test Log Update Required:
No
Manual Workflow Synthesis Report Update Required:
No
Build Readiness Shortlist Update Required:
No
Plugin UI Impact:
None
Supabase Impact:
None
Brain Room Routing Impact:
None
Automation Impact:
None
Queue Impact:
None
Dashboard Impact:
None
Generator Build Impact:
None
AI Employee Impact:
None
Cross Brain Routing Impact:
None
M Active Build Impact:
None
Page Count Impact:
Previous expected page count:
49 pages
New expected page count:
50 pages
Registry update timing:
Deferred until end of day batch update
Change Log
Version: v1.0
Date: 2026-06-08
Author: HeadOffice
Change:
Created Content Brain Site Intelligence To Content Brief Workflow as an Active Operational Workflow.
Defined how Content Brain should turn a Site Content Intelligence Report into the correct next content workflow.
Added workflow decision sequence, decision outcomes, handoff templates for Content Briefs, SEO Briefs, Affiliate Content Packs, Refresh, Internal Linking, Repurposing, and Brain routing.
Added workflow status values, common mistakes to avoid, relationships to Site Content Intelligence Report Template, Content Brain Content Briefs, SEO Content Briefs, Affiliate Content Packs, Refresh, Internal Linking, Repurposing, Publishing Readiness, Human Approval Points, future report generator, future fields, M handoff, drift protection, and recommended next step.
Confirmed this page does not authorise plugin UI, Supabase, Brain Room routing, automation, queues, dashboards, generators, AI Employees, cross brain routing, or M implementation handoff.
End Of Day Save Point Template
Page list checked:
Yes / No
Content Brain Site Content Intelligence Report Generator Specification created:
Yes / No
Content Brain Publishing Readiness Status Values Framework created:
Yes / No
Content Brain Source Depth And Evidence Label Framework created:
Yes / No
Content Brain Offer Evidence Requirements Framework created:
Yes / No
Content Brain Compliance Routing Needs Framework created:
Yes / No
Content Brain Human Approval Points Framework created:
Yes / No
Content Brain Future Fields To Define Later Framework created:
Yes / No
Content Brain Site Content Intelligence Report Template created:
Yes / No
Content Brain Site Intelligence To Content Brief Workflow created:
Yes / No
Content Brain Page Registry updated today:
Yes / No
Registry update deferred:
Yes / No
Pages created:
Content Brain Site Content Intelligence Report Generator Specification
Content Brain Publishing Readiness Status Values Framework
Content Brain Source Depth And Evidence Label Framework
Content Brain Offer Evidence Requirements Framework
Content Brain Compliance Routing Needs Framework
Content Brain Human Approval Points Framework
Content Brain Future Fields To Define Later Framework
Content Brain Site Content Intelligence Report Template
Content Brain Site Intelligence To Content Brief Workflow
Pages updated:
None / Content Brain Page Registry if updated at closeout
Pages renamed:
None
Pages deleted:
None
Current expected page count:
50 pages / other
No plugin UI started:
Yes / No
No Supabase work started:
Yes / No
No Brain Room routing started:
Yes / No
No automation started:
Yes / No
No queue work started:
Yes / No
No dashboard work started:
Yes / No
No generator build started:
Yes / No
No AI Employee work started:
Yes / No
No cross brain routing started:
Yes / No
M’s active work untouched:
Yes / No
Target save point:
Content Brain — Site Intelligence To Content Brief Workflow Created / Registry Update Deferred / Build Readiness Planning Stage / Manual Workflow Only / Plugin UI Not Started
Final Rule
A Site Content Intelligence Report should not automatically create new content.
The correct next action may be a content brief, SEO brief, affiliate content pack, refresh, internal linking, repurposing, research route, search route, affiliate route, compliance route, HeadOffice review, parking, or no content creation.
Content Brain must choose the correct next workflow before creating more assets.
This workflow is manual operating logic only.
It is not build approval.
END CONTENT BRAIN SITE INTELLIGENCE TO CONTENT BRIEF WORKFLOW v1.0
Date: 2026-06-11
Author: HeadOffice
Correction:
Content Brain Output Layer Operating Workflow should not be created as a standalone MCR page.
Reason:
Existing MCR source-of-truth page Content Brain Site Intelligence To Content Brief Workflow v1.0 already defines the manual workflow between Site Content Intelligence and Content Brief creation, SEO Brief creation, Affiliate Content Pack creation, Affiliate Funnel Support, Publishing Readiness, Internal Linking, Refresh, Repurposing, Research Brain routing, Search Intelligence Brain routing, Affiliate Brain routing, Compliance Brain routing, and HeadOffice review.
Decision:
Do not create Content Brain Output Layer Operating Workflow as standalone.
Correct Handling:
Use Content Brain Site Intelligence To Content Brief Workflow v1.0 as the source of truth for this operating sequence.
Pages Created:
None
Pages Updated:
None yet
Pages Deprecated:
None
Pages To Avoid Creating:
Content Brain Output Layer Operating Workflow
Pages On Hold:
Content Brain Output Style Selector Specification
Content Brain Output Layer Screen Specification
Registries Requiring Update:
No, if the duplicate page was not created.
Canon Version Update Required:
No
Change Log Entry Required:
Optional correction note only if today’s working log is tracking avoided duplicate pages.
Strategic Result:
Prevented duplicate Content Brain workflow bloat and restored MCR source-of-truth discipline before creating more output-layer pages.