Document Type: Page Registry
Status: Active
Version: v4.0
Authority: Content Brain Canon
Applies To: All Content Brain MCR Pages, Operational Pages, Frameworks, Standards, Templates, Specifications, Workflow Pages, Production Systems, Site Intelligence Support Pages, Migration Pages And Future Plugin Or UI Candidates
Parent: Content Brain
Enforcement Mode: Structural
Last Reviewed: 2026-07-19
Content Brain Page Registry
Purpose
The Content Brain Page Registry provides the structural inventory of all known Content Brain pages, operational systems and approved supporting records.
Its purpose is to:
maintain visibility over the complete Content Brain structure
confirm which Content Brain pages exist
record each page’s document type
track correct parent placement
prevent duplicate and overlapping pages
distinguish MCR source-of-truth pages from operational working pages
support Content Brain Copy Map alignment
support controlled movement between MCR and mwmscontentbrain.site
track Content Brain production frameworks
track content planning and briefing frameworks
track editing and quality-control frameworks
track publishing-support pages
track content refresh and repurposing systems
track website, article, social, script, advertising, email, newsletter, documentation and content-pack capabilities
track Site Intelligence as a supporting Content Brain capability
track migration, operational-copy and implementation-control pages
track approved production-plugin capabilities
protect MCR as the source of truth
prevent temporary technical screens from redefining Content Brain
preserve visibility over future production interfaces without authorising premature automation
The Registry acts as the master structural inventory for Content Brain.
It records:
what exists
where it belongs
its current status
its source-of-truth position
its intended operational relationship
its possible future interface role
It does not replace:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Copy Map
structured operational records stored in Supabase
The Content Brain Copy Map controls movement and destination classification.
The Content Brain Canon controls authority.
The Content Brain Architecture controls system structure.
The Content Brain Operating Model controls practical operation.
The Content Brain Workflow Map controls movement of work.
Scope
This Registry applies to:
Content Brain core pages
Content Brain Canon pages
Content Brain Architecture pages
Content Brain operating models
Content Brain workflow maps
Content Brain system maps
Content Brain production frameworks
Content Brain planning frameworks
Content Brain briefing standards and templates
Content Brain editing frameworks
Content Brain quality-control frameworks
Content Brain publishing-readiness pages
Content Brain content lifecycle frameworks
Content Brain refresh frameworks
Content Brain repurposing frameworks
Content Brain internal-linking frameworks
Content Brain authority and trust frameworks
Content Brain website-content systems
Content Brain article-production systems
Content Brain social-content systems
Content Brain script-production systems
Content Brain advertising-content systems
Content Brain newsletter and email systems
Content Brain manual, guide and documentation systems
Content Brain content-pack frameworks
Content Brain affiliate-support frameworks
Content Brain Site Intelligence support pages
Content Brain operational pages
Content Brain operational-copy pages
Content Brain standards
Content Brain templates
Content Brain checklists
Content Brain specifications
Content Brain queue specifications
Content Brain dashboard specifications
Content Brain migration plans
Content Brain migration reviews
Content Brain migration-execution control pages
Content Brain operational-layer build pages
Content Brain production-plugin screens
Content Brain future plugin or UI candidates
Content Brain review-later pages
This Registry records both source-of-truth and operationally related pages.
It must distinguish between:
MCR authority
MCR structural documentation
operational copies on mwmscontentbrain.site
plugin screens
Supabase records
temporary test records
future interface candidates
future automation candidates
The Registry must never treat all of these as the same layer.
Authority Boundary
The Registry records structure.
It does not create authority.
Authority is defined by:
Content Brain Canon
HeadOffice governance
MWMS Architecture Registry
MWMS Brain Interaction Protocol
MWMS MCR classification and storage rules
approved Content Brain frameworks and standards
The Registry does not authorise:
content generation
publishing automation
worker execution
queue execution
Brain Room routing
AI Employee activation
M handoff
Research Brain changes
cross-Brain automation
No capability is authorised merely because it appears as a future candidate in this Registry.
Core Content Brain Pages
Page Title: Content Brain
Document Type: Brain Landing Page
Parent Page: Brains
Status: Active
Migration Classification: MCR Source Of Truth
Plugin Or UI Candidate: Future Main Content Brain Home
Notes: Defines the Content Brain as the MWMS system responsible for controlled content planning, production, editing, approval, publishing preparation and lifecycle management.
Page Title: Content Brain Canon
Document Type: Canon
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: No
Notes: Defines Content Brain authority, boundaries, responsibilities and non-authorised capabilities.
Page Title: Content Brain Architecture
Document Type: Architecture
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: No Direct UI
Notes: Defines the complete Content Brain architecture from request and qualification through project definition, asset planning, intelligence assembly, briefing, production, editing, specialist review, human approval, publishing preparation, delivery, measurement and lifecycle management.
Page Title: Content Brain Operating Model
Document Type: Operating Model
Version: v1.2
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: Possible Operating Reference UI Later
Notes: Defines how the human-controlled Content Brain workflow operates.
Page Title: Content Brain Workflow Map
Document Type: Workflow Map
Version: v1.2
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: Possible Workflow Interface Later
Notes: Defines movement and decision branches for Content Brain work.
Page Title: Content Brain Page Registry
Document Type: Page Registry
Version: v3.9
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: Possible Registry Dashboard Much Later
Notes: Master structural inventory for Content Brain. It does not replace the Content Brain Copy Map.
Page Title: Content Brain Copy Map
Document Type: Copy Map
Version: v2.9
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: Possible Copy-Control Dashboard Much Later
Notes: Controls page movement, operational-copy classification and destination alignment between MCR and mwmscontentbrain.site.
Core Production And Planning Pages
Page Title: Content Brain Content Production System Framework
Document Type: Framework
Version: v1.1
Parent Page: Content Brain Canon
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Yes
Notes: Defines the controlled content-production system.
Page Title: Content Brain Content Brief Template
Document Type: Template
Version: v1.2
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Content Brief Workspace
Notes: Master MCR content-brief template.
Page Title: Content Brain SEO Content Brief Standard
Document Type: Standard
Version: v2.1
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible SEO Brief Interface Later
Notes: Defines SEO briefing requirements without replacing the general Content Brain brief structure.
Page Title: Content Brain Publishing Readiness Checklist
Document Type: Checklist
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Publishing Readiness Interface
Notes: Supports human-controlled publishing-readiness review.
Page Title: Content Brain Affiliate Funnel Support Map
Document Type: Support Map
Version: v1.2
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Affiliate Support Content Planner Later
Notes: Maps content assets across affiliate funnel stages.
Page Title: Content Brain Affiliate Product Content Pack Framework
Document Type: Framework
Version: v1.1
Parent Page: Content Brain Canon
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Affiliate Content Pack Generator Later
Notes: Defines coordinated affiliate content packs.
Page Title: Content Brain Affiliate Product Content Pack Checklist
Document Type: Checklist
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Checklist UI Later
Notes: Supports manual readiness review for affiliate product content packs.
Newsletter, Email And Deliverability Pages
Page Title: MWMS Newsletter Content Production Framework
Document Type: Framework
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Newsletter And Campaign Production Workspace Later
Notes: Defines human-controlled newsletter and scheduled email campaign production, including source review, campaign role, audience and segment definition, subject line and preview text governance, copy hierarchy, modular email sections, design direction, mobile readability, campaign calendars, lifecycle conflict review, communication-pressure review, approval and performance feedback. This page owns newsletter and campaign content production. It does not own behavioural lifecycle-flow architecture or sender infrastructure.
Page Title: MWMS Email Deliverability And Sender Reputation Governance Framework
Document Type: Framework
Version: v1.0
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Deliverability Monitoring And Incident Workspace Later
Notes: Defines sender identity, authentication governance, permission quality, list hygiene, engagement quality, communication pressure, bounce and complaint handling, reputation monitoring, deliverability incidents, remediation, revalidation and human change control across newsletters, campaigns, lifecycle and transactional email. This page is a cross-Brain dependency for Ecommerce Brain, Data Brain, Compliance Brain, Infrastructure Brain and Automation Brain.
Newsletter And Email Ownership Boundary
Content Brain owns:
newsletter production
scheduled campaign email production
subject lines
preview text
email copy hierarchy
message hierarchy
modular email sections
design direction
mobile readability
campaign calendars
editorial approval
publishing-readiness review
performance interpretation
Ecommerce Brain owns:
behavioural lifecycle messaging
flow triggers
flow entry and exclusion
sequence logic
timing
branching
exit conditions
suppression
customer-state relevance
email and SMS list-growth architecture
capture mechanisms
signup-source preservation
subscriber quality
segment-entry readiness
MWMS Email Deliverability And Sender Reputation Governance Framework owns:
sender identity
domain authentication governance
consent and permission quality
list hygiene
bounce handling
complaint handling
unsubscribe handling
sender reputation
inbox-placement confidence
deliverability incidents
remediation
revalidation
Duplicate Page Decision
The following standalone pages were reviewed and deliberately not created:
Newsletter Brain Email Copy And Message Architecture Framework
Reason: Its durable copy, subject-line, preview-text, opening, proof, CTA and message-hierarchy intelligence is already governed by MWMS Newsletter Content Production Framework v1.1.
Newsletter Brain Email Design And Modular Content Framework
Reason: Its durable section architecture, visual hierarchy, mobile readability, image independence and design-simplicity intelligence is already governed by MWMS Newsletter Content Production Framework v1.1.
These decisions prevent duplicate Canon and fragmented ownership.
Operational Copy Register
Page Title: Content Brain Home Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Operational Copy On mwmscontentbrain.site
Plugin Or UI Candidate: Possible Content Brain Home Later
Notes: Current operational homepage copy on mwmscontentbrain.site. MCR remains the controlling source of truth.
Page Title: Content Brain Workflow Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Operational Copy On mwmscontentbrain.site
Plugin Or UI Candidate: Possible Workflow Interface Later
Notes: Current operational workflow copy on mwmscontentbrain.site. Content Brain Workflow Map remains the controlling MCR source of truth.
Page Title: Content Brain Content Brief Template Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Operational Copy On mwmscontentbrain.site
Plugin Or UI Candidate: Possible Content Brief Generator Later
Notes: Current operational brief-template copy on mwmscontentbrain.site. Content Brain Content Brief Template remains the controlling MCR source of truth.
Page Title: Content Brain Publishing Readiness Checklist Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Operational Copy On mwmscontentbrain.site
Plugin Or UI Candidate: Possible Publishing Readiness Checklist UI Later
Notes: Current operational publishing-readiness copy on mwmscontentbrain.site. Content Brain Publishing Readiness Checklist remains the controlling MCR source of truth.
Page Title: Content Brain Affiliate Product Content Pack Checklist Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Operational Copy On mwmscontentbrain.site
Plugin Or UI Candidate: Possible Affiliate Product Content Pack Checklist UI Later
Notes: Current operational affiliate product content-pack checklist on mwmscontentbrain.site. The MCR checklist remains the controlling source of truth.
Page Title: Content Brain Affiliate Funnel Support Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: Operational Copy On mwmscontentbrain.site
Plugin Or UI Candidate: Possible Affiliate Support Content Planner Later
Notes: Current operational affiliate funnel-support copy on mwmscontentbrain.site. The MCR support framework and map remain the controlling source of truth.
Site Intelligence Position
Site Intelligence remains a supporting Content Brain capability.
It does not define the complete Content Brain production architecture.
Site Intelligence Tests 1 to 5 remain preserved.
Site Intelligence Records UI version: v0.4.1
Status: Stable
Permanent deletion: Not available
Main list actions: View and Edit
Archive action: Available only through controlled individual-record editing
Further Site Intelligence expansion authorised: No
Site Intelligence changed during Content Production v0.7.8 validation: No
Content Production Operational Layer
The Content Brain Production plugin is a separate operational plugin from the Site Intelligence Records plugin.
Its purpose is to support human-controlled:
content projects
selected content streams
manual content briefs
brief approval
manual content workspaces
draft content storage
revision-note storage
final-approved content snapshots
production-stage movement
editing-stage movement
review-stage movement
final human approval
publishing-readiness decisions
manual publication recording
publishing hold decisions
publishing-decision resumption
project progress roll-up
project completion
completed-record protection
archived-record protection
It does not generate content.
It does not publish content.
It does not run autonomous workflows.
It does not activate workers.
It does not route work through Brain Rooms.
It does not hand work to M.
Content Production Plugin Current Confirmed State
Plugin Name: MWMS Content Brain Production
Production Plugin Version: v0.7.8
Internal Version Constant: v0.7.8
Status: Active
Storage Layer: Supabase
Project Table: content_brain_projects
Stream Table: content_brain_assets
Brief Table: content_brain_briefs
Content Record Table: content_brain_content_records
Workflow Control: Human Controlled
Publishing Control: Human Controlled
Delete Control: Not Available
Archive And Restore: Available For Projects And Streams
Completed Project Editing: Locked
Archived Project Editing: Locked
Completed Stream Editing: Locked
Archived Stream Editing: Locked
Completed Stream Brief Editing: Locked
Archived Stream Brief Editing: Locked
Direct Edit URL Access For Locked Records: Blocked
Direct Update Submission For Locked Records: Blocked Server-Side
Adding Streams To Completed Projects: Blocked
Adding Streams To Archived Projects: Blocked
Content generation: Not Started
Automation: Not Started
Publishing automation: Not Started
Worker execution: Not Started
Brain Room routing: Not Started
M handoff: Not Started
Manual Content Workspace Current Confirmed State
Manual Content Workspace: Implemented And Validated
Existing Content Records: 2
Validated Project: Content Brain Production Test 3
Validated Stream: Content Brain Test Article Series
Approved Brief Linkage: Preserved
Working Title Storage: Confirmed
Draft Content Storage: Confirmed
Draft Content Editing: Confirmed
Revision Notes Storage: Confirmed
Final Approved Content Storage: Confirmed
Final Approved Content Storage Position: Separate Approved Snapshot
Human Owner Storage: Confirmed
Created Timestamp Storage: Confirmed
Updated Timestamp Storage: Confirmed
Content Status Storage: Confirmed
Current Validated Content Status: Final Approved
Current Validated Version Number: 9
Duplicate Content Record Created: No
Manual Content Workspace Validation
The existing content record was used for all validation.
No second content record was created.
The original five-paragraph Draft Content remained preserved.
A sixth controlled paragraph was added successfully to Draft Content.
The new paragraph appeared in WordPress after saving.
The new paragraph was stored through the Supabase draft_content field.
Revision Notes saved correctly during the controlled Draft Content edit.
Working Title remained unchanged.
Linked Project remained unchanged.
Linked Content Stream remained unchanged.
Approved Brief remained unchanged.
No unrelated stream changed.
No automatic workflow-stage change occurred.
No automatic approval occurred.
No automatic publishing occurred.
Version Number increased once for the successful Draft Content change.
Updated Date advanced correctly for the meaningful change.
No Change Save Protection
A save was completed without changing any meaningful content field.
Confirmed:
Version Number did not increase.
Draft Content remained unchanged.
Revision Notes remained unchanged.
Final Approved Content remained unchanged.
Content Status remained unchanged.
Updated Date did not advance.
No duplicate content record was created.
No workflow field changed.
Meaningful Content Version Handling
The following fields are treated as meaningful content fields:
Working Title
Draft Content
Revision Notes
Final Approved Content
Content Status
Version Number increases only when at least one meaningful content field changes.
Version Number does not increase when:
the submitted content is identical to the stored content
the save request contains no actual change
only an Updated Date would otherwise change
Final Approved Content Snapshot Validation
The original manual copy-and-paste design was rejected as inefficient.
Content Brain Production Plugin v0.7.8 preserves the replacement of the editable Final Approved Content box with a human-controlled action:
Approve Current Draft As Final Content
The action:
copies the complete current Draft Content into Final Approved Content
stores Final Approved Content separately from Draft Content
preserves Draft Content
changes Content Status to Final Approved
records the final approval Revision Notes
increases Version Number once
updates Updated Date once
does not change the linked stream stage
does not change stream Final Approval Status
does not mark Publishing Readiness as Ready
does not record publication
does not publish content
The Current Final Approved Content is displayed as view-only within the editing workspace.
The approved snapshot remains visible without requiring repeated manual copy and paste.
Final Approval Separation Validation
Content Workspace status and stream workflow approval remain separate controls.
After the content snapshot was approved:
Content Status became Final Approved.
The selected stream Current Stage remained Request.
The selected stream Final Approval Status remained Human Approval Required.
The selected stream Publishing Readiness remained Not Ready.
The selected stream Production Status remained Not Started.
The selected stream Editing Status remained Not Started.
The selected stream Review Status remained Not Started.
The Content Workspace remained Created.
This confirms:
Final Approved content does not equal stream final approval.
Stream final approval does not occur automatically.
Final Approved content does not equal Publishing Ready.
Final Approved content does not equal Published.
Publishing remains a separate human-controlled decision.
First Real Affiliate Content Workflow Validation
The first real end-to-end affiliate content job was completed using BeatBuds Pro UK.
Project: BeatBuds Pro UK Affiliate Content Project
Stream: BeatBuds Pro UK Review Article
Subtype: Review Article
Quantity: 1
Brief: BeatBuds Pro UK Review Article Brief
Content Workspace: Created
Final Content Status: Final Approved
Final Content Version Number: 5
Final Stream Stage: Publishing Readiness
Final Stream Status: On Hold
Final Approval Status: Approved
Publishing Readiness: Ready
Publication Recorded: No
The following human-controlled workflow actions were validated:
Start Production
Move To Editing
Move To Review
Complete Review
Approve Current Draft As Final Content
Approve Content Stream
Mark Publishing Ready
Place On Hold
Resume Publishing Decision
Place On Hold again after resume validation
Confirmed workflow movement:
Request to Production
Production to Editing
Editing to Review
Review to Approval
Approval to Publishing Readiness
Confirmed status movement:
Production Status moved from Not Started to In Progress to Completed.
Editing Status moved from Not Started to In Progress to Completed.
Review Status moved from Not Started to In Progress to Completed.
Final Approval Status moved from Human Approval Required to Approved only after separate human action.
Publishing Readiness moved from Not Ready to Ready only after separate human action.
The publishing hold changed stream Status to On Hold without removing Publishing Readiness.
Resume Publishing Decision returned stream Status to Active without recording publication.
The stream was then returned to On Hold because the article had not been published on a real destination.
Confirmed boundaries:
The content snapshot did not automatically approve the stream.
Stream approval did not automatically mark Publishing Readiness.
Publishing Readiness did not automatically publish the article.
Place On Hold did not remove the approved content snapshot.
Resume Publishing Decision did not alter production, editing, review or approval completion.
No automatic publication occurred.
No false published state was recorded.
Production Summary After Validation
Active Projects: 2
Selected Stream Records: 6
Manual Content Briefs: 5
Content Records: 2
Awaiting Brief Approval: 1
Awaiting Final Approval: 2
Publishing Ready: 1
Archived Records: 2
Confirmed Production Capabilities
The following production capabilities are confirmed:
content project creation
single selected-stream creation
multiple selected-stream creation
project and stream viewing
active project and stream safe editing
project and stream archiving
project and stream restoration
project-to-stream linkage
Supabase project persistence
Supabase stream persistence
adding a content stream to an existing active project
manual content-brief creation
one manual brief linked to one content stream
brief-to-stream status synchronisation
separate brief approval and final approval
manual Content Workspace creation
one Content Workspace linked to one selected stream
working-title storage
Draft Content storage
Draft Content editing
Revision Notes storage
meaningful-change version handling
no-change save protection
Final Approved Content snapshot storage
view-only approved-content display
human-controlled Approve Current Draft As Final Content action
Draft Content preservation after final approval
human-controlled content-status changes
human-controlled Start Production action
human-controlled Move To Editing action
human-controlled Move To Review action
human-controlled Complete Review action
human-controlled final stream approval
human-controlled publishing-readiness decision
human-controlled Return To Not Ready decision
human-controlled Place On Hold decision
human-controlled Resume Publishing Decision action
human-controlled manual-publication recording
project progress roll-up
project-stage roll-up synchronisation
human-controlled Complete Project action
project completion without altering linked streams
single-use final approval decision controls
server-side prevention of repeat final approval decisions
final approval controls hidden after a final decision is recorded
Mark Publishing Ready shown only after approved final stream decision
publishing decision controls shown only while publishing readiness is Ready
publishing decision controls removed after manual publication is recorded
completed project edit-button removal
completed stream edit-button removal
completed linked-brief edit-button removal
archived project edit-button removal
archived stream edit-button removal
archived linked-brief edit-button removal
direct completed-project edit-page blocking
direct completed-stream edit-page blocking
direct completed linked-brief edit-page blocking
direct archived-project edit-page blocking
direct archived-stream edit-page blocking
direct archived linked-brief edit-page blocking
server-side completed-project update blocking
server-side completed-stream update blocking
server-side completed linked-brief update blocking
server-side archived-project update blocking
server-side archived-stream update blocking
server-side archived linked-brief update blocking
Production Record Protection
Completed records remain viewable.
Completed records remain locked from editing.
Archived records remain preserved.
Archived records remain locked until restoration where restoration is permitted.
Completed and archived projects cannot receive additional streams.
Active project and stream editing remains available.
No permanent deletion control exists.
Future Plugin Or UI Candidate Register
Candidate: Content Project Workspace
Source Pages: Content Brain Architecture, Content Brain Operating Model And Content Brain Workflow Map
Priority: Partially Implemented
Status: Active Human-Controlled Production Plugin
Notes: Current project and linked-stream functions are implemented in the separate Content Production plugin.
Candidate: Asset Planning Workspace
Source Pages: Content Brain Architecture And Content Brain Operating Model
Priority: Later
Status: Future Plugin Or UI
Notes: May later define required assets, relationships, channels, sources and approval needs.
Candidate: Manual Content Brief Workspace
Source Pages: Content Brain Content Brief Template And Content Brain Operating Model
Priority: Implemented Initial Version
Status: Active Human-Controlled Production Plugin
Notes: Manual content briefs can be created, edited, approved and linked to individual streams while the linked stream remains open.
Candidate: Manual Content Workspace
Source Pages: Content Brain Content Production System Framework, Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Stores Working Title, Draft Content, Revision Notes, Final Approved Content, Content Status, version data, ownership and timestamps in Supabase while preserving separate project, stream, brief, approval and publishing controls.
Candidate: Current Draft Approval Snapshot
Source Pages: Content Brain Content Production System Framework And Content Brain Publishing Readiness Checklist
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Approve Current Draft As Final Content copies the current draft into a separate approved snapshot without changing stream stage, stream approval, publishing readiness or publication.
Candidate: Meaningful Content Version Handling
Source Pages: Content Brain Content Production System Framework
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Version Number and Updated Date change only when Working Title, Draft Content, Revision Notes, Final Approved Content or Content Status meaningfully changes.
Candidate: Human-Controlled Production Workflow
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented Initial Version
Status: Active Human-Controlled Production Plugin
Notes: Production, editing, review, approval, publishing readiness and manual publication recording are confirmed.
Candidate: Final Approval Decision Lock
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Final approval controls are available only while Final Approval Status is Human Approval Required. After one final decision, the controls disappear and repeat submission is blocked server-side.
Candidate: Completed-Record Edit Lock
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Completed projects, completed streams and briefs linked to completed streams are viewable but cannot be edited through buttons, direct edit URLs or direct update submissions.
Candidate: Archived-Record Edit Lock
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Archived projects, archived streams and briefs linked to archived streams are viewable or restorable where applicable but cannot be edited before restoration.
Candidate: Human-Controlled Publishing Decision Branches
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented And Validated
Status: Active Human-Controlled Production Plugin
Notes: Return To Not Ready, Place On Hold, Resume Publishing Decision and Record Published Manually are confirmed without automatic publishing.
Candidate: Project Progress Roll-Up
Source Pages: Content Brain Architecture And Content Brain Workflow Map
Priority: Implemented Initial Version
Status: Active Human-Controlled Production Plugin
Notes: Project progress is calculated from linked streams.
Candidate: Synchronise Project Progress
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented Initial Version
Status: Active Human-Controlled Production Plugin
Notes: Human-controlled action updates only the project Current Stage and Next Action from linked streams.
Candidate: Complete Project
Source Pages: Content Brain Operating Model And Content Brain Workflow Map
Priority: Implemented Initial Version
Status: Active Human-Controlled Production Plugin
Notes: Human-controlled action completes an eligible project without changing, archiving or deleting linked streams.
Candidate: Site Intelligence Records Screen
Source Pages: Content Brain Site Intelligence Records Screen Specification
Priority: Supporting Capability
Status: Stable Supporting Plugin
Notes: Must remain separate from the main Content Production workspace.
Candidate: Content Generation
Priority: Not Authorised
Status: Not Started
Notes: Must not begin without an approved later change.
Candidate: Publishing Automation
Priority: Not Authorised
Status: Not Started
Notes: The current system records human publishing decisions only.
Candidate: Worker Execution
Priority: Not Authorised
Status: Not Started
Notes: No worker exists.
Candidate: Brain Room Routing
Priority: Not Authorised
Status: Not Started
Notes: No Brain Room routing exists.
Candidate: M Handoff
Priority: Not Authorised
Status: Not Started
Notes: No automatic or manual implementation handoff to M has been started for the Content Brain Production plugin.
Operating Layer Boundaries
MCR
MCR contains:
Canon
architecture
operating models
workflow maps
governance
master frameworks
master templates
master specifications
source-of-truth rules
approved registries
migration controls
The Content Brain Site
The Content Brain site contains:
operational working pages
manual workflows
plugin screens
implementation pages
working copies
approved operator tools
supporting test interfaces
A Content Brain site-only page is operational unless deliberately approved and copied into MCR.
Supabase
Supabase contains:
repeatable records
content requests
projects
asset records
brief records
content records
Draft Content
Revision Notes
Final Approved Content snapshots
version data
ownership data
created and updated timestamps
source relationships
evidence relationships
production status
editing status
review status
approval status
publishing status
destination status
Current Operating Status
Content Brain Page Registry v4.0 active once this replacement is published.
Content Brain Copy Map v2.9 active.
MCR remains the source of truth.
The Content Brain site remains the operational environment.
Supabase remains the structured records layer.
Site Intelligence Tests 1 to 5 remain preserved.
Site Intelligence Records UI v0.4.1 remains stable.
Content Brain Production Plugin v0.7.8 is active.
The plugin header version and internal version constant are aligned at v0.7.8.
The Manual Content Workspace is implemented and validated.
The content_brain_content_records table is active.
Two content records are stored, including the first real affiliate production record.
The original validation record remains linked to Content Brain Production Test 3 and Content Brain Test Article Series.
The real production record is linked to BeatBuds Pro UK Affiliate Content Project and BeatBuds Pro UK Review Article.
The BeatBuds Pro UK Review Article Brief remains linked and approved.
The BeatBuds Pro content record reached Final Approved status and version 5.
The BeatBuds Pro stream reached Publishing Readiness with Publishing Readiness set to Ready.
The BeatBuds Pro stream is On Hold pending a real manual publishing destination.
No publication was recorded.
Draft Content editing is validated.
Revision Notes storage is validated.
No-change save protection is validated.
Meaningful-change version handling is validated.
Final Approved Content is stored separately.
Draft Content is preserved after final approval.
Approve Current Draft As Final Content is validated.
Content Status is human controlled.
Content Workspace final approval does not automatically approve the stream.
Content Workspace final approval does not mark Publishing Readiness.
Content Workspace final approval does not publish content.
Completed records remain locked.
Archived records remain preserved.
No Site Intelligence change occurred.
No permanent deletion occurred.
No content generation was started.
No automation was started.
No publishing automation was started.
No worker work was started.
No Brain Room routing was started.
No M handoff was started.
Safe Working Boundary
The next Content Brain Production work must remain human controlled.
Do not begin AI content generation without a separately approved implementation step.
Do not begin publishing automation.
Do not create workers.
Do not activate Brain Room routing.
Do not begin M handoff.
Do not merge Site Intelligence into the main production workspace.
Do not treat Content Workspace Final Approved status as stream Final Approval Status.
Do not treat stream Final Approval Status as Publishing Readiness.
Do not treat Publishing Readiness as publication.
Do not remove the separate Draft Content and Final Approved Content storage positions.
Do not restore manual copy-and-paste as the standard approval workflow.
Do not create duplicate Content Workspace records for the same selected stream.
Do not add new WordPress pages for individual content records.
Architectural Drift Protection
The following distinctions must remain protected:
MCR source of truth versus operational Content Brain pages
Content Brain Production plugin versus Site Intelligence Records plugin
project records versus stream records
stream records versus brief records
brief records versus content records
Draft Content versus Final Approved Content
Content Workspace content status versus stream workflow stage
Content Workspace Final Approved status versus stream Final Approval Status
stream Final Approval Status versus Publishing Readiness
Publishing Readiness versus publication
manual production controls versus automation
human-controlled approval versus automatic approval
human-controlled publishing decisions versus publishing automation
operational records versus permanent MCR pages
repeatable Supabase records versus WordPress page growth
Change Log
Version: v4.0
Date: 2026-07-19
Author: HeadOffice
Change: Updated the Content Brain Page Registry after controlled absorption of durable newsletter production, campaign email, email design and deliverability intelligence from Sam Piliero The Facebook Ads Blueprint bonus Email Marketing module by Max Sturtevant.
Change Impact Declaration
Pages Created:
MWMS Email Deliverability And Sender Reputation Governance Framework v1.0.
Pages Updated:
MWMS Newsletter Content Production Framework from v1.0 to v1.1.
Content Brain Page Registry from v3.9 to v4.0.
Pages Deprecated:
None.
Standalone Pages Not Created:
Newsletter Brain Email Copy And Message Architecture Framework was not created because its durable intelligence is already governed by MWMS Newsletter Content Production Framework v1.1.
Newsletter Brain Email Design And Modular Content Framework was not created because its durable intelligence is already governed by MWMS Newsletter Content Production Framework v1.1.
Registries Requiring Update:
Content Brain Page Registry.
Content Brain Copy Map requires update because one new Content Brain framework was created and the newsletter framework version and scope changed.
MWMS Architecture Registry.
MCR Page Registry.
MCR Copy Map.
MWMS Course Absorption Decision Registry.
Canon Version Update Required:
No.
System Map Update Required:
Yes.
Review:
Content Brain System Map.
Ecommerce Brain lifecycle messaging relationship.
Ecommerce Brain list-growth relationship.
Data Brain relationship.
Compliance Brain relationship.
Infrastructure Brain relationship.
Automation Brain relationship.
Change Log Entry Required:
Yes.
Strategic Absorption Result:
Content Brain now has explicit governance for both reader-facing newsletter and scheduled campaign production and the separate deliverability and sender-reputation control layer.
MWMS Newsletter Content Production Framework v1.1 now governs:
campaign-role definition
campaign calendars
campaign and lifecycle separation
audience and segment suitability
subject line and preview text pairing
copy and message hierarchy
proof and CTA structure
email section architecture
visual hierarchy
mobile readability
frequency-pressure review
lifecycle-conflict review
human-controlled sending
performance interpretation beyond open rate
MWMS Email Deliverability And Sender Reputation Governance Framework v1.0 now governs:
sender identity
SPF, DKIM and DMARC governance
permission and consent quality
list hygiene
engagement quality
communication pressure
content integrity
sending behaviour
bounce and complaint handling
unsubscribe handling
reputation monitoring
deliverability incidents
remediation
revalidation
economic interpretation
human change control
Confirmed Boundaries:
Newsletter and campaign content production remains owned by Content Brain.
Behavioural lifecycle-flow architecture remains owned by Ecommerce Brain.
Email and SMS list-growth architecture remains owned by Ecommerce Brain.
Technical implementation remains outside this registry and requires separate authorisation.
No autonomous sending was authorised.
No provider-specific Klaviyo, Figma or DNS procedures were absorbed as permanent Canon.
No separate Email Copy framework was created.
No separate Email Design framework was created.
No Content Brain Canon version increase is required.
Version: v3.9
Date: 2026-06-23
Author: HeadOffice
Change: Updated the Content Brain Page Registry after full controlled validation of Content Brain Production Plugin v0.7.8 and completion of the first real affiliate content workflow through publishing readiness.
Change Impact Declaration
Pages Created:
None.
Pages Updated:
Content Brain Page Registry only.
Pages Deprecated:
None.
Standalone Pages Not Created:
No standalone WordPress page was created for the BeatBuds Pro project, stream, brief, content record, Draft Content or Final Approved Content.
Registries Requiring Update:
Content Brain Page Registry only.
Content Brain Copy Map remains v2.9 and does not require replacement because no page movement, destination or classification changed.
Canon Version Update Required:
No.
Change Log Entry Required:
Yes. This v3.9 entry records the first real affiliate content workflow, the production-stage controls added through v0.7.8 and the validated publishing hold and resume boundary.
Strategic Absorption Result:
Content Brain can now carry one real affiliate content job from approved brief through Draft Content, production, editing, review, Final Approved Content, separate stream approval and publishing readiness while preserving human control at every decision point.
The real BeatBuds Pro article remains On Hold pending a genuine manual publishing destination and has not been falsely recorded as published.
Confirmed:
Content Brain Production Plugin advanced from v0.7.4 to v0.7.8.
Start Production implemented and validated.
Move To Editing implemented and validated.
Move To Review implemented and validated.
Complete Review implemented and validated.
Final Approval Workflow implemented and validated.
Approve Current Draft As Final Content validated on real content.
Separate Approve Content Stream decision validated.
Publishing Readiness Workflow implemented and validated.
Mark Publishing Ready validated.
Publishing Decision Workflow implemented and validated.
Place On Hold validated.
Resume Publishing Decision validated.
The stream returned to On Hold after resume testing.
Two content records are stored.
The BeatBuds Pro content record is Final Approved at version 5.
The BeatBuds Pro stream is Final Approval Approved and Publishing Ready.
The BeatBuds Pro stream remains On Hold.
No automatic content generation occurred.
No automatic approval occurred.
No automatic publication occurred.
No worker work was started.
No Brain Room routing was started.
No M handoff was started.
Version: v3.8
Date: 2026-06-23
Author: HeadOffice
Change: Updated the Content Brain Page Registry after implementation, correction and full controlled validation of the Manual Content Workspace and the Content Brain Production Plugin v0.7.4.
Change Impact Declaration
Pages Created:
None.
Pages Updated:
Content Brain Page Registry only.
Pages Deprecated:
None.
Standalone Pages Not Created:
No standalone WordPress page was created for the Manual Content Workspace.
No standalone WordPress page was created for the content record.
No standalone WordPress page was created for Draft Content.
No standalone WordPress page was created for Final Approved Content.
Registries Requiring Update:
Content Brain Page Registry only.
Content Brain Copy Map remains v2.9 and does not require replacement because no page movement, destination or classification changed.
Canon Version Update Required:
No.
Change Log Entry Required:
Yes. This v3.8 entry records the Manual Content Workspace implementation, repair, workflow correction and validation.
Strategic Absorption Result:
The Content Brain Production operational layer can now store, edit, version and approve actual content without collapsing content storage into the brief, stream approval or publishing workflow.
The validated Manual Content Workspace preserves the working draft, stores a separate approved snapshot, prevents false version increases and keeps all workflow, approval and publishing decisions under separate human control.
Confirmed:
Content Brain Production Plugin updated beyond v0.7.2 to v0.7.4.
Draft Content editing defect fixed.
Draft Content edits stored correctly.
Revision Notes stored correctly.
False version increases prevented.
No-change saves preserve Version Number and Updated Date.
Meaningful-change version handling confirmed.
Final Approved Content stored separately.
Draft Content preserved after final approval.
Manual copy-and-paste approval workflow replaced.
Approve Current Draft As Final Content action implemented and validated.
Content Status changed only through human action.
Content record linked to the correct project.
Content record linked to the correct stream.
Approved brief remained unchanged.
No duplicate content record was created.
No unrelated stream changed.
No automatic workflow change occurred.
No automatic stream approval occurred.
No automatic publishing occurred.
Publishing Readiness remained Not Ready.
Current Stage remained Request.
Completed records remained locked.
Archived records remained preserved.
Site Intelligence was not changed.
No permanent deletion was made.
No AI generation was started.
No automation was started.
No publishing automation was started.
No worker work was started.
No Brain Room routing was started.
No M handoff was started.
Version: v3.7
Date: 2026-06-19
Author: HeadOffice
Change: Updated the Content Brain Page Registry after completed-record protection correction and validation of the active-record editing boundary.
Version: v3.6
Date: 2026-06-19
Author: HeadOffice
Change: Updated the Content Brain Page Registry after correction and full controlled validation of the Content Brain Production final approval decision lock and the complete Content Brain Production Test 4 workflow.
Version: v3.5
Date: 2026-06-19
Author: HeadOffice
Change: Updated the Content Brain Page Registry after completion and validation of the remaining Content Brain Production Test 1 article stream and the full Test 1 project-completion path.
Version: v3.0
Date: 2026-06-08
Author: HeadOffice
Change: Updated the Content Brain Page Registry following registry stabilisation, Site Intelligence operating-layer work, manual workflow testing, short-log reconstruction and duplicate cleanup.
Version: v2.9
Date: 2026-05-28
Author: HeadOffice
Change: Added the Content Brain Workflow Operational Copy and related operational-copy alignment.
Version: v2.8
Date: 2026-05-27
Author: HeadOffice
Change: Updated the operational migration and first operational-layer build position.
Version: v2.7
Date: 2026-05-26
Author: HeadOffice
Change: Updated operational-copy classifications and controlled migration records.
Version: v2.6
Date: 2026-05-25
Author: HeadOffice
Change: Updated Content Brain migration classifications and supporting operational-page records.
Version: v2.5
Date: 2026-05-25
Author: HeadOffice
Change: Stabilised the Content Brain Registry and excluded the unapproved Drift Content Brief.
Version: v2.0
Date: 2026-05-24
Author: HeadOffice
Change: Expanded the Registry to include operational migration, copy-control and readiness records.
Version: v1.0
Date: 2026-04-11
Author: HeadOffice
Change: Initial creation of the Content Brain Page Registry.
END OF FULL FILE OUTPUT