Document Type: Specification
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Future Content Brain operational dashboard planning, production queue visibility, refresh queue visibility, repurposing queue visibility, publishing readiness visibility, content bottleneck review, future mwmscontentbrain.site operational use, and future Content Brain plugin or UI planning
Parent: Content Brain
Last Reviewed: 2026-05-06
Purpose
The Content Brain Content Operations Dashboard Specification defines the future dashboard structure used to view and manage Content Brain operational activity.
This dashboard will eventually provide one control surface for:
content production work
content refresh work
content repurposing work
publishing readiness status
blocked content tasks
high-priority content tasks
content review requirements
content handoff status
content risk visibility
content signal feedback needs
future Content Brain operational performance
The dashboard exists to prevent Content Brain work from becoming scattered across separate pages, templates, queues, notes, and manual memory.
This page is a planning specification only.
It does not activate a plugin, create a database table, build a screen, or interfere with M’s current build work.
Scope
This specification applies to:
future Content Brain dashboard design
future mwmscontentbrain.site operational planning
content production visibility
content refresh visibility
content repurposing visibility
content approval visibility
content risk visibility
content bottleneck visibility
content handoff visibility
content operational status review
future plugin or UI planning
This specification does not govern:
live plugin development
Supabase implementation
Brain-to-Brain request automation
HeadOffice reporting implementation
Affiliate Brain wiring
Research Brain wiring
Finance Brain wiring
Ads Brain campaign execution
final compliance approval
live publishing authority
M’s current build work
Those remain governed by the relevant Brain, Canon, protocol, standard, or implementation layer.
Core Principle
Content Brain needs an operations dashboard only after the manual queue system proves the need.
The dashboard should not be built because it sounds useful.
It should be built only when the system repeatedly needs to see:
what is being produced
what needs refreshing
what should be repurposed
what is blocked
what is ready
what is risky
what is waiting for review
what needs handoff
what needs signal feedback
If the dashboard does not improve operational visibility, it should not be built yet.
Governance Role
The Content Operations Dashboard is a visibility layer.
It does not create authority.
It does not approve offers.
It does not approve campaigns.
It does not approve compliance-sensitive claims.
It does not authorise publishing.
It does not replace Content Brain frameworks, templates, checklists, or queues.
It only displays operational content work so operators can see the state of the Content Brain system.
Authority remains with the relevant owner, Brain, or human approval path.
Relationship To MCR
MCR remains the source of truth.
This specification belongs in MCR because it defines the future structure, purpose, and boundaries of the dashboard before any implementation occurs.
The MCR version defines:
dashboard purpose
dashboard scope
dashboard panels
dashboard views
dashboard filters
risk visibility
queue relationships
future UI candidate logic
drift protection
mwmscontentbrain.site may later operationalise this dashboard as a working interface.
Relationship To mwmscontentbrain.site
mwmscontentbrain.site is the likely future home of the operational Content Operations Dashboard.
The future dashboard may appear as:
a WordPress admin page
a custom Content Brain dashboard
a queue overview screen
a status summary panel
a Supabase-backed operational dashboard
a manual dashboard page first
a later plugin screen
The first version should be manual.
A plugin or UI should only be considered after the Production Queue, Refresh Queue, and Repurposing Queue have been used enough to prove the dashboard need.
MCR To Brain Classification
Destination: Later Plugin Or UI
Reason: Repeated structured interaction, multi-queue visibility, operational status tracking, bottleneck visibility, risk visibility, and dashboard-level control surface planning
Source Of Truth: MCR
Future Use: Content operations dashboard inside mwmscontentbrain.site
Future Plugin Or UI: Yes
This page should be listed in the Content Brain Copy Map as a future plugin or UI candidate.
Dashboard Function
The Content Operations Dashboard should provide high-level visibility across the main Content Brain operational queues.
The dashboard should show:
production workload
refresh workload
repurposing workload
blocked items
high-priority items
review items
approval items
handoff items
risk-sensitive items
content feedback items
The dashboard should help the operator decide what needs attention next.
It should not become a cluttered control panel.
It should show the few things that matter most.
Dashboard Source Queues
The dashboard should draw from the following future queue specifications:
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Repurposing Queue Specification
Future supporting checklist or tool specifications may later include:
Content Brain Publishing Readiness Checklist
Content Brain Content Brief Template
Content Brain SEO Content Brief Standard
Content Brain Content Signal Feedback Framework
Content Brain Content Optimization Framework
Content Brain Content Repurposing Framework
Dashboard Primary Panels
The future dashboard should include clear panels.
Panel 1: Content Production Overview
Purpose:
Show current new content production work.
Should display:
new content requests
items in briefing
items in drafting
items in review
items ready for approval
items ready for handoff
items published or closed
blocked production items
high-priority production items
Source:
Content Brain Content Production Queue Specification
Primary Question:
What new content is moving through production?
Panel 2: Content Refresh Overview
Purpose:
Show existing content needing review, update, improvement, merge, republishing, or retirement.
Should display:
new refresh items
classified refresh tasks
items being updated
items in review
items ready for approval
items republished
items under monitoring
merge review items
retirement review items
blocked refresh items
high-priority refresh items
Source:
Content Brain Content Refresh Queue Specification
Primary Question:
What existing content needs maintenance or improvement?
Panel 3: Content Repurposing Overview
Purpose:
Show approved assets being adapted into new formats.
Should display:
new repurposing opportunities
source review items
items in adaptation
items in review
items ready for approval
items handed off
items published or used
blocked repurposing items
follow-up repurposing items
Source:
Content Brain Repurposing Queue Specification
Primary Question:
Which approved assets can create more value through reuse?
Panel 4: Blocked Work
Purpose:
Show all blocked work across the three queues.
Should display:
blocked production items
blocked refresh items
blocked repurposing items
blocked reason
next action
next owner
date blocked
blocking Brain where relevant
Primary Question:
What is stuck and who needs to unblock it?
Panel 5: High Priority Work
Purpose:
Show important or time-sensitive content work.
Should display:
critical items
high-priority items
requesting Brain
content type
status
next action
owner
target date where relevant
Primary Question:
What needs attention first?
Panel 6: Review And Approval Queue
Purpose:
Show items waiting for review or approval.
Should display:
items in quality review
items in SEO review
items in trust review
items in compliance sensitivity review
items in affiliate status review
items in conversion support review
items ready for human approval
items ready for handoff approval
Primary Question:
What is waiting on review or approval?
Panel 7: Risk And Compliance Visibility
Purpose:
Show content items with elevated risk.
Should display:
high-risk items
moderate-risk items
claim-sensitive items
affiliate-sensitive items
health-sensitive items
finance-sensitive items
income-sensitive items
legal-sensitive items
items needing Compliance Brain review
items needing human review
Primary Question:
What content needs extra care before use?
Panel 8: Handoff And Publishing Readiness
Purpose:
Show content ready to move to another operator, Brain, platform, or destination.
Should display:
ready for handoff
handed off
publishing readiness completed
publishing readiness pending
handoff destination
approval status
next owner
Primary Question:
What content is ready to move, and where is it going?
Panel 9: Signal Feedback Needs
Purpose:
Show content items that require monitoring or feedback after use.
Should display:
published items awaiting signal review
republished items under monitoring
repurposed items under monitoring
feedback signal to watch
review date
destination Brain for feedback
observed outcome where available
Primary Question:
What content should teach the system something next?
Panel 10: Content Brain Workload Summary
Purpose:
Show a simple total view of operational workload.
Should display:
total active production items
total active refresh items
total active repurposing items
total blocked items
total review items
total high-priority items
total risk-sensitive items
total ready for handoff items
Primary Question:
How busy is Content Brain right now?
Dashboard Status Model
The dashboard should not create new statuses.
It should display statuses from the underlying queues.
Source status models:
Production Queue status model
Refresh Queue status model
Repurposing Queue status model
The dashboard may group statuses into simplified categories:
New
In Progress
In Review
Needs Approval
Ready For Handoff
Blocked
Published Or Used
Monitoring
Closed
This summary grouping is for visibility only.
It must not overwrite the original queue status.
Dashboard Priority Model
The dashboard should display priority from the underlying queues.
Priority values:
Low
Medium
High
Critical
The dashboard should be able to show:
critical items across all queues
high-priority items across all queues
priority by queue
priority by requesting Brain
priority by owner
Priority should help operators decide what to handle first.
Priority does not override governance or approval rules.
Dashboard Risk Model
The dashboard should display risk from the underlying queues.
Risk values:
Low
Moderate
High
Risk visibility should include:
compliance sensitivity
claim risk
affiliate risk
offer status concern
approval requirement
review requirement
Content with elevated risk should be visible before publication, handoff, or use.
Dashboard Ownership Model
Every visible dashboard item should show:
owner
next owner
approval owner where relevant
requesting Brain
supporting Brain where relevant
A dashboard item without a next owner is operationally weak.
The dashboard should make owner gaps visible.
Dashboard Filters
The future dashboard should support filters.
Queue Filter
Production
Refresh
Repurposing
All Queues
Status Filter
New
In Progress
In Review
Needs Approval
Ready For Handoff
Blocked
Published Or Used
Monitoring
Closed
Priority Filter
Low
Medium
High
Critical
Risk Filter
Low
Moderate
High
Needs Compliance Review
Needs Human Review
Brain Filter
Content Brain
HeadOffice
Research Brain
Affiliate Brain
Ads Brain
Conversion Brain
Sales Brain
Customer Brain
Data Brain
Compliance Brain
Owner Filter
Owner
Next Owner
Approval Owner
Destination Filter
WordPress Blog
Affiliate Support Page
YouTube Description
Email Platform
Social Platform
Internal Knowledge Page
Sales Support Asset
Content Queue
Refresh Queue
Repurposing Queue
Operator Handoff
Dashboard Views
The future dashboard should support several useful views.
Daily Operator View
Shows:
high-priority items
blocked items
review items
ready for approval items
ready for handoff items
Purpose:
help the operator decide what to do today.
Queue Health View
Shows:
production queue counts
refresh queue counts
repurposing queue counts
blocked item counts
review backlog
closed items
Purpose:
show whether Content Brain workflow is healthy.
Risk Review View
Shows:
high-risk content
claim-sensitive content
compliance-sensitive content
affiliate-sensitive content
items needing human review
Purpose:
prevent risky content from slipping through.
Handoff View
Shows:
ready for handoff
handed off
handoff destination
next owner
approval state
Purpose:
make handoffs visible and reduce lost work.
Signal Feedback View
Shows:
content under monitoring
feedback signal
review date
observed outcome
destination Brain
Purpose:
keep Content Brain connected to learning.
Brain Demand View
Shows:
requests by Brain
content type by Brain
blocked items by Brain
high-priority requests by Brain
Purpose:
show which Brains are requesting content support.
Dashboard Metrics
The dashboard should use simple operational metrics first.
Possible metrics:
active production items
active refresh items
active repurposing items
blocked items
items in review
items ready for approval
items ready for handoff
high-priority items
critical items
risk-sensitive items
items under monitoring
closed items this period
These are visibility metrics.
They are not performance proof by themselves.
Future Advanced Metrics
Later, if useful, the dashboard may include:
average time in production
average time blocked
average time in review
refresh completion rate
repurposing completion rate
content handoff completion rate
signal feedback completion rate
content reuse rate
published content count
refreshed content count
repurposed content count
These should only be added after manual usage proves they matter.
Dashboard Data Requirements
The dashboard should eventually draw from structured queue data.
Possible future sources:
Content Production Queue
Content Refresh Queue
Repurposing Queue
Publishing Readiness Checklist
Content Signal Feedback records
Content handoff records
This specification does not create database tables.
Any future data implementation must follow MWMS Supabase Naming Standard and relevant MWMS schema rules.
Future Minimal Data Concept
If implemented later, dashboard records may draw from future tables such as:
content_queue_items
content_refresh_items
content_repurposing_items
content_reviews
content_handoffs
content_signal_feedback
This naming is conceptual only.
It is not an implementation instruction.
First Manual Version
The first version of this dashboard should be manual.
A manual dashboard may use:
MCR summary page
Google Sheet summary
WordPress page table
simple status board
manual dashboard block on mwmscontentbrain.site later
The manual version should prove:
which panels matter
which queue views are actually used
which filters are needed
which metrics help decisions
which statuses create confusion
which dashboard fields are unnecessary
Only after manual use should a plugin or UI be considered.
Minimum Viable Dashboard
The minimum useful dashboard should show:
Production Queue summary
Refresh Queue summary
Repurposing Queue summary
Blocked items
High-priority items
Review and approval items
Risk-sensitive items
Ready for handoff items
Signal feedback items
This is enough to start without overbuilding.
Future Plugin Or UI Candidate
The Content Operations Dashboard is a strong future plugin or UI candidate.
Possible future features:
Queue summary cards
Status counts
Priority filters
Risk filters
Brain filters
Owner filters
Blocked item panel
Review item panel
Ready for handoff panel
Signal feedback panel
Daily operator view
Queue health view
Risk review view
Handoff view
Signal feedback view
Brain demand view
This should not be built yet.
Manual workflow must prove the need first.
Relationship To Content Brain Copy Map
This page should be listed in the Content Brain Copy Map as:
Page Title: Content Brain Content Operations Dashboard Specification
Destination: Later Plugin Or UI
Reason: Repeated structured interaction, multi-queue visibility, operational status tracking, bottleneck visibility, risk visibility, and dashboard-level control surface planning
Source Of Truth: MCR
Future Use: Content operations dashboard inside mwmscontentbrain.site
Future Plugin Or UI: Yes
Relationship To Content Brain Page Registry
This page should be added to the Content Brain Page Registry as:
Page Title: Content Brain Content Operations Dashboard Specification
Document Type: Specification
Parent Page: Content Brain
Status: Draft
Destination: Later Plugin Or UI
Reason: Future content operations dashboard system
Source Of Truth: MCR
Future Use: Content operations dashboard planning
Relationship To Content Brain Operating Model
The Content Brain Operating Model defines Content Brain’s role and responsibilities.
This specification defines a future visibility layer for seeing those responsibilities in action.
Operating Model = role and boundaries
Operations Dashboard Specification = future operational visibility surface
Relationship To Content Brain Workflow Map
The Content Brain Workflow Map defines the movement of content work.
The Content Operations Dashboard displays that movement across multiple queues.
Workflow Map = process
Operations Dashboard = visibility layer
Relationship To Content Brain Content Production Queue Specification
The Content Production Queue tracks new content production.
The Operations Dashboard summarises production work across the wider content system.
Production Queue = new content tracking
Operations Dashboard = multi-queue overview
Relationship To Content Brain Content Refresh Queue Specification
The Content Refresh Queue tracks improvement of existing content.
The Operations Dashboard summarises refresh activity, bottlenecks, and priority.
Refresh Queue = content maintenance tracking
Operations Dashboard = multi-queue overview
Relationship To Content Brain Repurposing Queue Specification
The Repurposing Queue tracks approved content reuse into new formats.
The Operations Dashboard summarises repurposing opportunities, active adaptations, and handoffs.
Repurposing Queue = content reuse tracking
Operations Dashboard = multi-queue overview
Relationship To Content Brain Publishing Readiness Checklist
The Publishing Readiness Checklist defines the gate before publishing or handoff.
The Operations Dashboard may show readiness status across items.
Publishing Readiness Checklist = review gate
Operations Dashboard = readiness visibility
Relationship To Content Brain Content Signal Feedback Framework
The Content Signal Feedback Framework defines how content-generated signals return to the MWMS system.
The Operations Dashboard may show items needing signal review.
Content Signal Feedback Framework = feedback logic
Operations Dashboard = feedback visibility
Relationship To Other MWMS Documents
This page must align with:
Content Brain Copy Map
Content Brain Page Registry
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Content Brief Template
Content Brain Publishing Readiness Checklist
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Repurposing Queue Specification
Content Brain Content Signal Feedback Framework
Content Brain Content Production System Framework
Content Brain Content Optimization Framework
Content Brain Content Repurposing Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Brain To Brain Request Protocol
MWMS Supabase Naming Standard
MWMS Supabase Task Schema Standard
MWMS Document Structure Standard
MWMS Page Naming Standard
MWMS AI Output Standard Full File Delivery Rule
Drift Protection
The system must prevent:
dashboard work beginning before queues prove manual need
dashboard becoming a duplicate of MCR
dashboard replacing queue logic
dashboard creating authority
dashboard approving content
dashboard hiding risk-sensitive items
dashboard hiding blocked items
dashboard showing items without owner or next action
dashboard mixing governance pages with operational work
dashboard treating Review Later pages as active operational pages
dashboard being built as a plugin before manual workflow proves the need
dashboard interfering with M’s active build areas
dashboard creating noise instead of clarity
Architectural Intent
The Content Brain Content Operations Dashboard Specification exists to define the future visibility layer for Content Brain operations.
Its role is to unify operational visibility across production, refresh, and repurposing without merging those workflows into one confused queue.
The dashboard should help MWMS know:
what is being created
what is being improved
what is being reused
what is blocked
what is risky
what is ready
what needs review
what needs handoff
what needs signal feedback
The long-term intent is to support a practical operational dashboard on mwmscontentbrain.site while preserving MCR as the source of truth.
Final Rule
The Content Operations Dashboard must show content work.
It must not create authority.
If the dashboard does not make Content Brain clearer, faster, safer, or easier to manage, it should not be built yet.
Manual workflow must prove the dashboard before plugin or UI implementation begins.
Change Log
Version: v1.0
Date: 2026-05-06
Author: HeadOffice
Change: Initial creation of Content Brain Content Operations Dashboard Specification defining the future dashboard structure for production queue visibility, refresh queue visibility, repurposing queue visibility, blocked work, priority work, review and approval items, risk visibility, handoff status, signal feedback needs, dashboard filters, dashboard views, metrics, future data concepts, plugin or UI candidate logic, and drift protection.
Change Impact Declaration
Pages Created:
Content Brain Content Operations Dashboard Specification
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Change Log Entry Required:
No