Content Brain Manual Workflow Test Log

Brain Name: Content Brain
Document Type: Operational Log
Status: Active Operational Log
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, manual workflow testing, operational layer validation, site intelligence 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-03

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 set of manual workflow tests.

The tested operational areas include:

affiliate and conversion support briefing

SEO educational content briefing

site content intelligence review

The first operational layer is no longer only theoretical.

It has been tested against real use cases and has passed initial manual validation.

This does not mean the system is ready for plugin/UI build.

It means the manual workflow is usable and should continue being tested.

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


Consolidated Test Findings

The first three manual workflow tests show that Content Brain can currently handle:

affiliate/conversion-support briefing

SEO educational content briefing

site content intelligence 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.

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.

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

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 initial manual tests, but more repeated use is needed before creating build specifications.

Content Brain is now:

workflow-usable

site-aware

integration-aware

manual-ready

not yet plugin/UI-ready

Next Recommended Tests

Recommended next manual workflow tests:

Manual Workflow Test 4

Run Site Content Intelligence on a real affiliate or business site.

Purpose:

Check whether the site intelligence process works outside mwmscontentbrain.site.

Manual Workflow Test 5

Run an Affiliate Product Content Pack request through:

Content Brain Workflow

Content Brain Affiliate Content Packs

Content Brain Affiliate Funnel Support

Content Brain Publishing Readiness

Purpose:

Test affiliate product support workflow in more depth.

Manual Workflow Test 6

Run a Refresh request through:

Content Brain Workflow

Content Brain Refresh

Content Brain Content Optimization Framework

Content Brain Publishing Readiness

Purpose:

Test existing content improvement workflow.

Manual Workflow Test 7

Run an Internal Linking request through:

Content Brain Workflow

Content Brain Internal Linking

Content Brain Topic Cluster And Hub Architecture Framework

Content Brain Publishing Readiness

Purpose:

Test page connection and topic cluster support.

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

Registry Update Needed

After this page is created, Content Brain Page Registry should be updated to include:

Content Brain Manual Workflow Test Log

Recommended placement:

Governance And Registry Pages or Operational Logs section.

Suggested status:

Active Operational Log

Estimated page count should increase by one.

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.

Change Impact Declaration

Pages Created:
Content Brain Manual Workflow Test Log

Pages Updated:
None

Pages Renamed:
None

Pages Deprecated:
None

Registries Requiring Update:
Content Brain Page Registry should be updated later to include this new page after creation.

Canon Version Update Required:
No

Change Log Entry Required:
Recommended later in Content Brain Page Registry.

END CONTENT BRAIN MANUAL WORKFLOW TEST LOG v1.0