Brain Name: Content Brain
Document Type: Build-Readiness Planning Report
Status: Active Build-Readiness Planning Report
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, Manual Workflow Tests 1–10, Manual Workflow Synthesis Report, future Content Brain build-readiness planning, future Content Brain specification candidate selection, future M handoff preparation, manual workflow evidence review, and Content Brain system maturity planning
Parent: Content Brain
Last Reviewed: 2026-06-05
Content Brain Build-Readiness Shortlist
Purpose
The purpose of this page is to turn the evidence from Manual Workflow Tests 1–10 and the Content Brain Manual Workflow Synthesis Report into a clean build-readiness shortlist.
This page does not authorize technical build work.
This page does not create a plugin specification.
This page does not create a UI specification.
This page does not create a Supabase specification.
This page does not create a Brain Room routing specification.
This page does not create an automation specification.
This page exists to decide which future build candidates appear strongest, which should wait, which should stay manual, and which candidate should most likely become the first future specification candidate later.
The purpose is to create a planning bridge between manual workflow evidence and future build specification work.
Current Status
Content Brain has completed Manual Workflow Tests 1–10.
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 maturity status:
Workflow-usable
Evidence-backed
Not plugin/UI-ready
Not automation-ready
Not build-ready
Not yet M-handoff-ready
Current planning step:
Build-readiness shortlist creation
This page creates the first clean shortlist of possible future build candidates.
Evidence Source
This shortlist is based on:
Content Brain Manual Workflow Test Log
Version: v2.0
Status: Active Operational Log
Parent: Content Brain
Content Brain Manual Workflow Synthesis Report
Version: v1.0
Status: Active Operational Evidence Report
Parent: Content Brain
Content Brain Page Registry
Version before this page: v2.2
Status: Active Operational Registry
Parent: Content Brain
The Manual Workflow Test Log records the detailed test evidence.
The Manual Workflow Synthesis Report interprets the evidence.
This Build-Readiness Shortlist prioritises the strongest future build candidates based on that evidence.
Shortlist Criteria
Future build candidates are grouped using the following criteria.
Tier 1 Criteria
A candidate belongs in Tier 1 if it:
appeared repeatedly across manual workflow tests
supports multiple downstream workflows
reduces repeated operator friction
improves workflow consistency
helps prevent blind content creation
supports future specification work
could eventually help M wire proven logic
is upstream of other Content Brain workflows
can be defined later without starting technical build immediately
Tier 2 Criteria
A candidate belongs in Tier 2 if it:
has strong evidence but depends on another upstream workflow
supports important Content Brain operations
needs more standardisation before specification
may need additional manual testing
is useful, but should not be first
Tier 3 / Later Criteria
A candidate belongs in Tier 3 or Later if it:
is likely useful long-term
depends on multiple earlier systems
requires technical architecture decisions
may involve queues, dashboards, employees, routing, or automation
would be premature before field logic and workflow rules are stable
Do Not Build Yet Criteria
A candidate belongs in Do Not Build Yet if it would require:
plugin/UI work
Supabase work
Brain Room routing
automation
queues
dashboards
generators
AI Employees
cross-brain task wiring
M handoff
technical specification
implementation design
This shortlist does not authorize those items.
Should Stay Manual Criteria
A workflow should stay manual for now if it requires:
human judgment
HeadOffice authority
claim-risk interpretation
source-confidence assessment
offer-evidence review
VSL claim review
publishing approval
compliance-sensitive decision-making
M handoff approval
These areas are too judgment-sensitive for early automation or UI build.
Tier 1 Build Candidates
These are the strongest future build candidates based on Manual Workflow Tests 1–10 and the Manual Workflow Synthesis Report.
These are not approved for build yet.
They are only shortlisted as strongest future candidates.
1. Content Brain Site Content Intelligence Report Generator Specification
Status:
Tier 1 Build Candidate
Strength:
Very Strong
Reason:
Site Content Intelligence appeared as the strongest upstream workflow.
It helps Content Brain understand the site before creating, refreshing, linking, repurposing, or approving content.
It prevents blind content creation.
It supports many downstream workflows.
Evidence Pattern:
The Site Content Intelligence workflow helped identify:
existing site content
site purpose
site tone
content gaps
refresh opportunities
internal linking opportunities
trust gaps
proof gaps
claim-risk areas
next recommended content assets
site-specific content direction
Why It Matters:
Content Brain works best when it begins with site context.
Without site intelligence, Content Brain risks creating generic content, duplicated content, weak internal linking, tone mismatch, unsupported claims, or disconnected affiliate support assets.
Downstream Workflows Supported:
Content Briefs
SEO Content Briefs
Affiliate Product Content Packs
Content Refresh
Internal Linking
Publishing Readiness
Compliance routing
Ads Brain handoff
Affiliate Brain handoff
Bridge page review
Landing page refresh
Topic cluster planning
Repurposing planning
Future Specification Potential:
Very high
Current Verdict:
Strongest first future specification candidate.
Do not build yet.
2. Publishing Readiness Checklist UI
Status:
Tier 1 Build Candidate
Strength:
Strong
Reason:
Publishing readiness appeared across nearly all workflows.
Every Content Brain workflow eventually needs a final status decision before content is drafted, published, handed off, refreshed, repurposed, or used in a campaign.
Evidence Pattern:
Manual workflows repeatedly needed decisions such as:
ready for drafting
ready for briefing
not ready for publishing
needs compliance review
needs stronger evidence
needs claim softening
needs source review
approved for next workflow
hold for HeadOffice
Why It Matters:
Content Brain cannot safely operate as a publishing-support system without a clear readiness checkpoint.
This is especially important for affiliate content, bridge pages, campaign pages, wellness content, water security content, and any claim-sensitive content.
Downstream Workflows Supported:
Content Briefs
SEO Content Briefs
Affiliate Content Packs
Refresh
Repurposing
Bridge page review
Landing page optimization
Compliance routing
HeadOffice approval
M handoff discipline
Future Specification Potential:
High
Current Verdict:
Strong future utility.
Should wait until status values are cleaned and standardised.
Do not build yet.
3. Affiliate Product Content Pack Generator
Status:
Tier 1 Build Candidate
Strength:
Strong
Reason:
Affiliate product content pack planning worked across more than one niche and proved that Content Brain can support affiliate offers as content ecosystems, not isolated pages.
Evidence Pattern:
Manual tests showed that Content Brain can plan affiliate support content around:
product education
buyer awareness
reader problems
buyer questions
comparison content
FAQ content
trust content
objection handling
VSL preparation
internal linking
claim safety
publishing readiness
Why It Matters:
MWMS affiliate campaigns need structured supporting content.
A single landing page or article is not enough.
Affiliate campaigns need content packs that help readers understand the problem, solution, offer, evidence, objections, and next step.
Downstream Workflows Supported:
Affiliate Brain
Ads Brain
Conversion Brain
Compliance Brain
Content Briefs
SEO Content Briefs
Bridge page planning
VSL support content
Internal Linking
Publishing Readiness
Future Specification Potential:
High
Current Verdict:
Strong build candidate.
Should likely follow Site Content Intelligence because it depends on site and offer context.
Do not build yet.
Tier 2 Build Candidates
These candidates are strong, but should wait until Tier 1 logic is clearer or additional manual evidence is gathered.
1. Internal Linking Planner
Status:
Tier 2 Build Candidate
Strength:
Medium to Strong
Reason:
Internal linking proved important, but it needs more testing across different niches and site types before becoming build-ready.
Evidence Pattern:
Manual workflow testing showed that Content Brain can plan:
hub pages
spoke pages
reader journey links
product support links
FAQ links
trust links
proof links
education links
links to avoid
claim-sensitive linking
Why It Matters:
Content Brain should create connected content systems, not isolated pages.
Internal linking is not only SEO.
It also supports trust, buyer education, conversion timing, proof control, and safe reader progression.
Future Specification Potential:
Medium to high
Current Verdict:
Promising.
Needs more manual testing and clearer link-status logic before specification.
Do not build yet.
2. Topic Cluster Planner
Status:
Tier 2 Build Candidate
Strength:
Medium to Strong
Reason:
Topic clustering appeared as an important support layer for SEO, authority, internal linking, affiliate content, and reader journey planning.
Evidence Pattern:
Manual workflow testing showed that Content Brain can identify:
hub topics
spoke topics
supporting article opportunities
buyer education paths
authority-building topics
product support clusters
trust-building clusters
content gaps
Why It Matters:
Topic clusters help Content Brain build authority rather than random standalone content.
They also support Search Intelligence Brain, Research Brain, Affiliate Brain, and Ads Brain by organising content around useful journeys.
Future Specification Potential:
Medium to high
Current Verdict:
Useful future planner.
Should not be first because it depends on stronger site intelligence and internal linking logic.
Do not build yet.
3. Content Refresh Queue / Optimization Workflow
Status:
Tier 2 Build Candidate
Strength:
Medium to Strong
Reason:
Refresh and optimization testing proved that Content Brain can improve existing or proposed assets, but the workflow needs clearer sub-type definitions.
Evidence Pattern:
Manual tests showed Content Brain can identify:
clarity gaps
trust gaps
claim-risk issues
internal linking gaps
buyer education gaps
content improvement opportunities
publishing readiness issues
bridge page improvement opportunities
Why It Matters:
Content Brain must improve existing assets, not only create new ones.
MWMS will eventually need a reliable way to find, classify, improve, and re-approve older content.
Future Specification Potential:
Medium to high
Current Verdict:
Strong future candidate.
Should wait until Site Content Intelligence and Publishing Readiness logic are clearer.
Do not build yet.
4. Affiliate Bridge Page Refresh Template
Status:
Tier 2 Build Candidate
Strength:
Medium to Strong
Reason:
Bridge page review appeared as a major MWMS need, especially because affiliate traffic depends heavily on ad-to-page match, VSL transition, claim safety, and curiosity control.
Evidence Pattern:
Manual tests showed that affiliate bridge pages need checks for:
ad-to-page match
hook accuracy
headline clarity
VSL transition
claim safety
curiosity balance
CTA pressure
urgency language
reader expectation setting
publishing readiness
Why It Matters:
Affiliate bridge pages are not normal blog posts.
They sit between the ad, the content promise, the VSL, the offer, and the conversion event.
Poor bridge page logic can hurt compliance, conversion, trust, and campaign performance.
Future Specification Potential:
Medium to high
Current Verdict:
Important for MWMS.
Needs at least one more bridge page test before becoming build-ready.
Do not build yet.
Tier 3 / Later Candidates
These candidates may become useful later, but they should not be prioritised now.
They depend on earlier workflow structure, technical architecture, or multiple proven specifications.
1. Content Operations Dashboard
Status:
Tier 3 / Later Candidate
Reason:
A dashboard may eventually help Content Brain view active content work, statuses, bottlenecks, publishing readiness, refresh needs, and handoff points.
Why It Should Wait:
A dashboard depends on stable status values, stable workflows, stable data fields, and clear operator needs.
Current Verdict:
Later candidate only.
Do not build yet.
2. Content Production Queue
Status:
Tier 3 / Later Candidate
Reason:
A production queue may eventually track content requests from intake through brief, draft, review, approval, handoff, refresh, or repurposing.
Why It Should Wait:
Queue logic depends on stable workflow classification, status values, role ownership, and handoff rules.
Current Verdict:
Later candidate only.
Do not build yet.
3. Content Repurposing Queue
Status:
Tier 3 / Later Candidate
Reason:
A repurposing queue may eventually track approved assets that can be safely reused across formats.
Why It Should Wait:
Repurposing requires stable approval rules, claim preservation rules, audience-stage rules, and publishing readiness logic.
Current Verdict:
Later candidate only.
Do not build yet.
4. Content Brain AI Employee Router
Status:
Tier 3 / Later Candidate
Reason:
A future router may eventually help route content tasks to specialised Content Brain AI Employees.
Why It Should Wait:
No AI Employees should be built or routed until manual workflows, specifications, fields, statuses, and authority rules are much clearer.
Current Verdict:
Later candidate only.
Do not build yet.
5. Cross-Brain Handoff Router
Status:
Tier 3 / Later Candidate
Reason:
A cross-brain handoff router may eventually pass structured requests between Content Brain and other Brains such as Affiliate Brain, Ads Brain, Compliance Brain, Research Brain, Search Intelligence Brain, Data Brain, and HeadOffice.
Why It Should Wait:
Cross-brain routing requires stronger technical architecture, handoff schemas, authority rules, task types, and M build planning.
Current Verdict:
Later candidate only.
Do not build yet.
Do Not Build Yet
The following must not be built from this shortlist.
Do not build:
plugin/UI
Supabase
Brain Room routing
automation
dashboards
queues
generators
AI Employees
cross-brain routing
task wiring
status automation
content dashboards
content generators
publishing approval automation
compliance automation
M handoff packages
technical implementation plans
Reason:
Content Brain is still in Manual Workflow Evidence Stage.
The workflows are proven enough to shortlist future candidates.
They are not yet proven enough to wire into technical systems.
This page is a planning report only.
Should Stay Manual For Now
The following should stay manual for now:
compliance-sensitive claim judgment
publishing approval
offer evidence review
source depth confidence
VSL claim review
bridge page final approval
M handoff approval
cross-brain authority decisions
build candidate prioritisation
manual workflow synthesis
final go / hold / revise decisions
Reason:
These require judgment, context, and HeadOffice authority.
They are too sensitive to automate or turn into rigid UI logic too early.
Content Brain should not hand these decisions to a generator, dashboard, queue, or AI Employee yet.
Strongest First Future Specification Candidate
The strongest first future specification candidate is:
Content Brain Site Content Intelligence Report Generator Specification
This is the recommended first future specification candidate.
It should not be created until this shortlist is safely recorded and the Page Registry is updated.
Why This Candidate Is Strongest
The Site Content Intelligence Report Generator is strongest because it is upstream of the largest number of Content Brain workflows.
It supports:
Content Briefs
SEO Content Briefs
Affiliate Content Packs
Refresh
Internal Linking
Publishing Readiness
Compliance routing
Ads Brain handoff
Affiliate Brain handoff
Bridge page review
Landing page refresh
Topic cluster planning
Repurposing planning
Offer support content
Site tone extraction
Content gap detection
Trust gap detection
Proof gap detection
Reader journey planning
The core finding from Manual Workflow Tests 1–10 is that Content Brain works best when it understands site context before creating or improving content.
This makes Site Content Intelligence the best first future specification candidate.
Recommended Next Step
Recommended next step:
Update Content Brain Page Registry from v2.2 to v2.3.
Add this new page:
Content Brain Build-Readiness Shortlist
Status:
Active Build-Readiness Planning Report
Version:
v1.0
Parent:
Content Brain
Recommended registry placement:
Build-Readiness Planning Pages
Reason:
This page is not only a test log.
This page is not only an evidence report.
This page is a planning bridge between manual workflow synthesis and future specification work.
It deserves its own registry section.
Recommended new registry section:
Build-Readiness Planning Pages
Page Count Impact:
Before this page:
40 pages
After this page:
41 pages
Do not update Content Brain Canon unless governing identity or authority boundaries change.
Do not update Content Brain Architecture unless live structure or architectural design materially changes.
Do not update Content Brain Manual Workflow Test Log unless new test evidence is added.
Do not update Content Brain Manual Workflow Synthesis Report unless the interpretation of Tests 1–10 materially changes.
Build Not Authorised Notice
This page does not authorize build work.
No plugin/UI work is authorized.
No Supabase work is authorized.
No Brain Room routing work is authorized.
No automation work is authorized.
No dashboard work is authorized.
No queue work is authorized.
No generator work is authorized.
No AI Employee work is authorized.
No cross-brain routing work is authorized.
No M implementation handoff is authorized.
This page only identifies future build candidates and recommends the strongest first future specification candidate.
The next allowed action is registry update only.
Change Impact Declaration
Pages Created:
Content Brain Build-Readiness Shortlist
Pages Updated:
Content Brain Page Registry should be updated from v2.2 to v2.3 after this page is created.
Pages Renamed:
None
Pages Deleted:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Canon Version Update Required:
No
Architecture Version Update Required:
No
Manual Workflow Test Log Update Required:
No
Manual Workflow Synthesis Report Update Required:
No
Plugin/UI Impact:
None
Supabase Impact:
None
Brain Room Routing Impact:
None
Automation Impact:
None
M Active Build Impact:
None
Page Count Impact:
Previous page count:
40 pages
New page count:
41 pages
Change Log
Version: v1.0
Date: 2026-06-05
Author: HeadOffice
Change:
Created Content Brain Build-Readiness Shortlist after completion of Manual Workflow Tests 1–10, creation of the Manual Workflow Synthesis Report, and update of the Content Brain Page Registry to v2.2.
This page converts manual workflow evidence into a clean shortlist of possible future build candidates.
Identified Tier 1 build candidates:
Content Brain Site Content Intelligence Report Generator Specification
Publishing Readiness Checklist UI
Affiliate Product Content Pack Generator
Identified Tier 2 build candidates:
Internal Linking Planner
Topic Cluster Planner
Content Refresh Queue / Optimization Workflow
Affiliate Bridge Page Refresh Template
Identified Tier 3 / Later candidates:
Content Operations Dashboard
Content Production Queue
Content Repurposing Queue
Content Brain AI Employee Router
Cross-Brain Handoff Router
Confirmed that plugin/UI, Supabase, Brain Room routing, automation, dashboards, queues, generators, AI Employees, and cross-brain routing must not be built yet.
Confirmed that compliance-sensitive claim judgment, publishing approval, offer evidence review, source depth confidence, VSL claim review, bridge page final approval, and M handoff approval should stay manual for now.
Confirmed strongest first future specification candidate:
Content Brain Site Content Intelligence Report Generator Specification
Confirmed that the next action is registry update only.
End Of Day Save Point Template
Page list checked:
Yes / No
Manual Workflow Test Log checked:
Yes / No
Manual Workflow Synthesis Report checked:
Yes / No
Page Registry checked:
Yes / No
Build-Readiness Shortlist created:
Yes / No
Page Registry updated to v2.3:
Yes / No
Pages created:
Content Brain Build-Readiness Shortlist
Pages updated:
Content Brain Page Registry
Pages renamed:
None
Pages deleted:
None
Current page count:
41 pages
No plugin/UI started:
Yes / No
No Supabase work started:
Yes / No
No Brain Room routing started:
Yes / No
No automation started:
Yes / No
M’s active work untouched:
Yes / No
Target save point:
Content Brain — Build-Readiness Shortlist Created / First Future Specification Candidate Identified / Manual Workflow Evidence Stage / Manual Workflow Only / Plugin UI Not Started
Final Rule
This page is a shortlist.
It is not a build specification.
It is not a technical implementation instruction.
It is not an M handoff pack.
It is not a plugin/UI approval.
It is not a Supabase approval.
It is not an automation approval.
It is not a Brain Room routing approval.
The only next authorised action is to update Content Brain Page Registry to v2.3 and record the new page count.
END CONTENT BRAIN BUILD-READINESS SHORTLIST v1.0