Brain Name: Content Brain
Document Type: Operational Registry
Status: Active Operational Registry
Version: v2.6
Authority: HeadOffice
Parent: Content Brain
Last Reviewed: 2026-06-10
Purpose
The Content Brain Page Registry defines the live page structure used by Content Brain on mwmscontentbrain.site.
This page exists to prevent:
duplicate page creation
unclear page status
active pages being confused with legacy pages
old framework pages overriding newer operational pages
operator confusion
naming drift
parent page drift
uncontrolled page expansion
future build confusion
manual workflow evidence being lost
manual workflow synthesis being confused with build authorization
build readiness planning being confused with build authorization
future specification candidates being confused with approved implementation work
Site Intelligence test evidence being confused with downstream content production approval
M being handed planning material as build instructions
Operational Registry Notice
This page is the operational page registry for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR source of truth structure, MCR overrides it.
This page does not replace MCR.
This v2.5 page replaces the previous v2.4 WordPress registry page because the existing registry page became difficult to update and triggered WordPress JSON save failure.
The previous v2.4 page should be deleted only after this v2.5 page has been created, saved, and confirmed visible under Parent: Content Brain.
Current Operating Status
Content Brain status:
Manual Workflow Only / Plugin UI Not Started
No plugin UI has started.
No Supabase work has started.
No Brain Room routing has started.
No automation has started.
No queue work has started.
No dashboard work has started.
No generator build has started.
No AI Employee work has started.
No cross brain task wiring has started.
M’s active Research Brain work remains untouched.
Current Save Point
Content Brain — Registry v2.5 Recreated As Clean Live Page / Drift Content Brief Excluded / Site Intelligence Operating Layer Confirmed / Manual Workflow Only / Plugin UI Not Started
Current Valid Expected Page Count
54 pages
v2.5 Update Notice
This update adds the Site Intelligence operating layer and Site Intelligence test evidence layer created during the 2026-06-08 manual workflow block.
Valid added pages:
Content Brain Publishing Readiness Status Values Framework
Content Brain Source Depth And Evidence Label Framework
Content Brain Offer Evidence Requirements Framework
Content Brain Compliance Routing Needs Framework
Content Brain Human Approval Points Framework
Content Brain Future Fields To Define Later Framework
Content Brain Site Content Intelligence Report Template
Content Brain Site Intelligence To Content Brief Workflow
Content Brain Site Intelligence Manual Test Protocol
Content Brain Site Intelligence Test Log
Content Brain Site Intelligence Test 1 MWMS Content Brain Site Review
Content Brain Site Intelligence Test 2 Emergency Preparedness Affiliate Support Review
Excluded drift page:
Content Brain Content Brief Emergency Kit And First Aid Kit Fit
Reason:
This page was downstream content production drift and is not authorised as an active Content Brain page.
Handling rule:
Do not restore it.
Do not rewrite it.
Do not park it.
Do not add it to the registry.
Do not create a correction page unless HeadOffice explicitly asks for one later.
Current Content Brain Page Structure
Content Brain currently includes the following major page groups:
Active Brain Homepage
Active First Operational Layer
Active Integration Maps
Active Reference Frameworks
Site Intelligence Operating Pages
Site Intelligence Test Evidence Pages
Legacy Reference Pages
Older Legacy Pages Still Awaiting Future Update
Operational Logs And Evidence Reports
Build Readiness Planning Pages
Future Specification Candidate Pages
Governance And Registry Pages
Each group has a different purpose.
The operator should use the active first operational layer first.
Reference frameworks support deeper reasoning.
Site Intelligence operating pages support manual site review, testing, report structure, and workflow routing.
Site Intelligence test evidence pages record tests only.
Legacy pages are retained only for historical or future merge value.
Operational logs and evidence reports record and interpret manual workflow evidence before system build.
Build readiness planning pages turn evidence into controlled future specification candidate decisions.
Future specification candidate pages define what a future system may eventually need to do, but they do not authorize technical build work.
Governance pages define identity, structure, and source of truth discipline.
Active Brain Homepage
Content Brain
Status: Active
Parent: Top Level
Purpose: Main Content Brain homepage and operational index.
This page introduces Content Brain and points operators toward the active first operational layer.
It is the top level Content Brain page.
Active First Operational Layer
These are the primary operator pages for current manual Content Brain work.
Use these pages before using deeper reference frameworks or legacy pages.
Content Brain Workflow
Status: Active Operational Page
Parent: Content Brain
Purpose: Classifies content work, routes requests, parks unclear work, and protects workflow discipline.
Content Brain Content Briefs
Status: Active Operational Page
Parent: Content Brain
Purpose: Defines how general content briefs should be structured.
Content Brain SEO Content Briefs
Status: Active Operational Page
Parent: Content Brain
Purpose: Defines how search focused content briefs are prepared.
Content Brain Affiliate Content Packs
Status: Active Operational Page
Parent: Content Brain
Purpose: Defines structured affiliate product content pack planning.
Content Brain Affiliate Funnel Support
Status: Active Operational Page
Parent: Content Brain
Purpose: Maps content support to affiliate funnel stages.
Content Brain Publishing Readiness
Status: Active Operational Page
Parent: Content Brain
Purpose: Checks whether content is ready for use, publishing, handoff, refresh, or repurposing.
Content Brain Internal Linking
Status: Active Operational Page
Parent: Content Brain
Purpose: Defines how Content Brain plans page relationships and internal links.
Content Brain Repurposing
Status: Active Operational Page
Parent: Content Brain
Purpose: Defines how approved content can be reused safely across formats.
Content Brain Refresh
Status: Active Operational Page
Parent: Content Brain
Purpose: Defines how existing content is reviewed, improved, merged, retired, or updated.
Active Integration Maps
Content Brain Cross Brain Integration Map
Status: Active Integration Map
Parent: Content Brain
Purpose: Defines how Content Brain connects with other MWMS Brains.
This page maps Content Brain relationships with:
HeadOffice Brain
Research Brain
Search Intelligence Brain
Affiliate Brain
Ads Brain
Experimentation Brain
Conversion Brain
Compliance Brain
Data Brain
Finance Brain
Strategy Brain
SIT Brain
This page exists to make Content Brain integration ready for future technical wiring.
It does not authorize plugin, UI, queue, dashboard, generator, Supabase, Brain Room, or automation build by itself.
Active Reference Frameworks
These pages are active supporting frameworks.
They should be used after the active operational layer when deeper logic is needed.
They are not first layer operator workflow pages.
Content Brain Content Optimization Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how content should improve through signal informed optimization.
Content Brain Content Production System Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines structured content production from request to brief, draft, review, and handoff.
Content Brain Conversion Support Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how content supports decision readiness and conversion environments.
Content Brain E E A T Content Trust Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how content should demonstrate experience, expertise, authority, trustworthiness, transparency, and claim safety.
Content Brain Information Gain Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how MWMS content adds useful value beyond competitor content, generic AI output, and repeated market explanations.
Content Brain Intent Alignment Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how content matches reader intent, awareness stage, content depth, CTA fit, and next step logic.
Content Brain Topic Architecture Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how topics should be structured, grouped, expanded, refreshed, linked, and governed before content is created.
Content Brain Topic Cluster And Hub Architecture Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines hub, spoke, cluster, keyword cluster, topic cluster, URL cluster, and internal linking architecture.
Content Brain Site Content Intelligence Framework
Status: Active Reference Framework
Parent: Content Brain
Purpose: Defines how Content Brain reviews an existing website’s content, tone, topic coverage, gaps, internal links, refresh opportunities, repurposing opportunities, trust signals, affiliate support gaps, SEO structure, reader journey, and site specific content instructions before creating new content.
Content Brain Publishing Readiness Status Values Framework
Status: Active Reference Framework
Version: v1.0
Parent: Content Brain
Purpose: Defines the controlled status language Content Brain should use when reviewing whether content is ready for drafting, revision, publishing review, compliance routing, parking, or rejection.
Content Brain Source Depth And Evidence Label Framework
Status: Active Reference Framework
Version: v1.0
Parent: Content Brain
Purpose: Defines how Content Brain labels source depth, evidence quality, source limitations, and confidence before creating, refreshing, repurposing, or approving content.
Content Brain Offer Evidence Requirements Framework
Status: Active Reference Framework
Version: v1.0
Parent: Content Brain
Purpose: Defines what offer evidence Content Brain needs before creating, refreshing, repurposing, approving, or routing affiliate offer support content.
Content Brain Compliance Routing Needs Framework
Status: Active Reference Framework
Version: v1.0
Parent: Content Brain
Purpose: Defines when Content Brain should route content, claims, affiliate offer support material, bridge pages, VSL support content, refresh work, or publishing readiness decisions to Compliance Brain or HeadOffice before moving forward.
Content Brain Human Approval Points Framework
Status: Active Reference Framework
Version: v1.0
Parent: Content Brain
Purpose: Defines which Content Brain decisions must remain human approved before content, planning outputs, affiliate support assets, bridge page reviews, publishing readiness decisions, future specification candidates, or future build related materials move forward.
Content Brain Future Fields To Define Later Framework
Status: Active Reference Framework
Version: v1.0
Parent: Content Brain
Purpose: Defines how Content Brain should treat possible future fields before any technical build work begins.
Site Intelligence Operating Pages
These pages support manual Site Content Intelligence testing and workflow routing.
They are not build approval pages.
They are not M handoff pages.
They do not authorize plugin UI, Supabase, Brain Room routing, automation, queues, dashboards, generators, AI Employees, or cross brain wiring.
Content Brain Site Content Intelligence Report Template
Status: Active Operational Template
Version: v1.0
Parent: Content Brain
Purpose: Defines the manual report template Content Brain should use when reviewing an existing website before creating, refreshing, repurposing, linking, briefing, or approving content.
Content Brain Site Intelligence To Content Brief Workflow
Status: Active Operational Workflow
Version: v1.0
Parent: Content Brain
Purpose: Defines how Content Brain should turn a Site Content Intelligence Report into the correct next content workflow.
Important correction:
This page identifies possible downstream workflows.
It does not authorize automatic downstream execution.
Site Intelligence tests may identify a possible content brief, but the brief should not be created unless HeadOffice explicitly authorizes it.
Content Brain Site Intelligence Manual Test Protocol
Status: Active Operational Protocol
Version: v1.0
Parent: Content Brain
Purpose: Defines how Content Brain should manually test the Site Content Intelligence Report process before any future generator, UI, queue, dashboard, automation, AI Employee, Supabase structure, or M handoff is considered.
Content Brain Site Intelligence Test Log
Status: Active Operational Log
Version: v1.2
Parent: Content Brain
Purpose: Records manual Site Content Intelligence tests before any future Site Content Intelligence Report Generator, UI, queue, dashboard, automation, AI Employee, Supabase structure, Brain Room routing, cross brain wiring, or M handoff is considered.
This page currently records:
Site Intelligence Test 1 MWMS Content Brain Site Review
Site Intelligence Test 2 Emergency Preparedness Affiliate Support Review
Current Site Intelligence test summary:
Tests completed: 2
Tests passed: 1
Tests passed with friction: 1
Strong build signals: 1
Moderate build signals: 1
Current build readiness verdict:
Not build ready.
Reason:
Two Site Intelligence tests are useful evidence, but not enough to authorize generator build readiness.
Site Intelligence Test Evidence Pages
These pages record individual Site Intelligence test evidence.
They are evidence records only.
They do not authorize downstream content production.
They do not authorize article drafting.
They do not authorize affiliate promotion.
They do not authorize public publishing.
They do not authorize campaign use.
They do not authorize build work.
Content Brain Site Intelligence Test 1 MWMS Content Brain Site Review
Status: Active Operational Test Record
Version: v1.0
Parent: Content Brain
Purpose: Records the first controlled manual Site Content Intelligence test using mwmscontentbrain.site Content Brain page structure as the reviewed site.
Test result:
Passed With Friction
Build readiness signal:
Moderate Build Signal
Key value:
Confirmed Content Brain’s own site structure is strong enough to support manual Site Intelligence testing.
Main friction:
Report length and page bloat risk.
Content Brain Site Intelligence Test 2 Emergency Preparedness Affiliate Support Review
Status: Active Operational Test Record
Version: v1.0
Parent: Content Brain
Purpose: Records the second controlled manual Site Content Intelligence test using Ready.gov Build A Kit page material as authority preparedness source and Survival First Aid Kits supplied page text as commercial affiliate style offer support example.
Test result:
Passed
Build readiness signal:
Strong Build Signal
Key value:
Confirmed Content Brain can separate authority source material from commercial source material, identify offer evidence gaps, identify compliance routing needs, and recommend safe workflow direction.
Important boundary:
Test 2 does not authorize creation of an emergency kit article, content brief, affiliate content pack, campaign asset, or bridge page rewrite.
Downstream content production must be explicitly authorized by HeadOffice.
Legacy Reference Pages
These pages have been updated into legacy or reference status.
They are not active operator standards.
They are retained because they contain useful historical logic that may later be merged, retired, or converted into future system fields.
Content Brain Affiliate Conversion Support Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical affiliate conversion support logic.
Content Brain Offer Influence Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical offer interpretation and pre offer influence logic.
Content Brain Pre Sell Structure Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical pre sell structure logic.
Content Brain Research Signal Feedback Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical content to research signal feedback logic.
Content Brain Knowledge Structure Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical knowledge structure and topic relationship logic.
Content Brain Performance Measurement Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical content performance measurement and signal quality logic.
Content Brain Signal Interpretation Framework
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical content signal interpretation logic.
Content Brain Strategy Framework
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical content strategy and topic selection logic.
Content Brain Topic Authority Map
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical topic authority and knowledge domain strength logic.
Content Brain Topic Cluster Architecture
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical topic cluster logic superseded by Content Brain Topic Cluster And Hub Architecture Framework.
Content Brain Employee Registry
Status: Legacy Role Reference
Parent: Content Brain
Purpose: Early Content Brain role registry.
This page should not be treated as the final Content Brain AI Employee structure.
Older Legacy Pages Still Awaiting Future Update
These pages remain under Content Brain.
They have not yet received title cleanup or full future update.
They should be left alone for now.
Do not rename them until each page is being updated.
Content Asset Classification Framework
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical asset classification logic.
Content Audience Education Ladder
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical audience education progression logic.
Content Authority Development Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical authority development logic.
Content Behaviour Influence Model
Status: Legacy Reference
Parent: Content Brain
Purpose: Historical behaviour influence logic.
Operational Logs And Evidence Reports
These pages record or interpret manual workflow testing and operational evidence.
They help Content Brain prove what works before technical build decisions are made.
Content Brain Manual Workflow Test Log
Status: Active Operational Log
Version: v2.0
Parent: Content Brain
Purpose: Records manual workflow tests, pages used, test results, friction found, future build evidence, and build readiness signals before any Content Brain plugin, UI, queue, dashboard, generator, automation, Supabase route, Brain Room routing, or AI Employee is built.
This page currently records Manual Workflow Tests 1 to 10.
Content Brain Manual Workflow Synthesis Report
Status: Active Operational Evidence Report
Version: v1.0
Parent: Content Brain
Purpose: Summarises and interprets Manual Workflow Tests 1 to 10, identifies proven workflows, repeated friction patterns, strongest future build candidates, what should remain manual, what should not be built yet, and the recommended first future build ready specification candidate.
This page does not authorize build work by itself.
Build Readiness Planning Pages
Content Brain Build Readiness Shortlist
Status: Active Build Readiness Planning Report
Version: v1.0
Parent: Content Brain
Purpose: Turns Manual Workflow Tests 1 to 10 and the Content Brain Manual Workflow Synthesis Report into a clean shortlist of possible future build candidates.
The page confirms the strongest first future specification candidate is:
Content Brain Site Content Intelligence Report Generator Specification
This page does not authorize build work by itself.
Future Specification Candidate Pages
These pages define future system candidates at a planning level only.
They do not authorize technical build work.
They do not authorize plugin work.
They do not authorize UI work.
They do not authorize Supabase work.
They do not authorize Brain Room routing.
They do not authorize automation.
They do not authorize queues.
They do not authorize dashboards.
They do not authorize generators.
They do not authorize AI Employees.
They do not authorize cross brain routing.
They do not authorize M handoff.
Content Brain Site Content Intelligence Report Generator Specification
Status: Draft Future Specification Candidate
Version: v1.0
Parent: Content Brain
Purpose: Defines the first clean planning version of the future Content Brain Site Content Intelligence Report Generator.
This page confirms that the future Site Content Intelligence Report Generator would eventually help Content Brain review an existing site before creating, refreshing, repurposing, linking, briefing, or approving content.
This page confirms that it is not build ready.
Governance And Registry Pages
Content Brain Canon
Status: Governance Reference
Version: v1.1
Parent: Content Brain
Purpose: Defines the governing identity, boundaries, authority rules, manual first rule, cross brain authority relationships, integration ready direction, naming rules, status rules, drift protection, and future build readiness discipline for Content Brain.
Content Brain Architecture
Status: Active Architecture Reference
Version: v1.2
Parent: Content Brain
Purpose: Defines the live site operational structure of Content Brain, including operational layers, reference frameworks, legacy pages, governance pages, integration map, authority boundaries, manual first architecture, and future build readiness logic.
Content Brain Page Registry
Status: Active Operational Registry
Version: v2.5
Parent: Content Brain
Purpose: Tracks the current page structure of Content Brain on mwmscontentbrain.site.
Page Count Summary
Current visible Content Brain page structure after Site Intelligence operating pages and Site Intelligence test evidence pages were added:
Active Brain Homepage:
1 page
Active First Operational Layer:
9 child pages plus the homepage
Active Integration Maps:
1 page
Active Reference Frameworks:
15 pages
Legacy Reference Pages:
11 pages
Older Legacy Pages Awaiting Future Update:
4 pages
Operational Logs And Evidence Reports:
2 pages
Build Readiness Planning Pages:
1 page
Future Specification Candidate Pages:
1 page
Site Intelligence Operating Pages:
4 pages
Site Intelligence Test Evidence Pages:
2 pages
Governance And Registry Pages:
3 pages
Estimated current total:
56 pages
Page count change:
Previous page count:
42 pages
New page count:
56 pages
Reason for change:
The following 12 pages were added after Content Brain Page Registry v2.4:
Content Brain Publishing Readiness Status Values Framework
Content Brain Source Depth And Evidence Label Framework
Content Brain Offer Evidence Requirements Framework
Content Brain Compliance Routing Needs Framework
Content Brain Human Approval Points Framework
Content Brain Future Fields To Define Later Framework
Content Brain Site Content Intelligence Report Template
Content Brain Site Intelligence To Content Brief Workflow
Content Brain Site Intelligence Manual Test Protocol
Content Brain Site Intelligence Test Log
Content Brain Site Intelligence Test 1 MWMS Content Brain Site Review
Content Brain Site Intelligence Test 2 Emergency Preparedness Affiliate Support Review
Excluded from active page count:
Content Brain Content Brief Emergency Kit And First Aid Kit Fit
Reason:
This page was identified as workflow drift and should not be retained as an active Content Brain page unless HeadOffice explicitly chooses to retain it as a parked correction record.
Naming Rules
Live site page titles should follow these rules:
Use full Content Brain prefix for current active pages.
Do not use version numbers in page titles.
Do not use “Operational Copy” in live site page titles.
Do not use dash characters in page titles.
Do not use shortened names for active operator pages.
Do not keep old map, checklist, or framework names as active operator pages if they have been replaced.
Do not rename older legacy pages until they are being updated.
New active operational pages should sit under Parent: Content Brain.
New active reference frameworks should sit under Parent: Content Brain.
New Site Intelligence operating pages should sit under Parent: Content Brain.
New Site Intelligence test evidence pages should sit under Parent: Content Brain.
New build readiness planning pages should sit under Parent: Content Brain.
New future specification candidate pages should sit under Parent: Content Brain.
Content Brain homepage remains Top Level.
Status Rules
Use these status labels consistently:
Active
Active Operational Page
Active Integration Map
Active Reference Framework
Active Operational Registry
Active Architecture Reference
Active Operational Log
Active Operational Evidence Report
Active Build Readiness Planning Report
Active Operational Template
Active Operational Workflow
Active Operational Protocol
Active Operational Test Record
Draft Future Specification Candidate
Governance Reference
Architecture Reference
Legacy Reference
Legacy Role Reference
Retired
Parked
Do not use “Active Framework” for old pages that are no longer active operator standards.
Do not treat legacy pages as active workflow pages.
Do not treat operational logs as build authorization.
Do not treat operational evidence reports as build authorization.
Do not treat build readiness planning pages as build authorization.
Do not treat draft future specification candidate pages as build authorization.
Do not treat Site Intelligence test records as downstream content authorization.
Do not treat a possible next workflow as authorization to execute that workflow.
Site Intelligence tests record evidence.
They do not automatically authorize content briefs, drafts, publishing, affiliate content, bridge pages, campaign assets, generator work, or M handoff.
Operator Use Rule
For normal Content Brain work, use pages in this order:
Content Brain Workflow
Content Brain Site Content Intelligence Framework where existing site context matters
Content Brain Site Content Intelligence Report Template where a manual site review needs structure
Content Brain Site Intelligence To Content Brief Workflow where the next workflow needs to be identified
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
Use active reference frameworks only when deeper logic is needed.
Use legacy pages only for historical logic, future merge planning, or cleanup review.
Use Content Brain Cross Brain Integration Map when cross brain relationships matter.
Use Content Brain Canon when governing identity, authority boundaries, naming rules, status rules, or manual first discipline are unclear.
Use Content Brain Manual Workflow Test Log when recording manual workflow evidence, friction, and future build readiness signals.
Use Content Brain Manual Workflow Synthesis Report when reviewing what Tests 1 to 10 proved, which friction patterns repeated, which build candidates are strongest, and what should happen before future specifications or build work.
Use Content Brain Build Readiness Shortlist when deciding which future Content Brain build candidates appear strongest after Manual Workflow Tests 1 to 10 and the Manual Workflow Synthesis Report.
Use Content Brain Site Content Intelligence Report Generator Specification when reviewing what the future Site Content Intelligence Report Generator may eventually need to do at a planning level.
Use Content Brain Site Intelligence Manual Test Protocol when running new Site Intelligence tests.
Use Content Brain Site Intelligence Test Log when recording Site Intelligence test evidence.
Do not use the Build Readiness Shortlist as technical build approval.
Do not use the Site Content Intelligence Report Generator Specification as technical build approval.
Do not use Site Intelligence test records as content production approval.
Do not hand any of these pages to M as implementation instructions.
Site Intelligence Rule
Before creating important new content for an existing site, Content Brain should check whether site context matters.
If site context matters, use Content Brain Site Content Intelligence Framework before creating the brief.
This protects against:
generic content
tone mismatch
duplicate content
missed internal links
missed refresh opportunities
missed repurposing opportunities
missed affiliate support gaps
missed trust gaps
disconnected SEO content
site specific content drift
Site Content Intelligence does not replace Research Brain, Search Intelligence Brain, Affiliate Brain, Compliance Brain, Data Brain, or HeadOffice.
It gives Content Brain better site context before content planning begins.
Site Intelligence Test Boundary Rule
When external pages, screenshots, URLs, pasted page copy, or competitor examples are supplied for Content Brain testing, they are test material only unless HeadOffice explicitly authorizes downstream execution.
The default output of a Site Intelligence test is:
test record
test log update
workflow evidence
routing insight
friction note
build readiness signal
The default output is not:
new content brief
article draft
SEO brief
affiliate content pack
bridge page rewrite
landing page refresh
campaign asset
M handoff
technical build instruction
Possible next workflow does not mean authorized next workflow.
This rule was added after the drift event where Content Brain Content Brief Emergency Kit And First Aid Kit Fit was incorrectly created from Site Intelligence Test 2.
Manual Workflow Evidence Rule
Before Content Brain build work begins, manual workflow evidence should be recorded.
Use Content Brain Manual Workflow Test Log to record:
test name
test path
pages used
request type
output created
result
friction found
future build evidence
recommended next action
save point
Manual workflow tests help determine whether future build candidates are real needs or only theoretical ideas.
Do not build from one test.
Look for repeated patterns.
Manual Workflow Synthesis Rule
After a meaningful block of manual tests, Content Brain should create or update a synthesis report before moving into build specifications.
A synthesis report should identify:
what has been proven manually
what has not been proven
repeated friction patterns
strongest future build candidates
what should stay manual
what should not be built yet
recommended first future build ready specification candidate
next maturity step
Manual workflow synthesis does not authorize technical build work.
It prepares cleaner judgment before future build spec work.
Build Readiness Planning Rule
After manual workflow evidence has been recorded and synthesised, Content Brain may create a build readiness planning page.
A build readiness planning page should identify:
which future build candidates are strongest
which candidates should wait
which candidates should stay manual
which candidates should not be built yet
which candidate is most likely to become the first future specification candidate
what must happen before any M handoff or technical build work
Build readiness planning does not authorize build work.
Future Specification Candidate Rule
After a build readiness planning page identifies the strongest future candidate, Content Brain may create a future specification candidate page.
A future specification candidate page should define:
purpose
current status
evidence source
why the candidate comes first
what the future system would eventually do
what the future system must not do
manual workflow evidence
primary inputs
primary outputs
source depth labels where relevant
offer evidence requirements where relevant
compliance routing needs where relevant
supported downstream workflows
human approval points
not yet build ready notice
future fields to define later
recommended next step
change impact declaration
change log
end of day save point template
final rule
A future specification candidate page is not a build specification.
A future specification candidate page is not a technical implementation instruction.
A future specification candidate page is not an M handoff pack.
Cross Brain Integration Rule
Content Brain must work with the wider MWMS ecosystem.
Use Content Brain Cross Brain Integration Map when deciding how Content Brain connects to:
HeadOffice Brain
Research Brain
Search Intelligence Brain
Affiliate Brain
Ads Brain
Experimentation Brain
Conversion Brain
Compliance Brain
Data Brain
Finance Brain
Strategy Brain
SIT Brain
Content Brain must not take authority from these Brains.
Content Brain should translate approved or review ready intelligence into structured content systems.
Future Build Readiness Rule
This registry does not authorize technical build work by itself.
The Content Brain Build Readiness Shortlist identified the current strongest first future specification candidate as:
Content Brain Site Content Intelligence Report Generator Specification
That future specification candidate has been created as:
Content Brain Site Content Intelligence Report Generator Specification
Status:
Draft Future Specification Candidate
Version:
v1.0
Parent:
Content Brain
This does not authorize build work.
It only defines the first clean planning version of what the future Site Content Intelligence Report Generator may eventually need to do.
Current strongest future specification candidate created:
Content Brain Site Content Intelligence Report Generator Specification
Reason:
The Build Readiness Shortlist confirmed Site Content Intelligence is the strongest upstream workflow because it supports content briefs, SEO briefs, affiliate product packs, refresh plans, internal linking plans, bridge page reviews, publishing readiness decisions, compliance routing, Ads Brain handoff, Affiliate Brain handoff, and broader site specific content planning.
Drift Protection
The registry must prevent:
duplicate page creation
old pages becoming active again by accident
legacy pages overriding current operational pages
unreviewed pages being used as source of truth
Content Brain becoming a random article factory
Content Brain being disconnected from other Brains
Content Brain taking authority from other Brains
new pages being created without parent discipline
new pages being created without status discipline
new pages being created without purpose
new systems being built from vague ideas
M being handed unclear build instructions
new content being created for an existing site without checking site context where needed
site specific tone and structure being ignored
manual workflow evidence being lost
manual workflow synthesis being skipped before future build spec work
operational logs being treated as build approval
operational evidence reports being treated as build approval
build readiness planning pages being treated as build approval
future specification candidate pages being treated as build approval
Site Intelligence tests being treated as downstream content authorization
test material being converted into content briefs without explicit HeadOffice approval
possible next workflows being executed automatically
shortlist pages being handed to M as technical specifications
future specification candidates being handed to M as implementation instructions
future specification candidates being confused with approved implementation work
dashboards, queues, generators, AI Employees, Supabase work, Brain Room routing, or automation being started from a shortlist or draft future specification candidate rather than a build ready technical specification
Build Readiness Shortlist being treated as a replacement for the Manual Workflow Test Log or Manual Workflow Synthesis Report
Site Content Intelligence Report Generator Specification being treated as final build approval
single tests being over interpreted as system build readiness
mwmscontentbrain.site replacing MCR as source of truth
affiliate product content packs being treated as finished publishing assets
product content pack outputs bypassing compliance review in sensitive niches
refresh outputs being treated as publishing approval without a publishing readiness check
proposed asset optimization being confused with live page refresh
internal linking being treated as SEO only and ignoring reader journey
internal links pushing product pages too aggressively before education and trust are established
affiliate bridge page refresh being treated as the same thing as a normal article refresh
ad to page match being ignored on campaign pages
source depth being ignored when reviewing external sites, VSLs, offers, or affiliate pages
offer evidence being invented
claim risk being ignored
future fields being treated as approved database fields
draft future specification candidates being treated as technical specifications
Recommended Next Actions
Immediate action:
Create this new Content Brain Page Registry page as v2.5.
Confirm the new page saves successfully.
Confirm:
Title: Content Brain Page Registry
Parent: Content Brain
Status: Published
Version in body: v2.5
Once the new v2.5 page is saved and visible, delete the old broken v2.4 Content Brain Page Registry page.
Do not delete the old page before the new v2.5 page is saved.
Do not create or retain Content Brain Content Brief Emergency Kit And First Aid Kit Fit as an active operational page.
Do not update Content Brain Canon unless governing identity or authority boundaries materially change.
Do not update Content Brain Architecture unless live structure or architectural design materially changes.
Do not update Content Brain Manual Workflow Test Log unless new test evidence is added.
Do not update Content Brain Manual Workflow Synthesis Report unless the interpretation of Tests 1 to 10 materially changes.
Do not create M handoff instructions.
Do not start plugin or UI.
Do not start Supabase.
Do not start Brain Room routing.
Do not create queues, dashboards, generators, or automations.
Do not create AI Employees.
Do not touch M’s active build work.
Recommended next working action after this registry update:
Stabilise the page list.
Confirm duplicate Site Intelligence Test Log pages.
Keep only the correct current log page after review.
Do not create new pages until registry and duplicate cleanup are stable.
Target Save Point
Content Brain — Page Registry v2.5 Recreated As Clean Live Page / Old Registry v2.4 Deleted / Drift Content Brief Excluded / Site Intelligence Operating Pages And Test Evidence Added / Manual Workflow Only / Plugin UI Not Started
Change Impact Declaration
Pages Created:
Content Brain Page Registry
Pages Replaced:
Old Content Brain Page Registry v2.4 WordPress page
Pages Updated:
None inside old v2.4 page because WordPress JSON save failed.
Pages Deleted:
Old Content Brain Page Registry v2.4 after new v2.5 page saves successfully.
Content Brain Content Brief Emergency Kit And First Aid Kit Fit should remain deleted or excluded.
Pages Renamed:
None
Registries Requiring Update:
This page is the registry update.
Canon Version Update Required:
No
Architecture Version Update Required:
No
Manual Workflow Test Log Update Required:
No
Manual Workflow Synthesis Report Update Required:
No
Plugin UI Impact:
None
Supabase Impact:
None
Brain Room Routing Impact:
None
Automation Impact:
None
Queue Impact:
None
Dashboard Impact:
None
Generator Build Impact:
None
AI Employee Impact:
None
Cross Brain Routing Impact:
None
M Active Build Impact:
None
Page Count Impact:
Current valid expected count remains 54 Content Brain pages after excluding the drift page and replacing the broken old registry page with the new v2.5 registry page.
Change Log
Version: v2.5
Date: 2026-06-08
Author: HeadOffice
Change:
Recreated Content Brain Page Registry as a clean live v2.5 WordPress page because the previous v2.4 registry page became difficult to update and triggered WordPress JSON save failure.
Added the Site Intelligence operating layer and Site Intelligence test evidence layer created during the 2026-06-08 manual workflow block.
Added the following valid pages to the registry:
Content Brain Publishing Readiness Status Values Framework
Content Brain Source Depth And Evidence Label Framework
Content Brain Offer Evidence Requirements Framework
Content Brain Compliance Routing Needs Framework
Content Brain Human Approval Points Framework
Content Brain Future Fields To Define Later Framework
Content Brain Site Content Intelligence Report Template
Content Brain Site Intelligence To Content Brief Workflow
Content Brain Site Intelligence Manual Test Protocol
Content Brain Site Intelligence Test Log
Content Brain Site Intelligence Test 1 MWMS Content Brain Site Review
Content Brain Site Intelligence Test 2 Emergency Preparedness Affiliate Support Review
Excluded the drift page:
Content Brain Content Brief Emergency Kit And First Aid Kit Fit
Reason for exclusion:
Downstream content production was not authorised.
Confirmed Content Brain remains Manual Workflow Only / Plugin UI Not Started.
Confirmed this update does not authorize plugin UI, Supabase, Brain Room routing, automation, queues, dashboards, generators, AI Employees, cross brain routing, or M implementation handoff.
End Of Day Save Point Template
Page list checked:
Yes / No
New Content Brain Page Registry v2.5 created:
Yes / No
New Content Brain Page Registry v2.5 saved successfully:
Yes / No
Old Content Brain Page Registry v2.4 deleted:
Yes / No
WordPress JSON error avoided by new page:
Yes / No
Content Brain Content Brief Emergency Kit And First Aid Kit Fit excluded or deleted:
Yes / No
Valid page count:
54 pages / other
Content Brain Site Content Intelligence Report Generator Specification confirmed as planning only:
Yes / No
Duplicate Content Brain Site Intelligence Test Log pages checked:
Yes / No
Duplicate Content Brain Site Intelligence Test Log pages resolved:
Yes / No
New pages created today:
Yes / No
Pages created today:
Content Brain Page Registry
Pages updated today:
None / other
Pages deleted today:
Old Content Brain Page Registry v2.4 if new v2.5 saved successfully
No plugin UI started:
Yes / No
No Supabase work started:
Yes / No
No Brain Room routing started:
Yes / No
No automation started:
Yes / No
No queue work started:
Yes / No
No dashboard work started:
Yes / No
No generator build started:
Yes / No
No AI Employee work started:
Yes / No
No cross brain routing started:
Yes / No
M’s active Research Brain work untouched:
Yes / No
Final Rule
Create the new v2.5 Registry page first.
Only delete the old v2.4 Registry page after the new v2.5 page is saved and visible.
Do not create new Content Brain operating pages until the Registry replacement and duplicate log cleanup are stable.
Content Brain remains Manual Workflow Only / Plugin UI Not Started.
Version: v2.6
Date: 2026-06-10
Author: HeadOffice
Change:
Updated registry status after the Site Intelligence storage direction cleanup.
Confirmed Site Intelligence Test 5 The Blog Starter Refresh Before New Content Review is retained as a temporary WordPress test record and parent corrected to Content Brain.
Confirmed Tests 1 to 5 may remain as short WordPress test records until Supabase storage exists.
Confirmed repeatable future Site Intelligence test records should not keep becoming WordPress pages by default.
Added Content Brain Site Intelligence Test Record Supabase Structure as a Draft Future Supabase Planning Specification under Content Brain.
Confirmed this new page is planning only.
Confirmed it does not authorise SQL, Supabase table creation, plugin UI, dashboards, workers, automation, Brain Room routing, AI Employees, cross brain task wiring, or M handoff.
Current save point:
Content Brain — Site Intelligence WordPress Test Page Bloat Contained / Test Log v1.6 Stable / Test Records 1 To 5 Confirmed / Test 5 Parent Corrected / Site Intelligence Test Record Supabase Structure Created As Planning Only / Supabase Build Not Started / Manual Workflow Only / Plugin UI Not Started
END CONTENT BRAIN PAGE REGISTRY v2.6