Brain Name: Content Brain
Document Type: Operational Log
Status: Active Operational Log
Version: v2.0
Authority: HeadOffice
Applies To: Content Brain, manual workflow testing, operational layer validation, site intelligence testing, affiliate product content pack testing, refresh workflow testing, content optimization testing, internal linking testing, topic cluster testing, affiliate bridge page testing, affiliate landing page refresh testing, content briefing tests, SEO briefing tests, publishing readiness tests, future build-readiness evidence, future Content Brain system wiring, and future M handoff specifications
Parent: Content Brain
Last Reviewed: 2026-06-04
Purpose
The Content Brain Manual Workflow Test Log records practical tests performed through the live Content Brain operational layer.
Its purpose is to prove whether Content Brain workflows work manually before any plugin, UI, queue, dashboard, generator, automation, Supabase route, Brain Room routing, or AI Employee is built.
This log captures:
what was tested
which Content Brain pages were used
whether the workflow passed
what friction appeared
what future build candidates were revealed
what should remain manual
what should not be built yet
what evidence may later support M’s build work
Content Brain must prove workflows through real use before systemising them.
Current Status Notice
Content Brain has now completed its first ten manual workflow tests.
The tested operational areas include:
affiliate and conversion support briefing
SEO educational content briefing
site content intelligence review
real external affiliate/business site content intelligence review
affiliate product content pack planning
refresh and content optimization review
internal linking and topic cluster planning
second real external site intelligence review
second-niche affiliate product content pack planning
affiliate landing page / bridge page refresh review
The first operational layer is no longer only theoretical.
It has now been tested across ten practical manual workflow tests.
This does not mean the system is ready for plugin/UI build.
It means the manual workflow is usable, evidence is growing, and future build candidates are becoming clearer.
The current save point is:
Content Brain — Manual Workflow Tests 1–10 Completed / Affiliate Site Intelligence, Product Pack, Refresh, Bridge Page, And Internal Linking Evidence Captured / Manual Workflow Only / Plugin UI Not Started
Core Principle
Manual workflow comes before system build.
A workflow should not become a queue, dashboard, generator, AI Employee, or automated process until it has been used manually enough times to prove:
the input is clear
the output is clear
the status path is clear
the approval owner is clear
the handoff destination is clear
the risk rules are clear
the operator value is clear
the repeated pattern is real
Manual testing protects MWMS from building the wrong system too early.
Relationship To Content Brain Operational Layer
Manual workflow tests may use:
Content Brain Workflow
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 Repurposing
Content Brain Refresh
Content Brain Site Content Intelligence Framework
Content Brain Cross-Brain Integration Map
Content Brain Page Registry
Content Brain Architecture
Content Brain Canon
Each test should record which pages were used and whether they worked as intended.
Relationship To Build-Readiness
This log is an evidence layer.
It may later support:
Content Opportunity Queue
Content Production Queue
Content Refresh Queue
Content Repurposing Queue
Content Operations Dashboard
Content Brief Generator
SEO Brief Generator
Affiliate Content Pack Generator
Affiliate Funnel Support Planner
Internal Linking Planner
Publishing Readiness Checklist UI
Site Content Intelligence Report Generator
Content Signal Feedback Dashboard
Cross-Brain Handoff Router
Content Brain AI Employee Router
This log does not authorize those builds.
It records evidence that may later justify them.
Test Record Format
Each test should include:
Test Number:
Test Name:
Date:
Status:
Test Type:
Request:
Pages Used:
Source:
Source Brain:
Supporting Brains:
Output Created:
Approval Owner:
Risk Level:
Result:
Workflow Verdict:
Friction Found:
Future Build Evidence:
Recommended Next Action:
Save Point:
Test Status Labels
Use these status labels:
Passed
Passed With Friction
Needs Retest
Failed
Parked
Do not treat a test as passed if the workflow only worked because the operator manually rescued unclear logic.
If friction appears, record it clearly.
Manual Workflow Test 1
Test Number: 1
Test Name: How Content Brain Helps Affiliate Offers Convert Better Without Hype
Date: 2026-06-03
Status: Passed
Test Type: Affiliate / Conversion Support Workflow
Request
Create a content brief for an article explaining how Content Brain helps affiliate offers convert better without hype.
Pages Used
Content Brain Workflow
Content Brain Content Briefs
Content Brain Publishing Readiness
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
Data Brain
HeadOffice Brain
Output Created
Educational article brief / internal authority guide.
Approval Owner
HeadOffice
Risk Level
Low to Medium
Result
The request was successfully classified, briefed, risk-checked, and moved to:
Brief Approved For Drafting
The workflow showed that Content Brain can guide an affiliate/conversion-support content request from idea to structured brief without needing plugin/UI, Supabase, queues, dashboards, generators, or automation.
Workflow Verdict
Passed.
The workflow successfully handled:
request classification
purpose definition
audience definition
intent mapping
content type selection
article structure
claims to avoid
approval owner
handoff destination
publishing readiness status
Friction Found
Content Brain Workflow may contain an older naming reference to Content Workflow instead of Content Brain Workflow.
Content Brain Content Briefs may later need a cleaner copy-ready Brief Output Template.
Content Brain Publishing Readiness may later need clearer status values for future system build.
Future Build Evidence
Potential future status values appeared useful:
Parked
Briefing
Ready For Drafting
Draft In Review
Ready For Handoff
Ready For Publishing
Hold For Compliance
Hold For Affiliate Brain
Hold For Research Brain
This evidence may later support a Content Brain status framework or workflow status field.
Recommended Next Action
Run another test using SEO-focused content to confirm the operational layer works outside affiliate/conversion support.
Save Point
Content Brain — Manual Workflow Test 1 Passed / Affiliate Conversion Support Workflow Usable / Plugin UI Not Started
Manual Workflow Test 2
Test Number: 2
Test Name: What Is A Content Brain And How Does It Help Online Businesses?
Date: 2026-06-03
Status: Passed
Test Type: SEO / Educational Content Workflow
Request
Create an SEO content brief for an article:
What Is A Content Brain And How Does It Help Online Businesses?
Pages Used
Content Brain Workflow
Content Brain SEO Content Briefs
Content Brain Publishing Readiness
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Research Brain
Search Intelligence Brain
Strategy Brain
Conversion Brain
Data Brain
HeadOffice Brain
Output Created
SEO-focused educational content brief.
Approval Owner
HeadOffice
Risk Level
Low
Result
The request was successfully classified as an SEO content brief and developed into a structured educational SEO brief.
The brief included:
search intent
audience
reader problem
content goal
article structure
keywords and topic phrases
information gain angle
trust notes
claims to avoid
internal links
CTA
approval owner
signal to watch
The brief was marked:
Ready For Drafting
Workflow Verdict
Passed.
The workflow successfully handled SEO and educational content planning.
This proves the operational layer can support more than affiliate/conversion content.
Friction Found
SEO Content Briefs may later need a clearer reusable template because SEO briefs can become long.
If Content Brain becomes public-facing, a public-positioning rule may be needed:
Use “Content Brain” as MWMS terminology unless the market uses the term more broadly.
Future status values remained useful:
Parked
Briefing
Ready For Drafting
Draft In Review
Ready For Publishing
Hold For Research Brain
Hold For Search Intelligence Brain
Hold For Compliance Brain
Refresh Later
Repurpose Later
Future Build Evidence
This test supports future build candidates such as:
SEO Brief Generator
Content Brief Generator
Publishing Readiness Checklist UI
Content Production Queue
Content Operations Dashboard
The evidence is not enough to build yet.
More repeated tests are needed.
Recommended Next Action
Test site-specific content intelligence to check whether Content Brain can review an existing site before creating content.
Save Point
Content Brain — Manual Workflow Test 2 Passed / SEO Educational Brief Workflow Usable / Plugin UI Not Started
Manual Workflow Test 3
Test Number: 3
Test Name: mwmscontentbrain.site Site Content Intelligence Review
Date: 2026-06-03
Status: Passed
Test Type: Site Content Intelligence Workflow
Request
Review mwmscontentbrain.site and identify what content already exists, what the site tone feels like, what gaps remain, and what content should be created, refreshed, linked, or left alone next.
Pages Used
Content Brain Workflow
Content Brain Site Content Intelligence Framework
Content Brain Page Registry
Content Brain Architecture
Content Brain Cross-Brain Integration Map
Content Brain Internal Linking
Content Brain Refresh
Content Brain Repurposing
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Research Brain
Search Intelligence Brain
Affiliate Brain
Compliance Brain
Data Brain
HeadOffice Brain
SIT Brain
Output Created
Site Content Intelligence Report for mwmscontentbrain.site.
Approval Owner
HeadOffice
Risk Level
Low
Result
The Site Content Intelligence Framework successfully reviewed the current Content Brain site structure.
The test identified:
existing site structure
site purpose
site voice and tone
topic coverage
content gaps
refresh opportunities
internal linking opportunities
duplicate and overlap risks
thin content warning
future build candidates
next recommended action
The test confirmed the value of the Site Content Intelligence Framework.
Workflow Verdict
Passed.
The workflow successfully showed that Content Brain should check existing site content before creating new content when site context matters.
Friction Found
The uploaded page source used for the test was one step behind the latest registry state, but existing conversation context confirmed the newer Site Content Intelligence Framework and Page Registry v1.5.
For future tests, use the latest raw WordPress page list or latest Page Registry before running site intelligence.
The new Site Content Intelligence Framework may later need a dedicated report template if repeated tests prove the need.
Future Build Evidence
This test supports the future candidate:
Site Content Intelligence Employee
It also supports possible future tools:
Site Content Intelligence Report Generator
Site Content Inventory Tool
Site Voice And Tone Extractor
Content Gap Finder
Internal Linking Opportunity Finder
Refresh Opportunity Finder
Repurposing Opportunity Finder
Content Brief Generator input layer
However, no build should start yet.
More manual tests are needed.
Recommended Next Action
If continuing testing, run a site-intelligence workflow on a real affiliate or business website.
If stabilising the system, update the Page Registry and record this test log.
Save Point
Content Brain — Site Content Intelligence Tested / Manual Workflow Test 3 Passed / Site-Aware Content Direction Confirmed / Plugin UI Not Started
Manual Workflow Test 4
Test Number: 4
Test Name: Endorfix / Elevate Energi Real Site Content Intelligence Review
Date: 2026-06-04
Status: Passed With Friction
Test Type: Real External Site Content Intelligence Workflow
Request
Review a real MWMS-related affiliate or business site and identify what content already exists, what the site tone feels like, what content gaps remain, what should be refreshed, what should be internally linked, and what content should be created next.
Pages Used
Content Brain Workflow
Content Brain Site Content Intelligence Framework
Content Brain SEO Content Brief Standard
Content Brain Internal Linking Strategy Framework
Content Brain Publishing Readiness Checklist
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
HeadOffice Brain
Output Created
Site Content Intelligence Review for Endorfix / Elevate Energi direction.
Approval Owner
HeadOffice
Risk Level
Medium
Result
The Site Content Intelligence Framework successfully worked on a real external affiliate/business-style site.
The test identified that the site already has:
product/category content
product descriptions
FAQ/support content
shipping and returns information
ingredient-related explanations
customer review and proof signals
bold direct-response product positioning
ecommerce navigation
buyer reassurance content
The review identified that the site tone is:
bold
direct-response focused
wellness-tech positioned
slightly rebellious
product-led
benefit-driven
risk-sensitive because of energy, appetite, sleep, ingredient, and performance-related wording
The test found that the biggest content gaps are not basic product pages.
The bigger gaps are:
education content
trust-building content
comparison content
beginner guidance
usage support
troubleshooting content
safer proof handling
internal linking structure
compliance-safe ingredient education
The test recommended the next best content asset:
How Energy Patches Work: A Simple Beginner Guide
This was selected because it can support:
homepage trust
product page belief
buyer education
internal linking
Google Ads landing-page support
objection handling
safer product explanation
The test also identified secondary content opportunities:
Energy Patches vs Energy Drinks
Caffeine Patch vs Coffee
Where To Place An Energy Patch For Best Results
How Long Do Energy Patches Last?
Why You Might Not Feel An Energy Patch Straight Away
ingredient education pages
Australian customer information page
review/proof page
Workflow Verdict
Passed With Friction.
The workflow successfully handled a real external site intelligence review and produced practical content direction.
It proved that Content Brain can review an existing business or affiliate site before creating new content.
This is important because it prevents Content Brain from blindly creating content without understanding:
what already exists
what the site is trying to sell
what the tone feels like
where trust is weak
where internal links are missing
where claims may need softening
what content should be created next
Friction Found
The process worked, but the output would be easier to repeat if Content Brain later had a standard Site Intelligence Report Template.
The template may need fields for:
site reviewed
business model
existing content inventory
tone profile
offer/message match
content gaps
refresh opportunities
internal linking opportunities
proof/trust gaps
compliance-sensitive claims
recommended next content asset
recommended Content Brain workflow path
build-readiness evidence
External site reviews also need clearer evidence notes because real websites can include live pages, customer proof, product pages, claims, blog posts, FAQs, and support information.
Compliance Brain should be involved early for wellness, health, finance, income, legal, appetite, sleep, energy, medical, supplement, or performance-related content.
Future Build Evidence
This test strengthens the case for future candidates such as:
Site Content Intelligence Report Generator
Site Content Inventory Tool
Site Tone Extractor
Content Gap Finder
Refresh Opportunity Finder
Internal Linking Opportunity Finder
Compliance-Sensitive Claim Detector
Next Content Recommendation Engine
Site Intelligence To Content Brief workflow
Site Intelligence To Refresh Queue workflow
Site Intelligence To Internal Linking Planner workflow
However, this test does not authorize build work yet.
The workflow has passed one internal site test and one real external site test.
More repeated tests are needed before creating plugin/UI specifications.
Recommended Next Action
Do not start plugin/UI build.
Do not start Supabase work.
Do not start Brain Room routing.
Do not create queues, dashboards, generators, or automations yet.
Recommended next manual test:
Manual Workflow Test 5 — Affiliate Product Content Pack Test
Suggested path:
Content Brain Workflow
Content Brain Affiliate Product Content Pack Checklist
Content Brain Affiliate Funnel Support Map
Content Brain Publishing Readiness Checklist
Purpose:
Check whether Content Brain can manually generate a practical affiliate product content pack for one offer before any technical build is considered.
Save Point
Content Brain — Site Intelligence Tested On Real Site / Manual Workflow Test 4 Passed With Friction / Manual Workflow Evidence Growing / Manual Workflow Only / Plugin UI Not Started
Manual Workflow Test 5
Test Number: 5
Test Name: Endorfix Energy Patch Affiliate Product Content Pack
Date: 2026-06-04
Status: Passed
Test Type: Affiliate Product Content Pack Workflow
Request
Create an affiliate product content pack for Endorfix / Elevate Energi Energy Patches.
The pack should support product education, buyer trust, pre-sell content, internal linking, objection handling, and safe content direction.
The goal is not to create hype copy.
The goal is to create a practical affiliate/business content pack that can support traffic, landing pages, blog content, YouTube descriptions, email follow-up, and buyer reassurance.
Pages Used
Content Brain Workflow
Content Brain Affiliate Product Content Pack Checklist
Content Brain Affiliate Funnel Support Map
Content Brain Publishing Readiness Checklist
Content Brain Site Content Intelligence Framework
Content Brain Internal Linking Strategy Framework
Content Brain E E A T Content Trust Framework
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
HeadOffice Brain
Output Created
Affiliate Product Content Pack for Endorfix / Elevate Energi Energy Patches.
Approval Owner
HeadOffice
Risk Level
Medium
Reason:
The product category includes wellness, energy, appetite, sleep, ingredient, caffeine, performance, and daily-function wording.
This means content must avoid exaggerated claims, guaranteed outcomes, medical-style positioning, unsupported proof, and unsafe health implications.
Result
The Affiliate Product Content Pack workflow successfully turned the previous site intelligence findings into a practical affiliate/business content pack.
The test produced a structured content pack covering:
product education
buyer awareness stages
audience fit
reader problems
buyer questions
core content angle
tone direction
claims to avoid
recommended content assets
internal linking plan
compliance notes
publishing readiness status
recommended first content brief
The content pack selected the primary first asset:
How Energy Patches Work: A Simple Beginner Guide
This asset was selected because it can support:
homepage trust
product page belief
buyer education
internal linking
Google Ads landing-page support
objection handling
safer product explanation
The content pack also identified supporting assets:
Energy Patches vs Energy Drinks: What Is The Difference?
Caffeine Patch vs Coffee: Which Fits Your Day Better?
Where To Place An Energy Patch For Best Results
Why You Might Not Feel An Energy Patch Straight Away
Energy Patch FAQ
Ingredient Education Hub
Customer Review And Proof Page
The workflow also identified that the pack should not move directly to publishing.
It should move to:
Content Pack Approved For Briefing
The next working step should be to create a full content brief for the beginner guide.
Workflow Verdict
Passed.
Content Brain successfully turned site intelligence into a practical affiliate product content pack.
The workflow connected:
site intelligence
affiliate product support
buyer education
pre-sell content
internal linking
objection handling
compliance awareness
future publishing readiness
This confirms that Content Brain can move from site review to affiliate product content planning without needing plugin/UI, Supabase, queues, dashboards, generators, or automation.
Friction Found
The Affiliate Product Content Pack workflow works manually, but it may later need a cleaner repeatable template.
The content pack should include fixed fields for:
product / offer
audience
awareness stage
content pack purpose
core content angles
buyer questions
asset list
internal linking plan
claims to avoid
publishing readiness status
recommended first brief
Compliance handling should be visible earlier when the product involves wellness, energy, appetite, sleep, supplement, health, income, finance, legal, or performance-related claims.
Future Build Evidence
This test supports future candidates such as:
Affiliate Product Content Pack Generator
Affiliate Funnel Support Planner
Content Pack Template
Internal Linking Planner
Publishing Readiness Checklist UI
Compliance-Sensitive Claims Review Step
Site Intelligence To Affiliate Content Pack Workflow
Affiliate Product Content Pack Status Field
However, no build should start yet.
More repeated manual product-pack tests are needed before creating build specifications.
Recommended Next Action
Run Manual Workflow Test 6 using a Refresh request.
Suggested path:
Content Brain Workflow
Content Brain Refresh
Content Brain Content Optimization Framework
Content Brain Publishing Readiness Checklist
Purpose:
Check whether Content Brain can improve an existing content asset instead of only creating new content plans.
Think-ahead impact after this test:
Content Brain Manual Workflow Test Log has moved from v1.1 to v1.2.
Content Brain Page Registry should move from v1.7 to v1.8.
Page count stays 39.
No new page created.
No Canon update required.
No Architecture update required.
No plugin/UI work.
No Supabase work.
No Brain Room routing.
No M build work touched.
Save Point
Content Brain — Affiliate Product Content Pack Tested / Manual Workflow Test 5 Passed / Manual Workflow Evidence Growing / Manual Workflow Only / Plugin UI Not Started
Manual Workflow Test 6
Test Number: 6
Test Name: Endorfix Energy Patch Beginner Guide Refresh Test
Date: 2026-06-04
Status: Passed
Test Type: Refresh / Content Optimization Workflow
Request
Review the proposed content asset:
How Energy Patches Work: A Simple Beginner Guide
Identify how Content Brain would refresh or improve the content before it becomes a full article or publishing-ready page.
The refresh should improve clarity, trust, buyer education, internal linking, compliance safety, and publishing readiness.
The goal is to test whether Content Brain can take an existing or proposed content asset and improve it before publishing.
Pages Used
Content Brain Workflow
Content Brain Refresh
Content Brain Content Optimization Framework
Content Brain Publishing Readiness Checklist
Content Brain Site Content Intelligence Framework
Content Brain E E A T Content Trust Framework
Content Brain Internal Linking Strategy Framework
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
HeadOffice Brain
Output Created
Refresh and optimization review for the proposed content asset:
How Energy Patches Work: A Simple Beginner Guide
Approval Owner
HeadOffice
Risk Level
Medium
Reason:
The content asset involves energy, caffeine, wellness, daily performance, user expectations, product explanation, ingredient-adjacent education, and possible claims around effects.
This means the content must avoid medical-style claims, guaranteed outcomes, exaggerated performance promises, unsupported proof, and overly aggressive comparison language.
Result
The Refresh / Content Optimization workflow successfully reviewed the proposed beginner guide and identified how it should be improved before drafting or publishing.
The test found that the proposed beginner guide is a strong first content asset because it supports buyer education before promotion.
However, before drafting or publishing, the asset needs stronger structure, safer claims, clearer reader expectation setting, and better internal linking.
The content should not be written as a hard-sell sales page.
It should work as a buyer education page that explains the idea of energy patches, how people use them, what realistic expectations look like, and where the reader can go next.
The test identified improvement areas across:
clarity
trust
buyer education
internal linking
compliance safety
publishing readiness
The test recommended that the asset should move to:
Approved For Full Brief
The recommended brief type is:
SEO / Buyer Education Content Brief
The recommended compliance status is:
Compliance review required before publishing
Workflow Verdict
Passed.
Content Brain successfully reviewed a proposed content asset and identified how it should be improved before drafting or publishing.
The workflow handled:
refresh logic
content optimization
reader clarity
trust improvement
buyer education
internal linking
claims softening
compliance awareness
publishing readiness
This confirms that Content Brain can improve existing or proposed content assets, not only create new content plans.
Friction Found
The refresh workflow works manually, but it may later need a cleaner repeatable refresh template.
The future refresh template should include fixed fields for:
asset being reviewed
current status
content purpose
reader intent
what needs improving
what should be added
what should be removed
claims to soften
internal links to add
trust gaps
compliance risk
publishing readiness status
recommended next action
The workflow also needs a clear distinction between:
refreshing an existing live page
optimizing a proposed asset before drafting
improving a draft before publishing
These are related but not identical workflows.
Future Build Evidence
This test supports future candidates such as:
Content Refresh Queue
Content Optimization Workflow
Refresh Template
Publishing Readiness Checklist UI
Compliance-Sensitive Claims Review Step
Internal Linking Planner
Content Improvement Recommendation Engine
Refresh Status Field
Draft Improvement Workflow
However, no build should start yet.
More repeated manual refresh tests are needed before creating build specifications.
Recommended Next Action
Run Manual Workflow Test 7 using an Internal Linking request.
Suggested path:
Content Brain Workflow
Content Brain Internal Linking
Content Brain Topic Cluster And Hub Architecture Framework
Content Brain Publishing Readiness Checklist
Purpose:
Check whether Content Brain can connect related content assets into a clear reader journey, internal linking structure, and topic cluster support path.
Think-ahead impact after this test:
Content Brain Manual Workflow Test Log has moved from v1.2 to v1.3.
Content Brain Page Registry should move from v1.8 to v1.9.
Page count stays 39.
No new page created.
No Canon update required.
No Architecture update required.
No plugin/UI work.
No Supabase work.
No Brain Room routing.
No M build work touched.
Save Point
Content Brain — Refresh Workflow Tested / Manual Workflow Test 6 Passed / Proposed Content Asset Improved Before Drafting / Manual Workflow Evidence Growing / Manual Workflow Only / Plugin UI Not Started
Manual Workflow Test 7
Test Number: 7
Test Name: Endorfix Energy Patch Internal Linking And Topic Cluster Test
Date: 2026-06-04
Status: Passed
Test Type: Internal Linking / Topic Cluster Workflow
Request
Create an internal linking and topic cluster plan for the Endorfix / Elevate Energi Energy Patch content pack.
The plan should connect the beginner guide, comparison pages, FAQ, placement guide, troubleshooting page, ingredient hub, review/proof page, and product page into a clear reader journey.
The goal is to test whether Content Brain can plan internal links, hub/spoke relationships, topic support, buyer journey flow, and publishing readiness before content is created.
Pages Used
Content Brain Workflow
Content Brain Internal Linking
Content Brain Topic Cluster And Hub Architecture Framework
Content Brain Publishing Readiness Checklist
Content Brain Site Content Intelligence Framework
Content Brain Affiliate Content Packs
Content Brain E E A T Content Trust Framework
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
HeadOffice Brain
Output Created
Internal linking and topic cluster plan for the Endorfix / Elevate Energi Energy Patch content pack.
Approval Owner
HeadOffice
Risk Level
Medium
Reason:
The internal linking plan connects pages around energy, caffeine, wellness, product use, customer proof, ingredients, appetite, sleep, and performance-related topics.
This means the cluster needs careful linking logic so buyer education does not accidentally amplify unsupported claims or push users too aggressively toward purchase before trust and compliance checks are complete.
Result
The Internal Linking / Topic Cluster workflow successfully created a structured content relationship plan for the Endorfix / Elevate Energi Energy Patch content pack.
The test identified the main hub page as:
How Energy Patches Work: A Simple Beginner Guide
This page should act as the educational entry point and central content hub.
The test identified the main spoke pages as:
Energy Patches vs Energy Drinks: What Is The Difference?
Caffeine Patch vs Coffee: Which Fits Your Day Better?
Where To Place An Energy Patch For Best Results
Why You Might Not Feel An Energy Patch Straight Away
Energy Patch FAQ
Ingredient Education Hub
Customer Review And Proof Page
Energy Patch Product Page
The test created a clear reader journey:
education first
comparison second
usage support third
objection handling fourth
ingredient trust fifth
proof sixth
product page last
This structure protects the reader journey from becoming too sales-heavy too early.
The workflow also identified that the product page should not be the only destination from every page.
Some pages should link first to education, FAQ, placement guidance, troubleshooting, or ingredient content before linking to the product page.
This creates a safer and more useful internal linking pattern.
Internal Link Map
The beginner guide should link to:
Energy Patch Product Page
Energy Patch FAQ
Where To Place An Energy Patch For Best Results
Why You Might Not Feel An Energy Patch Straight Away
Energy Patches vs Energy Drinks
Caffeine Patch vs Coffee
Ingredient Education Hub
Customer Review And Proof Page
Energy Patches vs Energy Drinks should link to:
How Energy Patches Work: A Simple Beginner Guide
Caffeine Patch vs Coffee
Energy Patch FAQ
Energy Patch Product Page
Caffeine Patch vs Coffee should link to:
How Energy Patches Work: A Simple Beginner Guide
Energy Patches vs Energy Drinks
Energy Patch FAQ
Energy Patch Product Page
Where To Place An Energy Patch For Best Results should link to:
How Energy Patches Work: A Simple Beginner Guide
Energy Patch FAQ
Why You Might Not Feel An Energy Patch Straight Away
Energy Patch Product Page
Why You Might Not Feel An Energy Patch Straight Away should link to:
How Energy Patches Work: A Simple Beginner Guide
Where To Place An Energy Patch For Best Results
Energy Patch FAQ
Ingredient Education Hub
Energy Patch FAQ should link to:
How Energy Patches Work: A Simple Beginner Guide
Where To Place An Energy Patch For Best Results
Why You Might Not Feel An Energy Patch Straight Away
Ingredient Education Hub
Energy Patch Product Page
Ingredient Education Hub should link to:
How Energy Patches Work: A Simple Beginner Guide
Energy Patch FAQ
Customer Review And Proof Page
Energy Patch Product Page
Customer Review And Proof Page should link to:
How Energy Patches Work: A Simple Beginner Guide
Energy Patch FAQ
Energy Patch Product Page
Energy Patch Product Page should link back to:
How Energy Patches Work: A Simple Beginner Guide
Energy Patch FAQ
Where To Place An Energy Patch For Best Results
Why You Might Not Feel An Energy Patch Straight Away
Ingredient Education Hub
What Should Not Be Linked Too Aggressively
The product page should not be forced too early from every sentence or section.
The review/proof page should not be used to support exaggerated claims.
The ingredient hub should not be used to imply medical benefits.
The troubleshooting page should not imply that all non-response is user error.
The comparison pages should not attack coffee or energy drinks too aggressively.
The FAQ should not hide safety or sensitivity notes.
The internal linking should support education, trust, and clarity before conversion.
Publishing Readiness Assessment
Publishing Status:
Not ready for publishing yet.
Reason:
This is an internal linking and cluster plan, not final published content.
The plan is approved for use during content briefing and drafting.
Recommended next status:
Internal Linking Plan Approved For Briefing
Recommended first asset to brief:
How Energy Patches Work: A Simple Beginner Guide
Recommended follow-up asset:
Energy Patch FAQ
Recommended compliance status:
Compliance review required before publishing any page in this cluster.
Workflow Verdict
Passed.
Content Brain successfully created an internal linking and topic cluster plan before the content was created.
The workflow handled:
hub page selection
spoke page selection
reader journey planning
product page support linking
trust and proof linking
FAQ linking
troubleshooting linking
ingredient hub linking
claims-sensitive linking
publishing readiness assessment
This confirms that Content Brain can plan the content ecosystem around an affiliate product instead of treating each content asset as isolated.
Friction Found
The internal linking workflow works manually, but it may later need a cleaner repeatable internal linking template.
The future template should include fixed fields for:
hub page
spoke pages
reader journey stage
primary internal links
secondary internal links
product page links
trust/proof links
support/FAQ links
compliance-sensitive links
links to avoid
publishing readiness status
recommended next action
The workflow also showed that internal linking should not only be SEO-driven.
For affiliate and product content, internal linking must also consider:
reader trust
claim safety
buyer stage
objection handling
support content
proof control
conversion timing
Future Build Evidence
This test supports future candidates such as:
Internal Linking Planner
Topic Cluster Planner
Hub And Spoke Planner
Reader Journey Link Mapper
Affiliate Product Cluster Planner
Product Page Support Link Planner
Compliance-Sensitive Internal Link Review Step
Publishing Readiness Checklist UI
Internal Linking Status Field
However, no build should start yet.
More repeated internal linking tests are needed before creating build specifications.
Recommended Next Action
Run Manual Workflow Test 8 using another real external site intelligence review on a different site type.
Suggested options:
MWMSGlobal.com
MWMSNetwork.com
mwmscontentbrain.site after more pages are created
one affiliate landing/content site currently being used for testing
Purpose:
Check whether Site Content Intelligence still works when the site structure, offer, tone, and commercial model are different.
Think-ahead impact after this test:
Content Brain Manual Workflow Test Log has moved from v1.3 to v1.4.
Content Brain Page Registry should move from v1.9 to v2.0.
Page count stays 39.
No new page created.
No Canon update required.
No Architecture update required.
No plugin/UI work.
No Supabase work.
No Brain Room routing.
No M build work touched.
Save Point
Content Brain — Internal Linking And Topic Cluster Workflow Tested / Manual Workflow Test 7 Passed / Affiliate Content Cluster Planned / Manual Workflow Evidence Growing / Manual Workflow Only / Plugin UI Not Started
Manual Workflow Test 8
Test Number: 8
Test Name: MWMSNetwork Aqua Tower Site Content Intelligence Review
Date: 2026-06-04
Status: Passed With Friction
Test Type: Second Real External Site Content Intelligence Workflow
Request
Review MWMSNetwork.com and identify what content already exists, what the site tone feels like, what content gaps remain, what should be refreshed, what should be internally linked, and what content should be created next.
The goal is to test whether the Site Content Intelligence Framework still works on a different affiliate/campaign-style site structure, not only the Endorfix / Elevate Energi product ecosystem.
Pages Used
Content Brain Workflow
Content Brain Site Content Intelligence Framework
Content Brain SEO Content Briefs
Content Brain Affiliate Funnel Support
Content Brain Internal Linking
Content Brain Publishing Readiness Checklist
Content Brain E E A T Content Trust Framework
Content Brain Information Gain Framework
Content Brain Intent Alignment Framework
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
Ads Brain
HeadOffice Brain
Output Created
Site Content Intelligence Review for MWMSNetwork Aqua Tower campaign direction.
Approval Owner
HeadOffice
Risk Level
Medium to High
Reason:
The site appears connected to Aqua Tower / water-generation / preparedness-style affiliate messaging.
This category can involve water security claims, emergency preparedness claims, survival-style urgency, filtration/purification claims, environmental or drought-related claims, technology explanation claims, household safety claims, and affiliate offer pre-sell claims.
Because of this, Content Brain should include Compliance Brain early before any new public-facing content is created or refreshed.
Result
The Site Content Intelligence Framework successfully worked on a second external affiliate/campaign-style site.
The test found that MWMSNetwork appears to have at least one campaign-style content page connected to Aqua Tower and the “Most Overqualified Dehumidifier” angle.
The indexed page direction suggests the site is being used for affiliate pre-sell or bridge-page style content rather than a broad ecommerce content hub.
The content appears to focus on:
water-from-air positioning
filtration and purification
clean cold water delivery
preparedness-style product curiosity
dehumidifier comparison / repositioning angle
VSL support direction
The site tone appears to be:
curiosity-driven
campaign-focused
affiliate pre-sell oriented
lightly humorous
problem-aware
product-teaser focused
urgency-capable
less ecommerce-style than Endorfix
more bridge-page / advertorial-style than product catalogue
This makes it a useful second test because it proves Site Content Intelligence can handle a campaign/bridge-page structure, not only a product-store structure.
Existing Content Inventory
Confirmed or strongly indicated content:
Aqua Tower-related campaign landing page
“The Most Overqualified Dehumidifier You’ll Ever Meet” angle
water generation / water purification positioning
VSL-support style content
affiliate bridge-page style messaging
Likely site role:
pre-sell page
campaign support page
VSL transition page
offer education page
Google Ads / YouTube Ads support destination
What Content Gaps Remain
The biggest gap is not more hype.
The biggest gap is supporting education and trust around the idea of water-from-air technology.
Recommended content gaps:
Beginner education page
What Is An Atmospheric Water Generator?
Purpose:
Explain the concept clearly before sending people to a VSL.
Aqua Tower explanation page
How Does Aqua Tower Claim To Make Water From Air?
Purpose:
Clarify the mechanism without overstating or making unsupported technical claims.
Preparedness education page
Why Some Families Are Looking For Backup Water Options
Purpose:
Support the preparedness angle without fearmongering.
Comparison page
Atmospheric Water Generator vs Dehumidifier: What Is The Difference?
Purpose:
Clarify the “overqualified dehumidifier” angle safely.
FAQ page
Aqua Tower Questions Before Watching The Video
Purpose:
Reduce confusion and answer buyer objections.
Trust page
What To Check Before Relying On Any Backup Water System
Purpose:
Build trust and reduce compliance risk.
Refresh page
Update The Current Landing Page For Claim Safety And Reader Clarity
Purpose:
Make the bridge page safer, clearer, and more useful.
What Should Be Refreshed
The main campaign page should be reviewed for:
claim strength
clarity
tone balance
VSL transition logic
water safety language
filter/purification wording
urgency language
reader expectation setting
compliance-sensitive claims
The “overqualified dehumidifier” angle is strong, but it should not make the product sound like a normal dehumidifier or imply technical equivalence unless that is clearly explained.
The page should avoid implying:
guaranteed water production
unlimited water
works in all climates
replaces municipal water
solves water shortage risk by itself
medical-grade purification
government-level emergency protection
instant household independence
zero ongoing maintenance
safe drinking water without conditions
What Should Be Internally Linked
The campaign page should link to:
What Is An Atmospheric Water Generator?
Purpose:
Explain the broader concept.
How Does Aqua Tower Claim To Make Water From Air?
Purpose:
Explain the product mechanism.
Atmospheric Water Generator vs Dehumidifier
Purpose:
Clarify the creative angle.
Backup Water Options For Families
Purpose:
Support the preparedness angle.
Aqua Tower FAQ
Purpose:
Handle objections before the VSL.
What To Check Before Relying On Any Backup Water System
Purpose:
Build trust and reduce overclaim risk.
VSL page / offer page
Purpose:
Move educated readers to the offer.
Recommended Reader Journey
Best journey:
curiosity angle
basic education
technology explanation
comparison clarification
preparedness context
FAQ / trust support
VSL
Avoid:
curiosity angle
fear spike
instant product push
unsupported promise
VSL
The second path may create stronger short-term clicks but higher compliance risk and weaker trust.
What Content Should Be Created Next
Recommended next content asset:
Atmospheric Water Generator vs Dehumidifier: What Is The Difference?
Reason:
This directly supports the “Most Overqualified Dehumidifier” campaign angle.
It can explain the creative comparison without confusing the reader.
It can internally link back to the campaign page and forward to the VSL.
It can reduce risk that the hook is seen as misleading.
It gives Content Brain a strong bridge between ad curiosity and product education.
Recommended secondary asset:
Aqua Tower Questions Before Watching The Video
Reason:
This would support the VSL journey and reduce buyer confusion.
Compliance Notes
Compliance Brain should review any content that mentions:
water security
emergency water
drought
water shortages
filtration
purification
clean drinking water
contaminants
health/safety
self-reliance
off-grid survival
family safety
government failure
disaster preparedness
Use safer wording such as:
may help
backup water option
designed to support
learn how it works
watch the explanation
depending on conditions
results may vary
important to understand limitations
Avoid wording such as:
guaranteed water
unlimited water
never run out
survive any crisis
replaces your tap
makes any air safe
medical-grade water
no risk
works everywhere
government-proof solution
Publishing Readiness Assessment
Publishing Status:
Not ready for new publishing yet.
Reason:
This is a Site Content Intelligence review, not a final content brief or final publishable asset.
Recommended next status:
Site Intelligence Approved For Briefing
Recommended first brief:
Atmospheric Water Generator vs Dehumidifier: What Is The Difference?
Recommended brief type:
SEO / Affiliate Pre-Sell Education Brief
Recommended compliance status:
Compliance review required before publishing.
Workflow Verdict
Passed With Friction.
Content Brain successfully reviewed a second external campaign-style site and produced useful site intelligence, content gaps, refresh direction, internal linking direction, and next content recommendations.
The workflow proved that Site Content Intelligence can work beyond product-store sites.
It can also support:
affiliate bridge pages
campaign landing pages
VSL support pages
curiosity-angle pages
pre-sell education pages
The friction is that the available public site evidence was limited to an indexed page result, not a full crawl of the entire site.
Friction Found
The Site Content Intelligence workflow worked, but external site review needs clearer source depth labels.
Recommended source depth labels:
Full Site Crawl
Partial Site Review
Single Page Review
User-Supplied Page Copy Review
Screenshot-Based Review
Indexed Search Result Review
For this test, the correct source depth is:
Indexed Search Result Review / Partial Site Review
The workflow also needs a clearer rule for affiliate bridge pages because campaign sites are different from normal blogs or ecommerce stores.
Bridge pages need special attention to:
hook accuracy
VSL transition
claim safety
reader expectation setting
ad-to-page message match
compliance-sensitive urgency
Future Build Evidence
This test supports future candidates such as:
Site Content Intelligence Report Generator
Affiliate Landing Page Review Workflow
Bridge Page Content Gap Finder
VSL Support Content Planner
Ad-To-Page Message Match Checker
Compliance-Sensitive Claim Detector
Curiosity Hook Safety Checker
Internal Linking Planner
Publishing Readiness Checklist UI
Source Depth Label Field
However, no build should start yet.
More repeated manual tests are needed before creating build specifications.
Recommended Next Action
Run Manual Workflow Test 9 using another Affiliate Product Content Pack request for a different offer or niche.
Purpose:
Check whether the affiliate product content pack structure holds outside Endorfix / Elevate Energi.
Suggested options:
Aqua Tower / MWMSNetwork
Genius Wave / MWMSGlobal
another current affiliate campaign site
Recommended Test 9:
Aqua Tower Affiliate Product Content Pack Test
Reason:
Test 8 reviewed MWMSNetwork, so the next useful test is whether Content Brain can turn that site intelligence into a practical affiliate content pack.
Save Point
Content Brain — Second Real Site Intelligence Workflow Tested / Manual Workflow Test 8 Passed With Friction / MWMSNetwork Aqua Tower Site Direction Reviewed / Manual Workflow Evidence Growing / Manual Workflow Only / Plugin UI Not Started
Manual Workflow Test 9
Test Number: 9
Test Name: Aqua Tower Affiliate Product Content Pack Test
Date: 2026-06-04
Status: Passed With Friction
Test Type: Affiliate Product Content Pack Workflow
Request
Create an affiliate product content pack for Aqua Tower / MWMSNetwork.
The pack should support buyer education, affiliate pre-sell content, bridge-page support, VSL preparation, internal linking, objection handling, trust-building, and safe content direction.
The goal is not to create fear-heavy survival copy.
The goal is to create a practical affiliate/campaign content pack that can support YouTube ads, landing pages, bridge pages, blog content, VSL transitions, email follow-up, and buyer reassurance.
Pages Used
Content Brain Workflow
Content Brain Affiliate Product Content Pack Checklist
Content Brain Affiliate Funnel Support Map
Content Brain Publishing Readiness Checklist
Content Brain Site Content Intelligence Framework
Content Brain Internal Linking Strategy Framework
Content Brain E E A T Content Trust Framework
Content Brain Information Gain Framework
Content Brain Intent Alignment Framework
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
Ads Brain
HeadOffice Brain
Output Created
Affiliate Product Content Pack for Aqua Tower / MWMSNetwork campaign direction.
Approval Owner
HeadOffice
Risk Level
Medium to High
Reason:
The offer category involves water security, atmospheric water generation, emergency preparedness, drought concerns, filtration/purification wording, household safety, self-reliance, and affiliate pre-sell claims.
These areas can easily drift into fearmongering, unsupported technical claims, survival exaggeration, or misleading product expectations.
Compliance Brain should be involved before any public-facing copy is published.
Content Pack Name
Aqua Tower Backup Water Education Content Pack
Product / Offer
Aqua Tower / MWMSNetwork campaign direction
Content Pack Purpose
This content pack supports buyer education, pre-sell clarity, trust-building, and VSL preparation for people interested in backup water options and water-from-air technology.
The pack should help explain the idea behind atmospheric water generation, how the campaign angle differs from normal dehumidifier thinking, what questions a visitor should ask before watching the VSL, and what realistic expectations should be set.
The content pack should support curiosity without relying on fear-heavy survival pressure.
Primary Audience
People interested in backup water options, preparedness, self-reliance, and household resilience.
Secondary Audience
Rural and remote households
Preparedness-minded families
People concerned about drought or water restrictions
Off-grid or semi-off-grid homeowners
People curious about water-from-air technology
People who clicked from a YouTube ad or pre-video
People who need more explanation before watching a VSL
Audience Awareness Stage
Problem aware
Solution curious
Product aware after watching ad or landing page
Main Reader Problems
I am concerned about water reliability.
I want to understand backup water options.
I do not fully understand water-from-air technology.
I want to know how this is different from a dehumidifier.
I want to know if the idea is practical.
I want to understand the limitations before watching a sales video.
I want to avoid being misled by hype.
Main Buyer Questions
What is Aqua Tower?
What is atmospheric water generation?
How can water be pulled from air?
How is this different from a dehumidifier?
What conditions affect water output?
Does it filter or purify the water?
Is this for emergencies only or daily use?
What should I understand before watching the VSL?
What claims should I be careful about?
What are realistic expectations?
Core Content Angle
A curiosity-led backup water education angle.
The content should position Aqua Tower as something worth learning about, not as a guaranteed emergency solution.
The safest angle is:
“Before you judge the idea of water from air, understand what the technology is trying to do, what affects output, and what questions to ask before relying on any backup water system.”
Tone Direction
Curious
Practical
Educational
Preparedness-aware
Trust-building
Calm
Non-hype
Non-fearmongering
Not doom-heavy
Not exaggerated
Not anti-government
Not miracle-solution language
Claims To Avoid
Do not claim guaranteed water production.
Do not claim unlimited water.
Do not claim it works in all climates.
Do not claim it replaces municipal water.
Do not claim it solves water shortages by itself.
Do not claim medical-grade purification.
Do not claim it makes unsafe air automatically safe.
Do not claim zero maintenance.
Do not claim no electricity or no operating requirements unless fully verified.
Do not claim families can rely on it in every emergency.
Do not imply government failure as the only reason to buy.
Do not use disaster panic as the main driver.
Recommended Content Assets
Asset 1
Atmospheric Water Generator vs Dehumidifier: What Is The Difference?
Purpose:
Support the “Most Overqualified Dehumidifier” campaign angle without making the page misleading.
Use For:
Bridge page support
SEO article
YouTube ad support
VSL preparation
Internal link hub
Main Sections:
Why people compare the two
What a dehumidifier is designed to do
What an atmospheric water generator is trying to do
Why filtration and intended use matter
What conditions can affect water output
What to understand before watching the VSL
Soft CTA to learn more
Asset 2
What Is An Atmospheric Water Generator?
Purpose:
Create beginner-level education around the core concept.
Use For:
Blog article
Landing page support
VSL pre-frame
Email education
Main Sections:
Simple definition
How the idea works at a high level
Why humidity and conditions matter
Why filtration matters
Where the idea may fit in a backup plan
What not to assume
Soft CTA to watch the explanation
Asset 3
Aqua Tower Questions Before Watching The Video
Purpose:
Prepare users for the VSL and reduce confusion.
Use For:
FAQ page
Bridge page support
Email follow-up
YouTube description link
Main Sections:
What is the concept?
What does the video explain?
What should I pay attention to?
What conditions matter?
What should I not assume?
What questions should I ask before relying on any backup water system?
Asset 4
Why Some Families Are Looking For Backup Water Options
Purpose:
Support the preparedness angle without fearmongering.
Use For:
Educational article
Ad support content
Awareness-stage content
Main Sections:
Water reliability concerns
Weather and supply disruption concerns
Remote and rural household challenges
Why backup planning matters
Why no single solution should be overhyped
Soft CTA to learn about one possible option
Asset 5
What To Check Before Relying On Any Backup Water System
Purpose:
Build trust and reduce exaggerated claims.
Use For:
Trust page
Compliance support
Buyer education
Internal linking
Main Sections:
Output conditions
Power needs
Maintenance
Filtration
Water quality guidance
Local conditions
Storage
Emergency planning basics
Asset 6
Aqua Tower FAQ
Purpose:
Handle common objections and support VSL conversion.
Use For:
FAQ page
Landing page support
Main Questions:
What is Aqua Tower?
How does water-from-air technology work?
What affects output?
Is humidity important?
Does it filter the water?
Is it a replacement for tap water?
Can it be used off-grid?
What should I understand before buying?
Asset 7
Backup Water Planning Checklist
Purpose:
Create a practical, trust-building support asset.
Use For:
Lead magnet
Blog post
Email follow-up
Buyer education
Main Sections:
Current water sources
Emergency storage
Filtration options
Power needs
Household usage needs
Backup plan review
Questions before buying any device
Asset 8
Aqua Tower VSL Watch Guide
Purpose:
Improve VSL readiness and help visitors watch with clarity.
Use For:
Bridge page
YouTube description
Retargeting page
Main Sections:
What to listen for
What questions the video should answer
What claims to evaluate
What limitations to consider
How to decide if the idea fits your household
Internal Linking Plan
Main campaign page should link to:
Atmospheric Water Generator vs Dehumidifier
What Is An Atmospheric Water Generator?
Aqua Tower Questions Before Watching The Video
What To Check Before Relying On Any Backup Water System
VSL page / offer page
Atmospheric Water Generator vs Dehumidifier should link to:
Main campaign page
What Is An Atmospheric Water Generator?
Aqua Tower FAQ
VSL page / offer page
What Is An Atmospheric Water Generator should link to:
Atmospheric Water Generator vs Dehumidifier
Backup Water Planning Checklist
Aqua Tower FAQ
VSL page / offer page
Aqua Tower Questions Before Watching The Video should link to:
Main campaign page
Aqua Tower FAQ
What To Check Before Relying On Any Backup Water System
VSL page / offer page
Why Some Families Are Looking For Backup Water Options should link to:
What Is An Atmospheric Water Generator?
Backup Water Planning Checklist
Main campaign page
What To Check Before Relying On Any Backup Water System should link to:
Backup Water Planning Checklist
Aqua Tower FAQ
Main campaign page
Aqua Tower FAQ should link to:
What Is An Atmospheric Water Generator
Atmospheric Water Generator vs Dehumidifier
What To Check Before Relying On Any Backup Water System
VSL page / offer page
Backup Water Planning Checklist should link to:
What To Check Before Relying On Any Backup Water System
Aqua Tower FAQ
Main campaign page
Aqua Tower VSL Watch Guide should link to:
Main campaign page
Aqua Tower FAQ
VSL page / offer page
Content Pack Publishing Readiness
Publishing Status:
Not ready for publishing yet.
Reason:
This is a content pack plan, not final copy.
The pack should move to briefing before drafting.
Recommended next status:
Content Pack Approved For Briefing
Recommended first brief:
Atmospheric Water Generator vs Dehumidifier: What Is The Difference?
Recommended brief type:
SEO / Affiliate Pre-Sell Education Brief
Recommended compliance status:
Compliance review required before publishing.
Workflow Verdict
Passed With Friction.
Content Brain successfully created an affiliate product content pack for a different offer/niche from Endorfix.
This proves the Affiliate Product Content Pack workflow can transfer beyond wellness patches into a preparedness/water-technology affiliate campaign.
The workflow handled:
offer education
audience awareness
buyer questions
pre-sell positioning
VSL support
internal linking
trust-building
claims control
publishing readiness
next content recommendation
This confirms that Content Brain can support affiliate campaign content planning across different product categories.
Friction Found
The workflow worked, but Aqua Tower requires stronger compliance and evidence discipline than Endorfix because the claims can easily become too broad.
Specific friction:
Source depth is still limited.
Some content direction depends on what the live site, VSL, vendor claims, and official product materials actually say.
The content pack should not invent technical proof.
The system needs a stronger “offer evidence required” note before final briefs.
Future affiliate content pack tests should include:
source depth label
official vendor claims available
VSL reviewed yes/no
landing page reviewed yes/no
compliance risk level
proof required before publishing
This test also confirms that affiliate product packs may need niche-specific risk rules.
Aqua Tower risk rules are different from Endorfix risk rules.
Future Build Evidence
This test supports future candidates such as:
Affiliate Product Content Pack Generator
Affiliate Funnel Support Planner
VSL Support Content Planner
Bridge Page Content Planner
Ad-To-Page Message Match Checker
Source Depth Label Field
Offer Evidence Required Field
Compliance-Sensitive Claims Review Step
Affiliate Product Risk Rules
Internal Linking Planner
Publishing Readiness Checklist UI
However, no build should start yet.
More repeated manual testing is still preferred before creating build specifications.
Recommended Next Action
Run Manual Workflow Test 10 using an Aqua Tower landing page / bridge page refresh request.
Purpose:
Check whether Content Brain can improve a real affiliate landing or bridge page, not just create a content pack.
Suggested test:
Aqua Tower Landing Page / Bridge Page Refresh Test
Suggested path:
Content Brain Workflow
Content Brain Refresh
Content Brain Content Optimization Framework
Content Brain Affiliate Funnel Support Map
Content Brain Publishing Readiness Checklist
Save Point
Content Brain — Aqua Tower Affiliate Product Content Pack Tested / Manual Workflow Test 9 Passed With Friction / Affiliate Product Pack Workflow Proven Across Second Niche / Manual Workflow Evidence Growing / Manual Workflow Only / Plugin UI Not Started
Manual Workflow Test 10
Test Number: 10
Test Name: Aqua Tower Landing Page / Bridge Page Refresh Test
Date: 2026-06-04
Status: Passed With Friction
Test Type: Landing Page Refresh / Bridge Page Optimization Workflow
Request
Review the Aqua Tower / MWMSNetwork campaign direction and identify how Content Brain would refresh or improve the landing page / bridge page before it is treated as publishing-ready or campaign-ready.
The refresh should improve clarity, trust, VSL transition, claims safety, buyer education, ad-to-page message match, internal linking, and publishing readiness.
The goal is to test whether Content Brain can improve a real affiliate campaign / bridge page, not just create a content pack or proposed article plan.
Pages Used
Content Brain Workflow
Content Brain Refresh
Content Brain Content Optimization Framework
Content Brain Affiliate Funnel Support Map
Content Brain Publishing Readiness Checklist
Content Brain Site Content Intelligence Framework
Content Brain E E A T Content Trust Framework
Content Brain Intent Alignment Framework
Content Brain Internal Linking Strategy Framework
Source
Manual Operator Request
Source Brain
Content Brain
Supporting Brains
Affiliate Brain
Conversion Brain
Compliance Brain
Research Brain
Search Intelligence Brain
Ads Brain
HeadOffice Brain
Output Created
Landing Page / Bridge Page Refresh Review for the Aqua Tower / MWMSNetwork campaign direction.
Approval Owner
HeadOffice
Risk Level
Medium to High
Reason:
The campaign direction involves atmospheric water generation, water backup, household resilience, preparedness, filtration/purification wording, water security, and VSL-driven affiliate pre-sell.
These areas require careful handling because the page could easily drift into exaggerated emergency claims, fear-heavy positioning, unsupported technology claims, or misleading product expectations.
Result
The Landing Page Refresh / Bridge Page Optimization workflow successfully reviewed the Aqua Tower / MWMSNetwork campaign direction and identified how the page should be improved before being treated as campaign-ready.
The test found that the landing page direction is useful because it has a strong curiosity hook:
The Most Overqualified Dehumidifier You’ll Ever Meet
This is a strong creative angle because it creates curiosity and gives the visitor a simple mental comparison.
However, the page should be refreshed so the hook does not create confusion.
The page should clearly explain that the comparison is a positioning hook, not a claim that the product is just a standard dehumidifier.
The bridge page should help the visitor understand enough to want to watch the VSL, but it should not try to prove everything on the page itself.
The main refresh goal is to move from:
curiosity only
to:
curiosity plus safe education plus clear VSL transition
The page should not become a long technical article.
It should act as a bridge:
ad click
curiosity confirmation
simple explanation
realistic expectation setting
reason to watch the video
soft VSL transition
What Needs Improving
Clarity
The page should quickly explain:
why the dehumidifier comparison is being used
what atmospheric water generation means at a simple level
why conditions matter
why filtration/purification language must be handled carefully
what the visitor should watch for in the VSL
Trust
The page should include trust-building language that makes it clear the reader should understand the idea before making assumptions.
Recommended trust framing:
This page introduces the concept.
The video explains the full process.
Output and suitability may depend on conditions.
Any backup water system should be evaluated carefully.
No single device should be treated as a complete household water plan without understanding limitations.
Buyer Education
The page should add a short “What to understand before watching” section.
This section should include:
humidity matters
conditions matter
filtration matters
maintenance may matter
power requirements may matter
backup planning should be practical
the VSL should be watched for the full explanation
VSL Transition
The page should improve the transition into the VSL.
Instead of pushing too hard, it should say something like:
Before assuming this is just another gadget, watch the short explanation to see how the system is positioned, what it is designed to do, and what questions you should consider before deciding whether it fits your household.
This is safer than:
Watch now before it is too late.
This one device could solve your water problems.
Never worry about water again.
Ad-To-Page Match
The landing page should match the creative hook used in the ad.
If the ad says:
The Most Overqualified Dehumidifier You’ll Ever Meet
Then the page should immediately confirm that idea and explain it.
Recommended opening structure:
Headline:
The Most Overqualified Dehumidifier You’ll Ever Meet
Subhead:
It is not about drying a room. It is about understanding how water-from-air technology is being positioned as a backup water option.
Then move into:
why the comparison matters
what the visitor should know
why the video explains the full concept
Claims To Soften
Claim type:
makes clean water from air
Safer version:
is positioned around the idea of collecting water from air and filtering it for use, depending on the system and conditions
Claim type:
solves water shortages
Safer version:
may interest people exploring backup water options
Claim type:
works anywhere
Safer version:
output and suitability may depend on local conditions, humidity, setup, and system limitations
Claim type:
replaces tap water
Safer version:
should be evaluated as one possible backup water option, not assumed to replace normal water sources
Claim type:
emergency water solution
Safer version:
may be part of a broader household preparedness plan
Claim type:
safe drinking water
Safer version:
water quality, filtration, maintenance, and usage guidance should be understood before relying on any system
Sections To Add Or Refresh
Section 1: Hook Confirmation
Purpose:
Confirm the ad promise and explain the creative angle.
Suggested direction:
You may have heard it compared to a dehumidifier, but the real point is what the system is trying to do with moisture in the air.
Section 2: Simple Concept Explanation
Purpose:
Give a plain-language explanation of water-from-air technology without overclaiming.
Include:
air moisture
collection process
filtration concept
conditions matter
watch the video for details
Section 3: What This Is Not
Purpose:
Reduce hype and build trust.
Include:
not unlimited water
not guaranteed in every condition
not a replacement for understanding household water needs
not something to judge from a headline only
Section 4: Why People Are Looking At Backup Water Options
Purpose:
Support the preparedness angle without fear.
Include:
supply interruptions
rural/remote concerns
drought awareness
household planning
self-reliance curiosity
Avoid:
panic
government failure framing
disaster doom
Section 5: Questions To Ask Before Relying On Any Backup Water System
Purpose:
Create trust and credibility.
Questions:
What conditions affect output?
What maintenance is needed?
How is water filtered?
What power is required?
What role does it play in a broader backup plan?
What does the VSL explain?
Section 6: Watch The Explanation
Purpose:
Soft transition to VSL.
CTA style:
See how the system is explained in the video.
Avoid:
click now before it is banned
watch before this disappears
your family may not survive without this
Internal Linking Recommendations
The landing / bridge page should link to:
Atmospheric Water Generator vs Dehumidifier: What Is The Difference?
Purpose:
Clarify the main campaign angle.
What Is An Atmospheric Water Generator?
Purpose:
Educate visitors who need the basic concept.
Aqua Tower Questions Before Watching The Video
Purpose:
Prepare visitors for the VSL.
What To Check Before Relying On Any Backup Water System
Purpose:
Build trust and reduce overclaim risk.
Backup Water Planning Checklist
Purpose:
Give practical household planning context.
VSL / offer page
Purpose:
Move qualified visitors to the sales explanation.
What Should Not Be Linked Too Aggressively
The bridge page should not push the VSL before basic context is established.
The bridge page should not over-link to the product page from every section.
The bridge page should not link proof or review content in a way that implies guaranteed outcomes.
The bridge page should not use preparedness pages to create fear pressure.
The bridge page should not link to technical explanation pages unless those pages are claim-safe and reviewed.
Publishing Readiness Assessment
Publishing Status:
Not ready for campaign scaling yet.
Reason:
The landing / bridge page direction needs a claim-safety refresh, clearer VSL transition, better explanation of the dehumidifier comparison, and stronger expectation-setting before being treated as campaign-ready.
Recommended next status:
Bridge Page Approved For Refresh Brief
Recommended brief type:
Affiliate Landing Page / Bridge Page Refresh Brief
Recommended compliance status:
Compliance review required before campaign scaling.
Recommended first refresh priority:
Rewrite the opening section so the dehumidifier comparison is clear, curiosity-driven, and not misleading.
Workflow Verdict
Passed With Friction.
Content Brain successfully reviewed an affiliate landing / bridge page direction and identified how it should be improved before being treated as campaign-ready.
The workflow handled:
landing page refresh logic
bridge page positioning
ad-to-page message match
VSL transition improvement
buyer education
trust-building
claims softening
internal linking
compliance risk
publishing readiness
This confirms that Content Brain can improve campaign-facing affiliate pages, not only blog-style assets, content packs, or proposed articles.
Friction Found
The workflow worked, but a bridge page refresh has different needs from a normal content refresh.
A normal article refresh focuses on clarity, usefulness, SEO, freshness, and internal links.
A bridge page refresh also needs:
ad-to-page match
hook accuracy
VSL transition quality
claim control
curiosity balance
CTA pressure control
conversion flow
compliance-sensitive urgency review
This suggests Content Brain may later need a specific:
Affiliate Bridge Page Refresh Template
or
Landing Page / Bridge Page Optimization Workflow
However, this should not be built yet.
More bridge-page tests should be completed first.
Source-depth friction also remains.
The available public evidence appears limited, so final refresh briefs should require direct page copy, screenshots, or the live page content before final approval.
Future Build Evidence
This test supports future candidates such as:
Affiliate Bridge Page Refresh Template
Landing Page Optimization Workflow
VSL Transition Checker
Ad-To-Page Message Match Checker
Curiosity Hook Safety Checker
Compliance-Sensitive Urgency Review
CTA Pressure Review
Affiliate Funnel Support Planner
Publishing Readiness Checklist UI
Bridge Page Status Field
Source Depth Label Field
Offer Evidence Required Field
However, no build should start yet.
More repeated bridge-page refresh tests are needed before creating build specifications.
Recommended Next Action
Update the Content Brain Page Registry to v2.1 after this page is saved.
Think-ahead impact:
Content Brain Manual Workflow Test Log has moved from v1.4 to v2.0.
Content Brain Page Registry should move from v2.0 to v2.1.
Page count stays 39.
No new page created.
No Canon update required.
No Architecture update required.
No plugin/UI work.
No Supabase work.
No Brain Room routing.
No M build work touched.
Save Point
Content Brain — Aqua Tower Bridge Page Refresh Tested / Manual Workflow Test 10 Passed With Friction / Affiliate Landing Page Optimization Evidence Captured / Manual Workflow Tests 1–10 Completed / Manual Workflow Only / Plugin UI Not Started
Consolidated Test Findings
The first ten manual workflow tests show that Content Brain can currently handle:
affiliate/conversion-support briefing
SEO educational content briefing
internal site content intelligence review
real external affiliate/business site content intelligence review
affiliate product content pack planning
refresh and content optimization review
internal linking and topic cluster planning
second external affiliate/campaign site intelligence review
second-niche affiliate product content pack planning
affiliate landing page / bridge page refresh review
This means the first operational layer is usable.
The operational pages work together well enough for manual use.
Content Brain should continue manual testing before any system build.
The strongest current evidence is:
Content Brain can classify content requests.
Content Brain can produce structured briefs.
Content Brain can check publishing readiness.
Content Brain can review existing site context before recommending new content.
Content Brain can detect gaps, refresh needs, internal linking opportunities, and future build candidates.
Content Brain can support affiliate/business content direction without needing technical infrastructure yet.
Content Brain can turn site intelligence into affiliate product content packs.
Content Brain can improve proposed content assets before drafting or publishing.
Content Brain can plan internal links, hub/spoke structure, and reader journey flow before content is created.
Content Brain can review affiliate bridge pages and landing pages for ad-to-page match, VSL transition, claim safety, and campaign readiness.
Content Brain can adapt workflows across different niches, including wellness/energy products and preparedness/water-backup campaigns.
Consolidated Friction List
Friction 1: Minor Naming Cleanup
Content Brain Workflow may contain an older naming reference to Content Workflow instead of Content Brain Workflow.
Priority:
Low
Recommended action:
Fix later during a small workflow refresh.
Friction 2: Brief Output Template Needed Later
Content Brain Content Briefs may need a cleaner copy-ready brief output template.
Priority:
Medium later
Recommended action:
Do not update immediately.
Confirm through more repeated brief tests first.
Friction 3: SEO Brief Template Needed Later
Content Brain SEO Content Briefs may need a cleaner reusable SEO brief template.
Priority:
Medium later
Recommended action:
Do not update immediately.
Confirm through more SEO workflow tests first.
Friction 4: Status Values Need Future Standardisation
Tests repeatedly revealed possible status values.
Priority:
Medium later
Recommended action:
Create a Content Brain Status Values Framework only after more tests confirm the status list.
Friction 5: Site Intelligence Report Template May Be Needed
The Site Content Intelligence Framework may later need a separate report template.
Priority:
Medium later
Recommended action:
Run more site reviews before creating the template.
Friction 6: External Site Reviews Need Source/Evidence Fields
Manual Workflow Test 4 and Manual Workflow Test 8 showed that external site reviews need clearer evidence notes because real websites can include live pages, customer proof, product pages, claims, blog posts, FAQs, support information, indexed search results, screenshots, and user-supplied page copy.
Priority:
Medium later
Recommended action:
Add a source/evidence field to a future Site Intelligence Report Template only after more real-site tests confirm the structure.
Friction 7: Compliance Brain Should Be Flagged Earlier For Sensitive Niches
Manual Workflow Tests 4, 8, 9, and 10 showed that sensitive product and affiliate niches need Compliance Brain awareness earlier in the workflow because claims risk can appear before content creation begins.
Priority:
High for sensitive niches
Recommended action:
For wellness, health, finance, income, legal, appetite, sleep, energy, medical, supplement, water security, emergency preparedness, filtration, purification, drought, disaster, or performance-related sites, include Compliance Brain as a supporting Brain from the start.
Friction 8: Affiliate Product Content Pack Template May Be Needed
Manual Workflow Tests 5 and 9 showed that the Affiliate Product Content Pack workflow works manually across more than one niche, but a cleaner repeatable template may be needed later.
The future template may need fields for:
product / offer
audience
awareness stage
content pack purpose
core content angles
buyer questions
asset list
internal linking plan
claims to avoid
publishing readiness status
recommended first brief
source depth
official vendor claims available
VSL reviewed yes/no
landing page reviewed yes/no
compliance risk level
proof required before publishing
Priority:
Medium later
Recommended action:
Do not create a separate template yet.
Run more affiliate product content pack tests first to confirm repeated structure.
Friction 9: Refresh Template May Be Needed
Manual Workflow Test 6 showed that the Refresh workflow works manually, but a cleaner repeatable refresh template may be needed later.
The future refresh template may need fields for:
asset being reviewed
current status
content purpose
reader intent
what needs improving
what should be added
what should be removed
claims to soften
internal links to add
trust gaps
compliance risk
publishing readiness status
recommended next action
Priority:
Medium later
Recommended action:
Do not create a separate template yet.
Run more refresh tests first to confirm repeated structure.
Friction 10: Refresh Workflow Needs Sub-Type Clarity
Manual Workflow Test 6 showed that refresh work can mean different things.
Content Brain may later need to distinguish between:
refreshing an existing live page
optimizing a proposed asset before drafting
improving a draft before publishing
landing page / bridge page refresh
Priority:
Medium later
Recommended action:
Do not create a new framework yet.
Track this distinction through future refresh tests.
Friction 11: Internal Linking Template May Be Needed
Manual Workflow Test 7 showed that the Internal Linking workflow works manually, but a cleaner repeatable internal linking template may be needed later.
The future template may need fields for:
hub page
spoke pages
reader journey stage
primary internal links
secondary internal links
product page links
trust/proof links
support/FAQ links
compliance-sensitive links
links to avoid
publishing readiness status
recommended next action
Priority:
Medium later
Recommended action:
Do not create a separate template yet.
Run more internal linking tests first to confirm repeated structure.
Friction 12: Internal Linking Must Include Reader Journey And Claim Safety
Manual Workflow Test 7 showed that internal linking should not only be SEO-driven.
For affiliate and product content, internal linking must also consider:
reader trust
claim safety
buyer stage
objection handling
support content
proof control
conversion timing
Priority:
Medium later
Recommended action:
Track this through future internal linking and affiliate content tests before creating a formal standard.
Friction 13: Affiliate Bridge Pages Need Their Own Review Logic
Manual Workflow Tests 8 and 10 showed that affiliate bridge pages are different from standard blog posts, product pages, and content hubs.
Bridge pages need specific attention to:
ad-to-page match
hook accuracy
VSL transition quality
claim control
curiosity balance
CTA pressure control
conversion flow
compliance-sensitive urgency review
Priority:
Medium to High later
Recommended action:
Do not build yet.
Run more bridge page refresh tests first.
Friction 14: Source Depth Labels Are Needed
Manual Workflow Tests 8, 9, and 10 showed that Content Brain should know how much evidence it is working from.
Recommended source depth labels:
Full Site Crawl
Partial Site Review
Single Page Review
User-Supplied Page Copy Review
Screenshot-Based Review
Indexed Search Result Review
VSL Reviewed
VSL Not Reviewed
Official Vendor Materials Reviewed
Official Vendor Materials Not Reviewed
Priority:
Medium later
Recommended action:
Add source depth fields later if repeated tests confirm the need.
Future Build Candidates Identified
Possible future system candidates from testing:
Content Brief Generator
SEO Brief Generator
Publishing Readiness Checklist UI
Content Production Queue
Content Refresh Queue
Content Repurposing Queue
Content Operations Dashboard
Content Status Framework
Site Content Intelligence Employee
Site Content Intelligence Report Generator
Site Content Inventory Tool
Site Voice And Tone Extractor
Content Gap Finder
Internal Linking Opportunity Finder
Refresh Opportunity Finder
Repurposing Opportunity Finder
Compliance-Sensitive Claim Detector
Next Content Recommendation Engine
Site Intelligence To Content Brief workflow
Site Intelligence To Refresh Queue workflow
Site Intelligence To Internal Linking Planner workflow
Site Intelligence To Affiliate Content Pack Workflow
Affiliate Product Content Pack Generator
Affiliate Funnel Support Planner
Content Pack Template
Affiliate Product Content Pack Status Field
Content Optimization Workflow
Refresh Template
Content Improvement Recommendation Engine
Refresh Status Field
Draft Improvement Workflow
Internal Linking Planner
Topic Cluster Planner
Hub And Spoke Planner
Reader Journey Link Mapper
Affiliate Product Cluster Planner
Product Page Support Link Planner
Compliance-Sensitive Internal Link Review Step
Internal Linking Status Field
Affiliate Landing Page Review Workflow
Bridge Page Content Gap Finder
VSL Support Content Planner
Ad-To-Page Message Match Checker
Curiosity Hook Safety Checker
Affiliate Bridge Page Refresh Template
Landing Page Optimization Workflow
VSL Transition Checker
Compliance-Sensitive Urgency Review
CTA Pressure Review
Bridge Page Status Field
Source Depth Label Field
Offer Evidence Required Field
Affiliate Product Risk Rules
Cross-Brain Handoff Router
Content Brain AI Employee Router
These remain candidates only.
No build is authorised from these tests yet.
Build Readiness Verdict
Not build-ready yet.
Reason:
The workflows have passed ten manual tests, but build specifications should only be created after the patterns are cleaned, consolidated, and prioritised.
Content Brain is now:
workflow-usable
site-aware
integration-aware
manual-ready
real-site tested
affiliate-product-pack tested
refresh-tested
internal-linking-tested
topic-cluster-tested
affiliate-bridge-page tested
landing-page-refresh tested
not yet plugin/UI-ready
The strongest build candidates emerging from the tests are:
Site Content Intelligence Report Generator
Affiliate Product Content Pack Generator
Content Refresh Queue
Content Optimization Workflow
Internal Linking Planner
Topic Cluster Planner
Affiliate Bridge Page Refresh Template
Landing Page Optimization Workflow
Publishing Readiness Checklist UI
However, it is still too early to build.
Recommended threshold before build specification:
Complete a cleanup and synthesis pass first.
Then decide which candidate should become the first build-ready specification.
Recommended candidate for first future build spec:
Site Content Intelligence Report Generator
Reason:
It has now supported internal site review, external product site review, campaign-style site review, content gap analysis, refresh direction, internal linking direction, and affiliate product content planning.
Next Recommended Tests
Recommended next manual workflow tests:
Manual Workflow Test 11
Run another Internal Linking request using a different topic or offer.
Purpose:
Check whether the internal linking workflow holds outside the Endorfix / Elevate Energi cluster.
Manual Workflow Test 12
Run another Refresh request using an actual existing live page, not a proposed content asset.
Purpose:
Check whether Content Brain can improve a real existing page as well as a proposed asset and bridge page.
Manual Workflow Test 13
Run a Repurposing request.
Purpose:
Check whether Content Brain can safely turn one approved content asset into multiple formats without changing meaning, claim strength, or audience fit.
Manual Workflow Test 14
Run a Publishing Readiness-only request.
Purpose:
Check whether Content Brain can make a final go / hold / revise decision before handoff.
Recommended immediate next action:
Do not run more tests immediately.
First complete a consolidation review of Tests 1–10 and update the Content Brain Page Registry.
Operating Rule From Testing
Content Brain should now follow this improved working sequence:
Content Brain Workflow
Content Brain Site Content Intelligence Framework when site context matters
Content Brain Content Briefs / SEO Content Briefs / Affiliate Content Packs / Affiliate Funnel Support / Refresh / Repurposing / Internal Linking
Content Brain Publishing Readiness
Content Brain Page Registry or Architecture only when structure changes
Content Brain Cross-Brain Integration Map when another Brain is involved
Compliance Brain should be included early when the content involves sensitive claims, wellness, health, finance, income, legal, supplement, appetite, sleep, energy, medical, water security, emergency preparedness, filtration, purification, drought, disaster, or performance-related topics.
Affiliate Product Content Pack Rule
When Content Brain creates an affiliate product content pack, it should include:
product / offer
content pack purpose
primary audience
secondary audience
awareness stage
main reader problems
main buyer questions
core content angle
tone direction
claims to avoid
recommended content assets
internal linking plan
compliance notes
publishing readiness status
recommended first brief
future build evidence
source depth
offer evidence required
Content packs are not final publishing assets.
A content pack should usually move to:
Content Pack Approved For Briefing
Then one asset should be selected for a full content brief.
Refresh Workflow Rule
When Content Brain runs a refresh or optimization review, it should identify which refresh type is being performed:
live page refresh
proposed asset optimization
draft improvement before publishing
landing page / bridge page refresh
The refresh review should include:
asset being reviewed
current status
content purpose
reader intent
what needs improving
what should be added
what should be removed
claims to soften
internal links to add
trust gaps
compliance risk
publishing readiness status
recommended next action
A refresh review should not automatically move content to publishing.
Publishing readiness must be checked separately.
Internal Linking Rule
When Content Brain creates an internal linking plan, it should identify:
hub page
spoke pages
reader journey stage
primary internal links
secondary internal links
product page links
trust/proof links
support/FAQ links
compliance-sensitive links
links to avoid
publishing readiness status
recommended next action
Internal linking should not only be SEO-driven.
For affiliate and product content, internal linking must also support:
reader trust
claim safety
buyer stage
objection handling
support content
proof control
conversion timing
Internal linking should move readers through education and trust before pushing product links too aggressively.
Affiliate Bridge Page Rule
When Content Brain reviews an affiliate bridge page or landing page, it should check:
ad-to-page match
hook accuracy
headline clarity
curiosity balance
VSL transition quality
claim safety
CTA pressure
reader expectation setting
proof handling
urgency language
compliance-sensitive wording
supporting internal links
publishing readiness
Bridge pages should not use fear, confusion, or exaggerated urgency as the main conversion mechanism.
Bridge pages should prepare the visitor for the VSL while keeping claims safe and expectations clear.
Source Depth Rule
When Content Brain reviews an external site, landing page, affiliate offer, VSL, or campaign page, it should record source depth.
Recommended labels:
Full Site Crawl
Partial Site Review
Single Page Review
User-Supplied Page Copy Review
Screenshot-Based Review
Indexed Search Result Review
VSL Reviewed
VSL Not Reviewed
Official Vendor Materials Reviewed
Official Vendor Materials Not Reviewed
Source depth affects confidence.
Low source depth should trigger:
Passed With Friction
or
Needs More Evidence Before Publishing
Registry Update Needed
Content Brain Page Registry should be checked to ensure this page is listed as:
Content Brain Manual Workflow Test Log
Recommended placement:
Governance And Registry Pages or Operational Logs section.
Suggested status:
Active Operational Log
Suggested version:
v2.0
Estimated page count should remain stable unless a new page is created.
The registry should also record that Manual Workflow Tests 1–10 have been completed and that the Manual Workflow Test Log now includes site intelligence, affiliate product pack, refresh, internal linking, topic cluster, and affiliate bridge page evidence.
Architectural Intent
The Content Brain Manual Workflow Test Log exists to protect MWMS from premature system build.
It records real operating evidence.
It helps distinguish between:
ideas that sound useful
workflows that actually work
friction that needs fixing
patterns that may become future systems
build candidates that are not ready yet
The long-term intent is to give M clean evidence-based build specifications later.
M should wire proven logic, not guesses.
Final Rule
Do not build Content Brain systems from theory.
Test manually first.
Record the test.
Watch for repeated patterns.
Only then create build-ready specifications.
Manual workflow evidence comes before technical wiring.
Change Log
Version: v1.0
Date: 2026-06-03
Author: HeadOffice
Change:
Created Content Brain Manual Workflow Test Log to record the first three Content Brain manual workflow tests: affiliate/conversion-support brief, SEO educational content brief, and site content intelligence review. Added test record format, test status labels, individual test records, consolidated findings, friction list, future build candidates, build-readiness verdict, next recommended tests, operating rule from testing, registry update need, and architectural intent.
Version: v1.1
Date: 2026-06-04
Author: HeadOffice
Change:
Updated Content Brain Manual Workflow Test Log with Manual Workflow Test 4: Endorfix / Elevate Energi Real Site Content Intelligence Review. Added evidence that Site Content Intelligence can work on a real external affiliate/business-style site, not only mwmscontentbrain.site. Updated current status notice, consolidated test findings, friction list, future build candidates, build-readiness verdict, next recommended tests, operating rule from testing, registry update need, and final save point.
Version: v1.2
Date: 2026-06-04
Author: HeadOffice
Change:
Updated Content Brain Manual Workflow Test Log with Manual Workflow Test 5: Endorfix Energy Patch Affiliate Product Content Pack. Added evidence that Content Brain can turn site intelligence into a practical affiliate product content pack. Updated current status notice, consolidated test findings, friction list, future build candidates, build-readiness verdict, next recommended tests, operating rule, added Affiliate Product Content Pack Rule, updated registry update note, and final save point.
Version: v1.3
Date: 2026-06-04
Author: HeadOffice
Change:
Updated Content Brain Manual Workflow Test Log with Manual Workflow Test 6: Endorfix Energy Patch Beginner Guide Refresh Test. Added evidence that Content Brain can review and improve a proposed content asset before drafting or publishing. Updated current status notice, consolidated test findings, friction list, future build candidates, build-readiness verdict, next recommended tests, operating rule, added Refresh Workflow Rule, updated registry update note, and final save point.
Version: v1.4
Date: 2026-06-04
Author: HeadOffice
Change:
Updated Content Brain Manual Workflow Test Log with Manual Workflow Test 7: Endorfix Energy Patch Internal Linking And Topic Cluster Test. Added evidence that Content Brain can plan hub/spoke relationships, internal links, reader journey flow, claim-sensitive linking, product page support links, trust/proof links, and publishing readiness before content is created. Updated current status notice, consolidated test findings, friction list, future build candidates, build-readiness verdict, next recommended tests, operating rule, added Internal Linking Rule, updated registry update note, and final save point.
Version: v2.0
Date: 2026-06-04
Author: HeadOffice
Change:
Updated Content Brain Manual Workflow Test Log with Manual Workflow Tests 8, 9, and 10.
Added Manual Workflow Test 8: MWMSNetwork Aqua Tower Site Content Intelligence Review.
Added Manual Workflow Test 9: Aqua Tower Affiliate Product Content Pack Test.
Added Manual Workflow Test 10: Aqua Tower Landing Page / Bridge Page Refresh Test.
This update records the completion of Manual Workflow Tests 1–10 and adds evidence that Content Brain can support second-site intelligence, second-niche affiliate product packs, and affiliate bridge page / landing page refresh logic.
Updated current status notice, consolidated test findings, friction list, future build candidates, build-readiness verdict, next recommended tests, operating rules, registry update note, and final save point.
Added Affiliate Bridge Page Rule and Source Depth Rule.
Change Impact Declaration
Pages Created:
None
Pages Updated:
Content Brain Manual Workflow Test Log
Pages Renamed:
None
Pages Deprecated:
None
Pages Deleted:
None
Registries Requiring Update:
Content Brain Page Registry should be checked to ensure this page is listed as:
Content Brain Manual Workflow Test Log
Status: Active Operational Log
Version: v2.0
Parent: Content Brain
The registry should also record that Manual Workflow Tests 1–10 have been completed and that the Manual Workflow Test Log now includes affiliate site intelligence, product pack, refresh, internal linking, topic cluster, bridge page, and landing page optimization evidence.
Canon Version Update Required:
No
Architecture Version Update Required:
No
Change Log Entry Required:
Recommended later in Content Brain Page Registry.
END CONTENT BRAIN MANUAL WORKFLOW TEST LOG v2.0