Parent: Content Brain
Status: Active Specification
Version: v1.0
Last Reviewed: 2026-06-11
Purpose
The Content Brain Output Layer Screen Specification defines the first practical screen structure for the Content Brain Output Layer.
This page translates the Content Brain Output Style Selector, Output Layer Operating Workflow, and Output Templates And Field Standard into a simple first-version screen that can later be built inside the Content Brain plugin UI.
The purpose is to define the correct Content Brain operating surface before any UI build starts.
Content Brain must feel like a content department.
The screen must help the operator move from an approved input or record into a selected content output type, structured manual output, human review, and next action decision.
Core Rule
The Content Brain Output Layer screen must support this workflow:
Select Source
Classify Input
Choose Output Style
Create Structured Output
Review Next Action
The screen must not begin as automation.
The screen must not begin as a full content generator.
The screen must not begin as a task router.
The screen must not begin as an AI Employee execution surface.
The first screen must be a human-controlled content output decision surface.
Department Purpose
Content Brain owns the transformation of approved intelligence into usable content assets.
The screen must support:
Content output decisions
Output style selection
Brief creation
Refresh plan creation
Expansion plan creation
Publishing readiness review
Repurposing pack creation
Internal linking plan creation
Content QA output
Affiliate funnel support planning
The screen must not become:
A research evidence database
A generic dashboard
A raw records table
A full automation surface
A worker execution screen
A Brain Room routing screen
A full content generator
Those may be future layers if approved, but they are not the v1.0 screen purpose.
Screen Name
Recommended screen name:
Content Brain Output Layer
Alternative screen names:
Content Output Layer
Output Style Selector
Content Output Selector
Recommended first screen title:
Content Brain Output Layer
Reason:
This name keeps the screen connected to Content Brain’s real core purpose and avoids making the selector feel like a small feature instead of the main output surface.
Screen Purpose Statement
The screen should display a short purpose statement.
Recommended wording:
Use this screen to turn approved records, existing page reviews, content gaps, affiliate funnel needs, and publishing opportunities into the correct Content Brain output type.
Records store the intelligence.
This screen chooses what the intelligence should become.
Primary Screen Sections
The first version of the screen should include five primary sections.
- Select Source
- Classify Input
- Choose Output Style
- Create Structured Output
- Review Next Action
These sections should appear in this order.
The screen should guide the operator from source to decision, not from source to more storage.
Section 1: Select Source
Purpose
Select Source identifies what the operator is working from.
This could be a Site Intelligence Record, an existing WordPress page, an affiliate offer, a Research Brain input, a Compliance Brain note, or a manual review.
The purpose is to connect the output to a source without turning the screen into another records database.
Fields
Source Name
Source Type
Related Record ID
Related WordPress Page
Related URL
Related Offer
Source Status
Input Notes
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
Source Status Options
Approved input
Needs clarification
Needs evidence
Needs compliance review
Ready for output selection
Hold
Section Behaviour
The operator should be able to manually select or enter a source.
Future versions may connect directly to Supabase Site Intelligence Records, but v1.0 should not require full automation.
Section 1 Output
At the end of this section, the operator should know:
What source is being used
What type of source it is
Whether the source is ready for output selection
Whether more clarification is needed before continuing
Section 2: Classify Input
Purpose
Classify Input determines what content situation exists.
This section prevents Content Brain from jumping directly into the wrong output type.
Fields
Content Situation
Primary Goal
Audience Stage
Existing Asset Status
Affiliate Relevance
Compliance Risk
Evidence Status
Publishing Readiness
Content Situation Options
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
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
Affiliate Relevance Options
Not affiliate-related
Affiliate support possible
Affiliate offer primary
Affiliate funnel support required
Unknown
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
Section Behaviour
This section should help the operator classify the input before selecting the output type.
It should not decide automatically at v1.0.
It may suggest an output type later, but human control remains required.
Section 2 Output
At the end of this section, the operator should know:
What kind of content situation exists
What the primary goal is
Whether the input is affiliate-related
Whether compliance risk matters
Whether the output is ready to proceed
Section 3: Choose Output Style
Purpose
Choose Output Style is the main Content Brain decision point.
This section selects what the input should become.
Fields
Recommended Output Type
Secondary Output Type If Needed
Reason For Selection
Output Priority
Output Confidence
Hold Reason If Not Ready
Recommended Output Type 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
Secondary Output Type Options
None
Internal Linking Plan
Compliance Brain Review Required
Research Brain Clarification Required
Conversion Brain Review Required
UX Brain Review Required
Repurposing Pack
Publishing Readiness Checklist
Content QA Output
Output Priority Options
Low
Medium
High
Hold
Output Confidence Options
Low
Moderate
High
Decision Rules
If no page exists and search intent is clear:
Recommend SEO Content Brief.
If no page exists and the offer needs pre-sell support:
Recommend Affiliate Pre-Sell Page Brief.
If one product or offer is being evaluated:
Recommend Product Review Page Brief.
If multiple options must be compared:
Recommend Comparison Page Brief.
If the topic naturally requires a list:
Recommend Listicle Brief.
If the goal is topical authority:
Recommend Authority Article Brief.
If a page exists and needs improvement:
Recommend Refresh Plan.
If a page exists but lacks depth:
Recommend Thin Content Expansion Plan.
If page connections are weak:
Recommend Internal Linking Plan.
If a strong asset can be reused elsewhere:
Recommend Repurposing Pack.
If a draft or page is close to publishing:
Recommend Publishing Readiness Checklist.
If quality is uncertain:
Recommend Content QA Output.
If multiple assets are needed around an affiliate offer:
Recommend Affiliate Funnel Support Pack.
Section Behaviour
The operator should choose the output type manually.
The screen may show guidance based on the classification, but it should not force the choice.
Section 3 Output
At the end of this section, the operator should know:
What output type has been selected
Why that output type was selected
Whether any secondary review or support output is needed
Whether the output is high priority or should be held
Section 4: Create Structured Output
Purpose
Create Structured Output produces the actual manual output.
This section should generate or display the structured brief, plan, checklist, pack, QA output, or readiness review.
At v1.0 this should remain a manual structured output layer, not a full content generation layer.
Fields
Output Name
Output Type
Source Input
Primary Goal
Audience Stage
Output Body
Evidence Requirements
Compliance Notes
Internal Linking Notes
Affiliate Notes
Publishing Readiness
Recommended Next Action
Human Approval Status
Template Selection
The selected Output Type should determine the structure of the Output Body.
Template mappings:
SEO Content Brief uses SEO Content Brief Template.
Affiliate Pre-Sell Page Brief uses Affiliate Pre-Sell Page Brief Template.
Product Review Page Brief uses Product Review Page Brief Template.
Comparison Page Brief uses Comparison Page Brief Template.
Listicle Brief uses Listicle Brief Template.
Authority Article Brief uses Authority Article Brief Template.
Refresh Plan uses Refresh Plan Template.
Thin Content Expansion Plan uses Thin Content Expansion Plan Template.
Internal Linking Plan uses Internal Linking Plan Template.
Repurposing Pack uses Repurposing Pack Template.
Publishing Readiness Checklist uses Publishing Readiness Checklist Template.
Content QA Output uses Content QA Output Template.
Affiliate Funnel Support Pack uses Affiliate Funnel Support Pack Template.
Output Body Requirements
The Output Body must include:
Source summary
Output purpose
Recommended structure
Evidence requirements
Compliance notes if relevant
Internal linking notes if relevant
Affiliate or funnel notes if relevant
Publishing readiness status
Recommended next action
Human approval status
No Full Generation Rule
The Output Body should not automatically create full articles at v1.0.
Allowed:
Briefs
Plans
Checklists
Packs
QA outputs
Readiness reviews
Manual next action recommendations
Not approved at v1.0:
Full article generation
Automatic publishing
Automatic routing
Automatic queue creation
Automatic worker execution
Automatic AI Employee execution
Automatic cross-brain task wiring
Section 4 Output
At the end of this section, the operator should have a usable structured output.
The output should be specific enough to act on manually.
Section 5: Review Next Action
Purpose
Review Next Action confirms what happens after the output is created.
This keeps the workflow human controlled and prevents hidden automation.
Fields
Human Approval Status
Reviewer Notes
Final Next Action
Hold Reason
Follow-Up Brain Needed
Ready For Manual Work
Human Approval Status Options
Not reviewed
Needs Martyn review
Approved for brief
Approved for refresh
Approved for publishing review
Approved for manual draft
Blocked
Final 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
Create manual draft
Update existing page manually
Hold
No action
Follow-Up Brain Needed Options
None
Research Brain
Compliance Brain
Conversion Brain
UX Brain
Ads Brain
Data Brain
Affiliate Brain
HeadOffice
Ready For Manual Work Options
Yes
No
Hold
Section Behaviour
This section should not trigger automatic routing at v1.0.
It should only record the recommended next action.
Future versions may add routing after approval.
Section 5 Output
At the end of this section, the operator should know:
Whether the output is approved
What should happen next
Whether another Brain should be consulted
Whether the asset is ready for manual work
First Version UI Layout
Recommended layout:
Top summary bar
Source panel
Classification panel
Output selector panel
Structured output panel
Review and next action panel
Top Summary Bar Fields
Output Name
Source Type
Selected Output Type
Primary Goal
Compliance Risk
Human Approval Status
Recommended Next Action
Top Summary Bar Purpose
The summary bar should make the workflow status visible without turning the screen into a dashboard.
It should answer:
What are we working on?
What will this become?
What is the next action?
Admin Menu Placement
Recommended admin menu placement:
Content Brain
Submenu:
Output Layer
Alternative submenu names:
Output Style Selector
Content Outputs
Recommended:
Output Layer
Reason:
Output Layer is broader than Output Style Selector and allows the screen to later include structured outputs, review, and next actions.
Screen Status Line
The screen should include a status line.
Recommended status line:
Manual output selection enabled.
Structured output creation enabled.
Human review required.
No full content generation.
No automation.
No worker execution.
No Brain Room routing.
No publishing action.
No M handoff.
Important clarification:
This status line applies only to v1.0 of this screen.
It does not ban future automation, routing, workers, generators, AI Employees, dashboards, queues, or cross-brain wiring.
Those are later build layers that must be approved in the correct sequence.
Button Behaviour
Recommended first-version buttons:
Create Output
Save Output
View Output
Edit Output
Mark Reviewed
Hold
Recommended buttons not included at v1.0:
Generate Full Article
Publish
Auto Route
Send To Worker
Create Queue Task
Assign AI Employee
Delete
Button Rules
Create Output:
Creates or displays the structured output based on selected output type.
Save Output:
Saves the manual output record if output records are approved.
View Output:
Shows the structured output.
Edit Output:
Allows safe editing of the output.
Mark Reviewed:
Updates human approval status.
Hold:
Marks output as not ready.
Do not include Delete at v1.0 unless explicitly approved.
Supabase Relationship
This screen may later connect to a Supabase output records table.
This specification does not approve that table yet.
Potential future table:
content_brain_outputs
Potential fields:
id
created_at
updated_at
source_name
source_type
source_record_id
related_page_id
related_url
related_offer
input_status
content_situation
primary_goal
audience_stage
existing_asset_status
affiliate_relevance
compliance_risk
evidence_status
publishing_readiness
selected_output_type
secondary_output_type
reason_for_selection
output_priority
output_confidence
output_name
output_body
evidence_requirements
compliance_notes
internal_linking_notes
affiliate_notes
human_approval_status
reviewer_notes
recommended_next_action
follow_up_brain_needed
ready_for_manual_work
status
migration_status
Supabase Boundary
Supabase may store repeatable operational records.
WordPress should not become the storage layer for every output decision.
If output records become repeatable, they should go to Supabase, not WordPress test pages.
WordPress Relationship
WordPress pages should be used for:
Core operating pages
Frameworks
Protocols
Templates
Specifications
Short summary logs
Approved canon
WordPress should not be used for:
Every output record
Every test record
Every review outcome
Every content decision
Every archive state
Every migration state
The Output Layer screen should reduce WordPress bloat, not create more of it.
First Build Scope
The first build scope should include:
Output Layer submenu
Source selection section
Input classification section
Output type selector
Structured output display area
Human review fields
Recommended next action field
Manual save if output records are approved
The first build scope should not include:
Full content generation
Automatic publishing
Brain Room routing
Worker execution
AI Employee assignment
Queue creation
Cross-brain automation
Dashboard reporting
Delete function
Current Status For This Specification
This page is a specification only.
It does not start the plugin build.
It does not start Supabase build.
It does not create a worker.
It does not create routing.
It does not create automation.
It defines the correct screen shape so future build work does not drift.
Future Expansion
Future versions may add:
Supabase output records
Template-based output saving
Output history
Output queue
Content production queue
Full draft generation
Publishing workflow
Compliance routing
Research clarification routing
Conversion review routing
UX review routing
AI Employee assignment
Worker execution
Dashboard reporting
These future layers must be approved separately.
Success Criteria
The screen is successful when:
The operator can select a source.
The input can be classified.
The correct output style can be chosen.
A structured output can be created.
A human review decision can be recorded.
The next action is clear.
The screen feels like Content Brain, not Research Brain.
Records remain support infrastructure.
No extra WordPress test-page bloat is created.
No hidden automation starts.
Failure Conditions
The screen has failed if:
It becomes mainly a records table.
It focuses mainly on evidence capture.
It feels like Research Brain.
It generates full articles without approval.
It routes tasks without approval.
It creates workers without approval.
It creates queue tasks without approval.
It assigns AI Employees without approval.
It creates unnecessary WordPress pages.
It does not produce a clear content output.
It does not show a clear next action.
Operating Principle
The screen must make Content Brain practical.
It must help the operator decide what content asset should be created, refreshed, expanded, repurposed, checked, or prepared next.
It must not become another storage layer.
Final Rule
The Content Brain Output Layer Screen is the first practical UI surface for Content Brain’s corrected output direction.
The screen must guide the operator through source selection, input classification, output style selection, structured output creation, and human review.
At v1.0, the screen remains manual and output-focused.
Future automation, routing, queues, workers, AI Employees, dashboards, and generators are allowed later only after the output workflow is stable and approved.
Version: v1.0
Date: 2026-06-11
Author: HeadOffice
Change:
Added Content Brain Output Layer Screen Specification as the first practical screen specification for the corrected Content Brain Output Layer.
This page translates the Output Style Selector, Output Layer Operating Workflow, and Output Templates And Field Standard into a simple first-version Content Brain UI screen structure.
Change Impact Declaration
Pages Created:
Content Brain Output Layer Screen Specification
Pages Updated:
None
Pages Deprecated:
None
Standalone Pages Not Created:
Content Brain Output Layer Plugin Build Pack
Content Brain Output Records Supabase Schema
Content Brain Content Generator Specification
Content Brain Output Queue Specification
Content Brain AI Employee Specification
Content Brain Brain Room Routing Specification
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 output direction moved from conceptual workflow into first-screen specification. The screen is defined around source selection, input classification, output style selection, structured output creation, and human review. This gives Content Brain a practical UI direction while keeping Records as support infrastructure and preventing premature automation, generation, routing, workers, queues, or AI Employee execution.