Parent: Content Brain
Status: Active Specification
Version: v1.0
Last Reviewed: 2026-06-11
Purpose
The Content Brain Output Layer Operating Workflow defines how Content Brain moves from approved intelligence, Site Intelligence Records, existing page reviews, affiliate funnel needs, content gaps, and publishing opportunities into usable content outputs.
This page explains the operating sequence behind the Content Brain Output Style Selector.
The purpose is to make sure Content Brain works like a content department.
Content Brain should not stop at records.
Content Brain should not become Research Brain.
Content Brain should not create more WordPress test-page bloat.
Content Brain should move approved inputs into the correct output pathway.
Core Rule
Content Brain operates through this sequence:
Input
Decision
Output Type Selection
Structured Output
Human Review
Next Action
The Output Layer does not begin with full automation.
The Output Layer does not begin with full article generation.
The Output Layer begins with controlled manual outputs that help Martyn decide what content asset, brief, plan, checklist, pack, or support asset should be created next.
Department Purpose
Content Brain owns the transformation of approved intelligence into usable content assets.
Content Brain does not own primary research discovery.
Content Brain does not own compliance policy.
Content Brain does not own campaign testing.
Content Brain does not own attribution infrastructure.
Content Brain does not own finance approval.
Content Brain does not own automation execution.
Content Brain receives inputs from other Brains and turns those inputs into content output pathways.
Operating Principle
Content Brain should ask:
What should this become?
Not:
What else can we research?
What else can we store?
What else can we log?
What else can we turn into another test page?
The Content Brain Output Layer exists to convert known information into content action.
Workflow Overview
The Content Brain Output Layer has six operating stages.
Stage 1:
Input Capture
Stage 2:
Input Classification
Stage 3:
Output Style Selection
Stage 4:
Structured Output Creation
Stage 5:
Human Review
Stage 6:
Next Action Decision
Each stage must remain human controlled until a later automation layer is explicitly approved.
Stage 1: Input Capture
Input Capture identifies the source material that Content Brain will use.
Accepted input sources include:
Site Intelligence Records
Existing WordPress pages
Existing MCR pages
Affiliate offer notes
Research Brain outputs
Compliance Brain notes
Conversion Brain notes
UX Brain notes
Ads Brain signals
Data Brain performance signals
Manual page reviews
Refresh candidates
Publishing readiness checks
Content gaps
Affiliate funnel gaps
Internal linking gaps
Repurposing opportunities
Content Brain should not treat every input as a new WordPress page.
The input should first be classified.
Stage 2: Input Classification
Input Classification determines what kind of content situation exists.
The operator should classify the input as one of the following:
New content opportunity
Existing page refresh
Thin content expansion
Affiliate funnel support need
Pre-sell asset need
Product review need
Comparison page need
Authority article need
Internal linking need
Publishing readiness need
Repurposing opportunity
Content QA need
Compliance-sensitive content need
Research clarification needed
Hold / not ready
This stage prevents Content Brain from jumping too quickly into content creation.
Stage 3: Output Style Selection
Output Style Selection chooses the correct Content Brain output type.
Approved first-stage output types are:
SEO Content Brief
Affiliate Pre-Sell Page Brief
Product Review Page Brief
Comparison Page Brief
Listicle Brief
Authority Article Brief
Refresh Plan
Thin Content Expansion Plan
Internal Linking Plan
Repurposing Pack
Publishing Readiness Checklist
Content QA Output
Affiliate Funnel Support Pack
The selector should recommend one primary output type.
It may also recommend one secondary supporting output if needed.
Example:
Primary Output:
Refresh Plan
Secondary Output:
Internal Linking Plan
Another example:
Primary Output:
Affiliate Pre-Sell Page Brief
Secondary Output:
Compliance Brain Review Required
The selector should avoid creating too many simultaneous next actions.
Stage 4: Structured Output Creation
Structured Output Creation produces the selected manual output.
At this stage, Content Brain should create:
A brief
A plan
A checklist
A pack
A QA output
A readiness review
A content pathway
It should not automatically create a full article unless full content generation has been explicitly approved.
The structured output should include:
Source input
Output type
Primary goal
Audience stage
Content purpose
Recommended structure
Evidence requirements
Internal linking notes
Affiliate or funnel notes if relevant
Compliance notes if relevant
Publishing readiness status
Recommended next action
Human approval status
Stage 5: Human Review
Human Review confirms whether the output is useful, accurate, aligned, and ready for the next step.
The reviewer should check:
Is the correct output type selected?
Does the output match Content Brain’s department purpose?
Is the input source clear?
Is the goal clear?
Is the page or asset purpose clear?
Are compliance risks flagged?
Are evidence gaps flagged?
Is the next action clear?
Is this ready to become a draft, update, pack, or checklist?
If the output is not ready, it should be revised before moving forward.
Stage 6: Next Action Decision
Next Action Decision determines what happens after the structured output is reviewed.
Possible next actions include:
Create draft manually
Update existing page manually
Create WordPress page manually
Create content brief only
Send to Compliance Brain for review
Send to Research Brain for clarification
Send to Conversion Brain for page improvement
Send to UX Brain for usability review
Add to content queue later
Mark as ready for publishing review
Hold
Archive record
No action
At this phase, the next action remains human controlled.
No automatic routing should occur unless a later Brain Room routing layer is explicitly approved.
First Version Behaviour
The first version of the Content Brain Output Layer should behave as a manual decision and output workflow.
It should:
Read from existing inputs or records
Help choose the right output style
Produce a structured brief, plan, checklist, or pack
Keep the operator in control
Avoid full automation
Avoid full content generation
Avoid hidden routing
Avoid AI Employee execution
Avoid queue creation unless approved later
Avoid M handoff unless explicitly requested
This is not a limitation on the future system.
It is the correct first build sequence.
Records Layer Relationship
The Records layer is a support layer for this workflow.
The Records layer stores:
Site Intelligence test records
Evidence records
Review outcomes
Friction signals
Build readiness signals
Compliance risk flags
Routing recommendations
Status tracking
Migration tracking
Archive state
The Output Layer uses these records to decide what content output should happen next.
Correct relationship:
Records store intelligence.
Output Style Selector chooses the output.
Output Layer creates the structured content pathway.
Human review approves the next action.
The Records layer is important and should continue to be used for material that belongs in structured storage.
But the Records layer is not the main Content Brain product.
Output Layer Field Structure
Each Output Layer record should include the following fields.
Source Name
The name of the page, record, offer, review, or input.
Source Type
Options:
Site Intelligence Record
Existing WordPress Page
MCR Page
Affiliate Offer
Research Brain Input
Compliance Brain Input
Conversion Brain Input
UX Brain Input
Ads Brain Input
Data Brain Input
Manual Review
Other
Input Status
Options:
Approved input
Needs clarification
Needs evidence
Needs compliance review
Ready for output selection
Hold
Output Type Selected
Options:
SEO Content Brief
Affiliate Pre-Sell Page Brief
Product Review Page Brief
Comparison Page Brief
Listicle Brief
Authority Article Brief
Refresh Plan
Thin Content Expansion Plan
Internal Linking Plan
Repurposing Pack
Publishing Readiness Checklist
Content QA Output
Affiliate Funnel Support Pack
Primary Goal
Options:
Traffic
Conversion
Authority
Refresh
Expansion
Publishing
Repurposing
Internal Linking
Affiliate Funnel Support
Compliance Preparation
Audience Stage
Options:
Unaware
Problem Aware
Solution Aware
Product Aware
Most Aware
Existing Asset Status
Options:
No page exists
Page exists
Page exists and needs review
Page exists and needs refresh
Page exists and needs expansion
Page exists and is near publishing
Page exists and should be repurposed
Compliance Risk
Options:
Low
Moderate
High
Unknown
Evidence Status
Options:
Sufficient
Needs more evidence
Unclear
Not required
Publishing Readiness
Options:
Not started
Draft required
Draft exists
Needs review
Ready after fixes
Ready
Human Approval Status
Options:
Not reviewed
Needs Martyn review
Approved for brief
Approved for refresh
Approved for publishing review
Approved for manual draft
Blocked
Recommended Next Action
Options:
Create brief
Create refresh plan
Create expansion plan
Create internal linking plan
Create repurposing pack
Run Content QA
Run publishing readiness check
Request Compliance Brain review
Request Research Brain clarification
Request Conversion Brain review
Request UX Brain review
Hold
No action
Output Type Rules
The selected output type must match the situation.
If no page exists and search intent is clear:
Use SEO Content Brief.
If no page exists and the offer needs pre-sell support:
Use Affiliate Pre-Sell Page Brief.
If one product or offer is being evaluated:
Use Product Review Page Brief.
If multiple options must be compared:
Use Comparison Page Brief.
If the topic naturally requires multiple options:
Use Listicle Brief.
If the goal is topical authority:
Use Authority Article Brief.
If a page exists and needs improvement:
Use Refresh Plan.
If a page exists but lacks depth:
Use Thin Content Expansion Plan.
If page connections are weak:
Use Internal Linking Plan.
If a strong asset can be reused elsewhere:
Use Repurposing Pack.
If a draft or page is close to going live:
Use Publishing Readiness Checklist.
If quality is uncertain:
Use Content QA Output.
If multiple assets are needed around an affiliate offer:
Use Affiliate Funnel Support Pack.
Cross-Brain Input Handling
Content Brain may receive input from other Brains, but must transform the input into Content Brain output.
Research Brain input becomes:
Content brief direction
Authority article direction
Evidence-backed content plan
Content gap decision
Compliance Brain input becomes:
Claim-safe content notes
Evidence requirements
Publishing caution
Review required status
Conversion Brain input becomes:
Pre-sell structure
CTA improvement
Trust section requirement
Page refresh recommendation
UX Brain input becomes:
Content layout improvement
Navigation support
Readability improvement
Content clarity fix
Ads Brain input becomes:
Hook-informed content angle
Affiliate funnel support need
Landing page content support
Data Brain input becomes:
Refresh priority
Performance-informed content decision
Content opportunity validation
The source Brain does not take over the Content Brain output.
No Full Generation Rule
The Output Layer does not automatically generate full articles at v1.0.
Allowed outputs at v1.0:
Briefs
Plans
Checklists
Packs
QA outputs
Readiness reviews
Manual next action recommendations
Not allowed at v1.0 unless explicitly approved:
Full article generation
Automatic publishing
Automatic task routing
Automatic worker execution
Automatic AI Employee action
Automatic queue creation
Automatic cross-brain wiring
This is a sequencing rule, not a permanent ban.
Content generation can become a later layer after the output workflow is stable.
WordPress Page Boundary
Content Brain should not create WordPress pages for every test, record, or output decision.
WordPress should be used for:
Core operating pages
Frameworks
Protocols
Templates
Specifications
Short summary logs
Approved canon
Supabase should be used for:
Repeatable test records
Evidence records
Review outcomes
Friction signals
Build readiness signals
Compliance risk flags
Routing recommendations
Migration tracking
Archive state
Output Layer records may later live in Supabase if they become repeatable operational records.
MCR / WordPress should not become the storage layer for every output decision.
First Build Screen Concept
The first Output Layer screen should be simple.
Screen name:
Content Brain Output Layer
Primary sections:
Select Source
Classify Input
Choose Output Style
Create Structured Output
Review Next Action
Source panel fields:
Source name
Source type
Related record
Related WordPress page
Related offer
Input status
Classification panel fields:
Content situation
Primary goal
Audience stage
Existing asset status
Compliance risk
Evidence status
Selector panel fields:
Recommended output type
Secondary output if needed
Reason for recommendation
Output panel fields:
Brief / plan / checklist / pack body
Internal link notes
Compliance notes
Publishing readiness
Recommended next action
Review panel fields:
Human approval status
Reviewer note
Final next action
This screen should remain manual at first.
Success Criteria
The Output Layer is successful when:
Content Brain clearly feels like a content department.
The operator can move from a record or page review into a content output.
The correct output type is easy to choose.
The output is useful enough for manual action.
Records remain support infrastructure.
WordPress test-page bloat is reduced.
Existing MCR / WordPress Site Intelligence material can be migrated into structured records.
Content Brain moves toward real content asset production.
The next action is clear.
Failure Conditions
The Output Layer has failed if:
It becomes another records screen.
It creates more research-style storage.
It creates more WordPress test pages.
It does not produce a content brief, plan, checklist, pack, or next action.
It starts automation too early.
It starts full content generation without approval.
It starts routing without approval.
It hides the source of the output.
It does not keep the human in control.
It makes Content Brain feel like Research Brain.
Future Expansion
Future versions may include:
Output brief templates
Draft generation
Content production queue
Content approval workflow
Publishing workflow
Content generator
Content worker
Content Brain AI Employee
Supabase output records
Brain Room routing
Compliance review routing
Research clarification routing
Conversion review routing
Internal linking automation
Repurposing automation
Dashboard reporting
These future layers should only start after:
The Output Style Selector is stable
The Output Layer workflow is clear
Support versus core is understood
Manual workflow proves the right path
Martyn approves the next build stage
Operating Principle
The Output Layer is the bridge between intelligence and content production.
It should not collect intelligence forever.
It should not generate content too early.
It should select the correct content output and create the structured pathway for action.
Final Rule
The Content Brain Output Layer Operating Workflow defines how Content Brain moves from approved inputs into structured content outputs.
The workflow must remain output-focused.
Records support the workflow.
The Output Style Selector guides the workflow.
Human review controls the workflow.
Future automation, routing, workers, generators, queues, AI Employees, and dashboards are allowed later only when the manual output workflow is stable and approved.
Version: v1.0
Date: 2026-06-11
Author: HeadOffice
Change:
Added Content Brain Output Layer Operating Workflow as the operating sequence behind the Content Brain Output Style Selector.
This page defines how Content Brain moves from inputs, records, existing pages, affiliate needs, content gaps, refresh opportunities, and cross-brain signals into selected content output types, structured manual outputs, human review, and next action decisions.
Change Impact Declaration
Pages Created:
Content Brain Output Layer Operating Workflow
Pages Updated:
None
Pages Deprecated:
None
Standalone Pages Not Created:
Content Brain Output Layer UI Build Pack
Content Brain Content Production Queue Specification
Content Brain Content Generator Specification
Content Brain AI Employee Specification
Content Brain Brain Room Routing Specification
Content Brain Supabase Output Records Schema
Registries Requiring Update:
Content Brain Page Registry
MWMS Architecture Registry if tracking Content Brain core surface specifications
Canon Version Update Required:
No
Change Log Entry Required:
Yes
Strategic Absorption Result:
Content Brain core direction strengthened. The Output Layer Operating Workflow establishes the manual operating sequence for moving from approved intelligence and support records into content output decisions. It confirms that Records remain support infrastructure while the Output Layer becomes the bridge toward SEO briefs, affiliate pre-sell briefs, review briefs, comparison briefs, refresh plans, expansion plans, internal linking plans, repurposing packs, publishing readiness checks, content QA outputs, and affiliate funnel support packs.