Parent: Content Brain
Status: Active Specification
Version: v1.0
Last Reviewed: 2026-06-11
Purpose
The Content Brain Output Templates And Field Standard defines the required structure for Content Brain’s first manual output templates.
This page supports the Content Brain Output Style Selector and the Content Brain Output Layer Operating Workflow.
The purpose is to make each Content Brain output consistent, useful, copyable, reviewable, and ready for human-controlled action.
Content Brain should not produce vague recommendations.
Content Brain should produce structured outputs that can become briefs, plans, checklists, packs, QA reviews, publishing reviews, and affiliate funnel support assets.
Core Rule
Every Content Brain output must follow a defined template.
The output must clearly state:
Source input
Output type
Purpose
Audience stage
Primary goal
Existing asset status
Recommended structure
Evidence requirements
Compliance notes
Internal linking notes
Publishing readiness
Human approval status
Recommended next action
If the output does not make the next action clear, it has failed.
Relationship To Output Style Selector
The Output Style Selector chooses what type of output is needed.
This page defines what each selected output must contain.
Correct relationship:
Output Style Selector chooses the output type.
Output Layer Operating Workflow controls the process.
Output Templates And Field Standard controls the structure of each output.
Manual workflow remains human controlled.
No full content generation is approved by this page.
Output Template Rules
Each output template must be:
Clear
Structured
Human-reviewable
Source-linked
Action-focused
Content-output shaped
Not research-shaped
Not dashboard-shaped
Not automation-shaped
Not generic
Each template should help Martyn or the operator decide what to do next.
Each template should support eventual plugin UI or Supabase structure, but it should work manually first.
Shared Fields For All Output Templates
Every Content Brain output should include the following shared fields.
Output Name
The name of the output being created.
Example:
ProDentim Affiliate Page Refresh Plan
Output Type
The selected output type.
Examples:
SEO Content Brief
Refresh Plan
Affiliate Pre-Sell Page Brief
Publishing Readiness Checklist
Source Input
The source record, page, review, offer, or input used to create the output.
Examples:
Site Intelligence Test 3 ProDentim Affiliate Page Review
Existing WordPress page
Affiliate offer notes
Research Brain 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
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
SEO Content Brief Template
Use this template when the output should become a search-focused content brief.
Template Fields
Output Name
Output Type
Source Input
Target Topic
Search Intent
Primary Keyword If Known
Secondary Topics
Audience Stage
Primary Goal
Page Purpose
Recommended Page Type
Required Sections
Questions To Answer
Evidence Requirements
Internal Linking Opportunities
Affiliate Placement Notes If Relevant
Compliance Notes
Publishing Readiness
Recommended Next Action
Human Approval Status
Required Sections
The SEO Content Brief should include:
Content goal
Target reader
Search intent
Page structure
Key headings
Evidence requirements
Internal link targets
CTA direction if relevant
Publishing readiness status
Use When
Use SEO Content Brief when:
A new search-focused page is needed.
The topic supports traffic growth.
The topic supports authority growth.
The content can support affiliate or internal linking goals.
Search intent is clear enough to plan the page.
Do Not Use When
Do not use SEO Content Brief when:
The page already exists and mainly needs fixing.
The offer needs a pre-sell bridge.
The main need is publishing QA.
The main need is repurposing.
Affiliate Pre-Sell Page Brief Template
Use this template when the content should warm the reader before an affiliate offer click-through.
Template Fields
Output Name
Output Type
Source Input
Affiliate Offer
Audience Problem
Audience Stage
Pre-Sell Angle
Belief Shift Needed
Story Or Education Angle
Trust Signals Required
Objections To Handle
Proof Requirements
CTA Direction
Vendor Bridge Alignment
Compliance Risk
Compliance Notes
Recommended Page Structure
Recommended Next Action
Human Approval Status
Required Sections
The Affiliate Pre-Sell Page Brief should include:
Audience problem
Why the offer is relevant
Belief shift
Education or story flow
Trust building
Objection handling
CTA direction
Compliance notes
Use When
Use Affiliate Pre-Sell Page Brief when:
The audience needs warming before vendor click-through.
The offer requires trust building.
The affiliate page needs story, education, or belief shift.
The content supports a campaign or funnel.
Do Not Use When
Do not use Affiliate Pre-Sell Page Brief when:
The page should be a neutral authority article.
The page is mainly a review.
The output is only internal linking.
The page is already written and just needs QA.
Product Review Page Brief Template
Use this template when the output should become a product or offer review.
Template Fields
Output Name
Output Type
Source Input
Product Or Offer Name
Audience Stage
Review Purpose
Problem Solved
Product Summary
Key Benefits
Key Concerns
Who It Is For
Who It Is Not For
Proof Requirements
Claims Requiring Evidence
Comparison Context
CTA Direction
Compliance Risk
Compliance Notes
Recommended Structure
Recommended Next Action
Human Approval Status
Required Sections
The Product Review Page Brief should include:
Product overview
Audience fit
Problem solved
Benefits
Concerns
Evidence requirements
Comparison context
CTA direction
Compliance notes
Use When
Use Product Review Page Brief when:
A single product or affiliate offer is being reviewed.
The audience is near buying decision.
Trust, proof, benefits, and concerns need structure.
Do Not Use When
Do not use Product Review Page Brief when:
The main goal is to compare multiple products.
The page is only educational.
The product does not have enough evidence to discuss safely.
Comparison Page Brief Template
Use this template when the content should compare multiple options, products, methods, tools, or approaches.
Template Fields
Output Name
Output Type
Source Input
Comparison Topic
Options Compared
Audience Stage
Decision Context
Comparison Criteria
Best Fit Logic
Strengths
Weaknesses
Evidence Requirements
Affiliate Notes If Relevant
Internal Link Notes
CTA Direction
Compliance Notes
Recommended Structure
Recommended Next Action
Human Approval Status
Required Sections
The Comparison Page Brief should include:
What is being compared
Why the comparison matters
Who each option fits
Comparison criteria
Strengths and weaknesses
Best-fit recommendation logic
CTA direction
Use When
Use Comparison Page Brief when:
The reader is choosing between options.
The topic has multiple solution paths.
The page can support affiliate or internal linking goals.
Do Not Use When
Do not use Comparison Page Brief when:
There is only one product.
The content should be a simple authority article.
There is not enough evidence to compare fairly.
Listicle Brief Template
Use this template when the content should become a list-style article.
Template Fields
Output Name
Output Type
Source Input
List Topic
List Angle
Audience Stage
Selection Criteria
Number Of Items
Item Structure
Ranking Logic If Needed
Evidence Requirements
Affiliate Placement Notes If Relevant
Internal Link Notes
CTA Direction
Compliance Notes
Recommended Structure
Recommended Next Action
Human Approval Status
Required Sections
The Listicle Brief should include:
List promise
Selection criteria
Item format
Evidence requirements
Internal links
Affiliate placement if relevant
CTA direction
Use When
Use Listicle Brief when:
The topic fits “best”, “top”, “ideas”, “examples”, or “options” style intent.
The reader wants choices.
The site can support traffic, authority, or affiliate goals through the list.
Do Not Use When
Do not use Listicle Brief when:
The topic needs deep authority explanation.
The topic is a single-product review.
The page already exists and mainly needs refresh.
Authority Article Brief Template
Use this template when the content should build topical authority and educate the audience.
Template Fields
Output Name
Output Type
Source Input
Core Topic
Audience Stage
Knowledge Level
Education Goal
Authority Purpose
Required Sections
Questions To Answer
Examples Needed
Evidence Requirements
Internal Linking Opportunities
Related Future Assets
Compliance Notes
Recommended Next Action
Human Approval Status
Required Sections
The Authority Article Brief should include:
Core explanation
Audience knowledge level
Educational flow
Examples
Evidence requirements
Internal links
Related future assets
Use When
Use Authority Article Brief when:
The goal is authority growth.
The page supports a cluster.
The topic helps users understand the field.
The page supports future internal linking.
Do Not Use When
Do not use Authority Article Brief when:
The main purpose is immediate conversion.
The page needs a product review.
The page needs refresh rather than new planning.
Refresh Plan Template
Use this template when an existing page needs improvement.
Template Fields
Output Name
Output Type
Source Input
Existing Page Name
Existing Page URL If Available
Refresh Reason
Current Page Issue
Primary Goal
Audience Stage
Sections To Keep
Sections To Update
Sections To Add
Sections To Remove
Evidence Gaps
Internal Links To Add
CTA Updates
Compliance Issues
Publishing Readiness
Recommended Next Action
Human Approval Status
Required Sections
The Refresh Plan should include:
Why the page needs refresh
What stays
What changes
What gets added
What gets removed
Internal linking updates
Compliance notes
Publishing readiness status
Use When
Use Refresh Plan when:
The page exists.
The page is outdated.
The page is weak but salvageable.
The page has clear improvement potential.
Do Not Use When
Do not use Refresh Plan when:
No page exists.
The page should be replaced completely.
The main need is only repurposing.
Thin Content Expansion Plan Template
Use this template when an existing page lacks depth, usefulness, structure, evidence, or information gain.
Template Fields
Output Name
Output Type
Source Input
Existing Page Name
Thin Content Diagnosis
Missing User Intent
Missing Sections
Missing Examples
Missing Evidence
Missing Trust Signals
Expansion Structure
Internal Link Opportunities
Compliance Notes
Publishing Readiness
Recommended Next Action
Human Approval Status
Required Sections
The Thin Content Expansion Plan should include:
Thin content problem
Intent gap
Missing sections
Expansion outline
Evidence requirements
Internal linking notes
Use When
Use Thin Content Expansion Plan when:
The page exists but is too thin.
The page lacks usefulness.
The page does not satisfy intent.
The page needs depth before publishing or promotion.
Do Not Use When
Do not use Thin Content Expansion Plan when:
The page is already strong.
The main need is a full refresh.
The page should be archived or ignored.
Internal Linking Plan Template
Use this template when the main output should improve site structure and content connectivity.
Template Fields
Output Name
Output Type
Source Input
Linking Goal
Source Pages
Target Pages
Priority Links
Suggested Anchor Direction
Link Purpose
Cluster Relationship
Affiliate Funnel Relationship If Relevant
Links To Avoid
Implementation Notes
Recommended Next Action
Human Approval Status
Required Sections
The Internal Linking Plan should include:
Linking goal
Source and target pages
Priority links
Anchor direction
Cluster role
Implementation notes
Use When
Use Internal Linking Plan when:
Pages are disconnected.
A hub or cluster needs support.
A page needs authority flow.
Affiliate support pages need better traffic flow.
Do Not Use When
Do not use Internal Linking Plan when:
No relevant pages exist.
The main problem is content quality.
The page needs a new brief first.
Repurposing Pack Template
Use this template when an existing asset should be turned into smaller distribution assets.
Template Fields
Output Name
Output Type
Source Input
Source Asset
Repurposing Goal
Audience Stage
Core Message
Social Post Ideas
Email Angles
Short-Form Video Angles
Quote Or Insight Snippets
CTA Direction
Platform Notes If Relevant
Compliance Notes
Recommended Next Action
Human Approval Status
Required Sections
The Repurposing Pack should include:
Core message
Social post ideas
Email angles
Short-form video angles
CTA direction
Compliance notes
Use When
Use Repurposing Pack when:
A strong source asset exists.
The content can support distribution.
The page should create more reach from existing work.
Do Not Use When
Do not use Repurposing Pack when:
The source content is weak.
The page needs refresh first.
The message is not clear enough to repurpose.
Publishing Readiness Checklist Template
Use this template when a page, draft, or asset is close to publishing.
Template Fields
Output Name
Output Type
Source Input
Asset Name
Publishing Status
Title Check
Intent Alignment Check
Structure Check
Evidence Check
Compliance Check
Internal Linking Check
CTA Check
Formatting Check
Mobile / Readability Check
Final Issues
Publishing Decision
Recommended Next Action
Human Approval Status
Required Sections
The Publishing Readiness Checklist should include:
Readiness status
Checks passed
Checks failed
Required fixes
Publishing decision
Use When
Use Publishing Readiness Checklist when:
A draft exists.
A page is close to publishing.
Final human-controlled review is required.
Do Not Use When
Do not use Publishing Readiness Checklist when:
No draft exists.
The page still needs a brief.
The page needs major refresh first.
Content QA Output Template
Use this template when the content needs a quality review.
Template Fields
Output Name
Output Type
Source Input
Asset Name
QA Purpose
Quality Score If Used
Main Issues
Clarity Problems
Trust Gaps
Evidence Gaps
Structure Problems
Content Depth Problems
Compliance Flags
Internal Linking Issues
Recommended Fixes
Recommended Next Action
Human Approval Status
Required Sections
The Content QA Output should include:
Quality verdict
Main issues
Evidence gaps
Trust gaps
Recommended fixes
Next action
Use When
Use Content QA Output when:
The page exists.
The operator needs to know whether it is good enough.
Quality, clarity, trust, structure, usefulness, or compliance is uncertain.
Do Not Use When
Do not use Content QA Output when:
The next action is already clear.
The page needs a specific refresh plan.
No source page exists.
Affiliate Funnel Support Pack Template
Use this template when a content output needs to support a wider affiliate funnel.
Template Fields
Output Name
Output Type
Source Input
Affiliate Offer
Funnel Stage
Audience Stage
Primary Funnel Goal
Required Content Assets
Pre-Sell Asset Need
Review Page Need
Comparison Page Need
Email Support Need
Repurposing Support Need
Internal Linking Support Need
Compliance Risk
CTA Direction
Recommended Asset Priority
Recommended Next Action
Human Approval Status
Required Sections
The Affiliate Funnel Support Pack should include:
Offer context
Funnel stage
Required supporting assets
Asset priority
CTA direction
Compliance notes
Next action
Use When
Use Affiliate Funnel Support Pack when:
Multiple assets are needed around an offer.
The offer needs funnel support.
Content must connect to ads, pre-sell, review, email, or retargeting.
Do Not Use When
Do not use Affiliate Funnel Support Pack when:
Only one simple content asset is needed.
The offer is not ready.
The compliance risk is too high without review.
Template Output Quality Standard
Every output template must produce a clear next action.
A good output says:
Here is what this should become.
Here is why.
Here is what needs to be included.
Here is what must be checked.
Here is what happens next.
A poor output says:
This may be useful.
More review is needed.
There are some opportunities.
Consider improving the content.
The Content Brain output must be specific enough to act on.
Manual Workflow Boundary
At v1.0, these templates support manual workflow.
Allowed:
Create structured briefs
Create plans
Create checklists
Create packs
Create QA outputs
Create readiness reviews
Recommend next action
Not approved by this page:
Full article generation
Automatic publishing
Automatic routing
Automatic queue creation
Automatic AI Employee execution
Automatic worker execution
Automatic cross-brain task wiring
These future layers may be added later after approval.
Supabase Future Field Alignment
These templates may later inform Supabase output records.
Possible future table fields:
id
created_at
updated_at
source_name
source_type
source_record_id
output_type
primary_goal
audience_stage
existing_asset_status
compliance_risk
evidence_status
publishing_readiness
human_approval_status
recommended_next_action
output_body
review_notes
status
migration_status
This page does not approve building the Supabase output table.
It only defines the template and field standard that could support it later.
Plugin UI Future Alignment
These templates may later inform plugin UI screens.
Possible future screens:
Output Style Selector
Create Output Brief
Refresh Plan Builder
Content QA Review
Publishing Readiness Review
Repurposing Pack Builder
Affiliate Funnel Support Planner
This page does not approve building the plugin UI screens.
It only defines the output structure those screens should follow later.
Success Criteria
This standard is successful when:
Each Content Brain output has a predictable structure.
The operator can act on the output.
The selected output type is clear.
The next action is clear.
The source input is clear.
Evidence gaps are visible.
Compliance risks are visible.
Human approval status is visible.
Content Brain feels like a content department.
Failure Conditions
This standard has failed if:
Outputs are vague.
Outputs look like research summaries only.
Outputs do not recommend a next action.
Outputs do not identify the source input.
Outputs skip compliance risk.
Outputs skip publishing readiness.
Outputs become full content generation without approval.
Outputs create more WordPress test-page bloat.
Outputs do not help content production.
Operating Principle
A Content Brain output should be structured enough to become action.
It should not be a loose note.
It should not be only a research summary.
It should not be only a record.
It should be a usable content pathway.
Final Rule
The Content Brain Output Templates And Field Standard defines the required structure for Content Brain’s first manual output types.
Every Content Brain output must identify the source, output type, goal, audience stage, evidence needs, compliance risk, publishing readiness, human approval status, and recommended next action.
Content Brain outputs must be specific, structured, and action-ready.
Version: v1.0
Date: 2026-06-11
Author: HeadOffice
Change:
Added Content Brain Output Templates And Field Standard as the template and field structure layer for Content Brain’s first manual output types.
This page defines the required fields and template logic for SEO Content Briefs, Affiliate Pre-Sell Page Briefs, Product Review Page Briefs, Comparison Page Briefs, Listicle Briefs, Authority Article Briefs, Refresh Plans, Thin Content Expansion Plans, Internal Linking Plans, Repurposing Packs, Publishing Readiness Checklists, Content QA Outputs, and Affiliate Funnel Support Packs.
Change Impact Declaration
Pages Created:
Content Brain Output Templates And Field Standard
Pages Updated:
None
Pages Deprecated:
None
Standalone Pages Not Created:
Content Brain SEO Content Brief Output Template
Content Brain Affiliate Pre-Sell Page Brief Template
Content Brain Refresh Plan Template
Content Brain Publishing Readiness Output Template
Content Brain Repurposing Pack Template
Content Brain Affiliate Funnel Support Pack Template
Content Brain Output Supabase Field Schema
Content Brain Output Plugin UI Build Pack
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 layer strengthened with a reusable template and field standard. This prevents each output style from becoming a separate unnecessary WordPress page while giving Content Brain a consistent structure for manual briefs, plans, checklists, packs, QA outputs, and publishing readiness reviews.