Brain Name: Content Brain
Document Type: Active Reference Framework
Status: Active Reference Framework
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, Content Brain Site Content Intelligence Framework, Content Brain Site Content Intelligence Report Generator Specification, Content Brain Publishing Readiness, Content Brain Content Briefs, Content Brain SEO Content Briefs, Content Brain Affiliate Content Packs, Content Brain Affiliate Funnel Support, Content Brain Refresh, Content Brain Repurposing, Content Brain Internal Linking, Content Brain Publishing Readiness Status Values Framework, Manual Workflow Tests 1 to 10, future Content Brain report generation, future content evidence labelling, future offer evidence review, future claim risk review, future Search Intelligence routing, future Research Brain routing, future Compliance Brain routing, future Affiliate Brain routing, and future Content Brain build readiness planning
Parent: Content Brain
Last Reviewed: 2026-06-08
Content Brain Source Depth And Evidence Label Framework
Purpose
The purpose of this page is to define how Content Brain labels the depth and reliability of source evidence used during manual content planning, site intelligence reviews, affiliate content support, refresh work, publishing readiness checks, and future specification candidate planning.
This page exists because Content Brain must not treat all evidence as equal.
A quick surface review is not the same as a full supplied source review.
A visible website scan is not the same as reviewing source documents.
A VSL impression is not the same as validated offer evidence.
A user supplied note is not the same as independent research.
A claim seen on a sales page is not the same as a verified claim.
This page creates controlled manual language for describing evidence depth.
This page does not authorise build work.
This page does not create plugin instructions.
This page does not create UI instructions.
This page does not create Supabase instructions.
This page does not create Brain Room routing instructions.
This page does not create automation instructions.
This page does not create queue instructions.
This page does not create dashboard instructions.
This page does not create generator instructions.
This page does not create AI Employee instructions.
This page does not create M handoff instructions.
This page exists to improve manual judgement before Content Brain creates, refreshes, repurposes, links, briefs, approves, or routes content.
Current Status
Current Content Brain status:
Manual Workflow Only
Plugin UI Not Started
No Supabase Work Started
No Brain Room Routing Started
No Automation Started
No Queue Build Started
No Dashboard Build Started
No Generator Build Started
No AI Employee Build Started
No Cross Brain Routing Build Started
M’s Active Build Work Untouched
Current evidence stage:
Manual Workflow Evidence Stage
Current planning stage:
Build Readiness Planning Stage
Current page role:
Active Reference Framework
Current maturity status:
Workflow usable
Evidence backed
Manual ready
Site aware
Source depth labels need standardisation
Offer evidence labels need standardisation
Claim evidence labels need standardisation
Future field logic not authorised
Future UI not authorised
Future generator not authorised
Future M handoff not authorised
This page is a manual reference framework only.
Why This Page Is Needed
Content Brain works across many different evidence situations.
Sometimes the operator has full page content.
Sometimes the operator only has a title or page list.
Sometimes the operator has a visible website.
Sometimes the operator has a transcript.
Sometimes the operator has a product sales page.
Sometimes the operator has a VSL summary.
Sometimes the operator has a course file.
Sometimes the operator has a newsletter.
Sometimes the operator has a user supplied description.
Sometimes the operator has verified research.
Sometimes the operator has only weak signals.
Without source depth labels, Content Brain may accidentally overstate confidence.
This creates risk.
It may lead to:
unsupported claims
weak publishing decisions
bad affiliate content
thin content
duplicate content
poor compliance routing
overconfident recommendations
wrong Brain routing
false build readiness
weak HeadOffice decisions
confusing future specifications
Source depth labels protect Content Brain from pretending shallow evidence is deep evidence.
Core Principle
Content Brain must label how deeply evidence has been reviewed before using it to make content decisions.
The stronger the source depth, the more confidence Content Brain can place in the recommendation.
The weaker the source depth, the more cautious Content Brain must be.
A source depth label does not guarantee truth.
A source depth label only explains how much evidence was reviewed.
Evidence depth and evidence quality are related, but they are not the same.
A deep review of poor evidence may still require caution.
A shallow review of strong evidence may still need deeper checking.
Content Brain must label both depth and risk where possible.
Source Depth Label Rules
Source depth labels should be:
clear
short
consistent
easy to understand
manual workflow friendly
safe for future field planning
compatible with publishing readiness
compatible with site intelligence reports
compatible with affiliate content packs
compatible with compliance routing
compatible with Research Brain routing
compatible with Search Intelligence routing
compatible with future Content Brain specification planning
Source depth labels should not be:
vague
overconfident
treated as proof by themselves
treated as final validation
treated as final approval
treated as database fields yet
treated as UI labels yet
treated as automation triggers yet
treated as M build instructions
These labels are manual operating language only until HeadOffice approves later build work.
Primary Source Depth Labels
Use the following source depth labels across Content Brain manual work.
Surface Review
Meaning:
Only a light or partial review was completed.
Use when:
only a title was reviewed
only a page list was reviewed
only a short excerpt was reviewed
only a screenshot was reviewed
only visible surface information was reviewed
only summary level information was available
the operator has not opened the source deeply
Do not use when:
full source material was reviewed
multiple pages were reviewed
the source was directly supplied and analysed
Typical confidence level:
Low
Typical next action:
Do not make strong claims.
Use cautious recommendations.
Request deeper source review if the decision matters.
Basic Site Review
Meaning:
A limited but useful review of visible site pages was completed.
Use when:
several visible pages were reviewed
site purpose was reasonably identified
site tone was observed
some topic coverage was reviewed
some content gaps were identified
the review was useful but not exhaustive
Do not use when:
only one page was reviewed
a full inventory was completed
private analytics or backend data was reviewed
Typical confidence level:
Low to medium
Typical next action:
Use for early site intelligence, but do not treat as a full audit.
Multi Page Site Review
Meaning:
Multiple site pages were reviewed enough to identify stronger patterns.
Use when:
a range of pages was reviewed
site tone patterns are clearer
topic coverage is clearer
internal linking patterns are clearer
content gaps are more reliable
refresh opportunities are more visible
Do not use when:
only a few surface pages were checked
the operator only reviewed page titles
the review did not include meaningful content inspection
Typical confidence level:
Medium
Typical next action:
Use for stronger site intelligence recommendations, but still apply caution for claims and SEO validation.
Full Supplied Page Review
Meaning:
The operator supplied full page content and Content Brain reviewed it directly.
Use when:
the full text of a page was supplied
the page was reviewed in detail
structure, tone, claims, links, gaps, and next steps were assessed
Do not use when:
only a screenshot or title was supplied
only page metadata was reviewed
only a summary was reviewed
Typical confidence level:
Medium to high
Typical next action:
Use for stronger content refresh, publishing readiness, or brief planning decisions.
Source Material Review
Meaning:
Relevant source materials were reviewed directly.
Use when:
documents were reviewed
transcripts were reviewed
course notes were reviewed
uploaded source files were reviewed
manual evidence logs were reviewed
research material was reviewed
Do not use when:
source material was only mentioned but not reviewed
only a summary was available
the source was not directly inspected
Typical confidence level:
Medium to high depending on source quality
Typical next action:
Use to support stronger recommendations, but label any remaining evidence gaps.
Offer Page Review
Meaning:
An affiliate offer page, sales page, product page, or VSL support page was reviewed.
Use when:
offer messaging was reviewed
sales page claims were reviewed
product positioning was reviewed
affiliate support needs were reviewed
offer education gaps were reviewed
VSL transition needs were reviewed
Do not use when:
only the offer name was known
only affiliate network data was available
only a second hand summary was available
Typical confidence level:
Medium for offer messaging
Low to medium for truth of claims
Typical next action:
Use for offer support planning, but do not treat sales page claims as verified evidence.
VSL Claim Review
Meaning:
VSL claims, implied claims, or VSL support context were reviewed.
Use when:
VSL transcript was reviewed
VSL claim summary was reviewed
VSL angles were reviewed
VSL mechanism was reviewed
VSL proof structure was reviewed
VSL transition needs were reviewed
Do not use when:
the VSL was not reviewed
only the sales page was reviewed
only the offer name was known
Typical confidence level:
Medium for claim identification
Low to medium for claim truth
Typical next action:
Route claim sensitive items to Compliance Brain or Research Brain if needed.
User Supplied Context
Meaning:
The operator provided context manually.
Use when:
the user described the site
the user described the offer
the user described past tests
the user described page purpose
the user supplied task instructions
the user supplied background knowledge
Do not use when:
the information came from verified source files
the information came from direct research
the information came from reviewed page content
Typical confidence level:
Useful but requires caution
Typical next action:
Use as working context but label unsupported claims clearly.
Manual Workflow Evidence
Meaning:
The evidence comes from prior manual Content Brain workflow testing.
Use when:
Manual Workflow Test Log was used
Manual Workflow Synthesis Report was used
Build Readiness Shortlist was used
Content Brain manual test outputs were reviewed
Do not use when:
the evidence is only a general assumption
the workflow was not tested
the evidence was not recorded
Typical confidence level:
Medium to high for workflow usefulness
Typical next action:
Use for build readiness planning, not technical build approval.
Verified External Research
Meaning:
A claim or content decision is supported by reviewed external sources.
Use when:
credible external sources were checked
current data was verified
specific claims were sourced
multiple sources support the claim
the evidence is suitable for content planning
Do not use when:
the source was not reviewed
the source is outdated
the source is weak
the claim comes from sales material only
Typical confidence level:
Medium to high depending on source quality
Typical next action:
Use for stronger content decisions, but still apply publishing and compliance review.
Search Intelligence Required
Meaning:
The evidence is not enough to make a search or SEO decision.
Use when:
search intent is unclear
SERP fit is unknown
keyword cannibalisation may exist
SEO opportunity is uncertain
topic cluster search value is unknown
content gap may not match search demand
Do not use when:
Search Intelligence Brain has already validated the search logic
the content is not search driven
Typical confidence level:
Not enough for SEO decision
Typical next action:
Route to Search Intelligence Brain.
Research Required
Meaning:
The evidence is not enough to support claims or content decisions.
Use when:
facts are unclear
claims are unsupported
audience data is missing
market context is weak
offer claims need verification
source material is missing
external validation is needed
Do not use when:
the source material has already been reviewed
the issue is only wording or structure
Typical confidence level:
Insufficient
Typical next action:
Route to Research Brain.
Compliance Review Required
Meaning:
The evidence or content may contain claim risk or policy sensitive issues.
Use when:
claims need compliance interpretation
health or wellness claims appear
financial or income claims appear
safety claims appear
scarcity or urgency claims appear
testimonial claims appear
comparison claims appear
VSL claims appear
affiliate disclosures are needed
Do not use when:
there is no meaningful claim risk
the issue is only site tone or structure
Typical confidence level:
Insufficient for safe approval
Typical next action:
Route to Compliance Brain or HeadOffice.
Unknown Evidence Depth
Meaning:
The depth of evidence is unclear.
Use when:
the operator does not know what was reviewed
the source trail is unclear
the original evidence is missing
the content came from an unknown source
the page was inherited without clear review history
Do not use when:
the review depth can be clearly labelled
Typical confidence level:
Low
Typical next action:
Do not make strong claims.
Review the source again or park the decision.
Evidence Quality Labels
Source depth explains how much was reviewed.
Evidence quality explains how reliable the evidence appears.
Use these evidence quality labels where helpful.
Strong Evidence
Meaning:
The evidence is direct, relevant, current, and credible.
Use when:
source material directly supports the claim
evidence is recent where recency matters
source is credible
claim is not overstated
multiple supporting signals exist
Caution:
Strong evidence still needs compliance review if the claim is sensitive.
Moderate Evidence
Meaning:
The evidence is useful but incomplete.
Use when:
source material supports the direction
some gaps remain
more detail would improve confidence
the claim should be softened
additional review may be needed before publishing
Caution:
Use cautious wording.
Weak Evidence
Meaning:
The evidence is thin, indirect, outdated, unsupported, or mostly inferred.
Use when:
source is shallow
claim is not directly supported
evidence is old
source is promotional
context is missing
recommendation is mostly judgement based
Caution:
Do not use strong claims.
Route to Research Brain or Compliance Brain if needed.
Unsupported
Meaning:
The claim or recommendation does not yet have enough evidence.
Use when:
claim is not supported by reviewed material
source is missing
evidence is invented or assumed
the operator cannot verify the statement
Caution:
Do not publish.
Do not brief as fact.
Do not use in ad or affiliate content.
Conflicting Evidence
Meaning:
The reviewed evidence points in different directions.
Use when:
sources disagree
site pages contradict each other
offer claims conflict with disclaimers
user context conflicts with source material
old content conflicts with new positioning
Caution:
Route to HeadOffice, Research Brain, Compliance Brain, or Affiliate Brain depending on the issue.
Evidence Label Combination Rule
Content Brain should combine source depth and evidence quality where needed.
Examples:
Surface Review / Weak Evidence
Basic Site Review / Moderate Evidence
Full Supplied Page Review / Strong Evidence
Offer Page Review / Weak Evidence
VSL Claim Review / Compliance Review Required
Manual Workflow Evidence / Moderate Evidence
Verified External Research / Strong Evidence
Unknown Evidence Depth / Unsupported
This combination gives clearer decision context than either label alone.
Confidence Language Rule
Content Brain should adjust language based on evidence depth.
If evidence is shallow, use cautious language such as:
appears to
suggests
may indicate
likely
possible
needs review
requires confirmation
If evidence is strong, Content Brain may use firmer language such as:
confirms
shows
supports
indicates
demonstrates
However, even strong evidence should not be overstated.
Claim sensitive areas still require compliance review.
Source Depth By Workflow
Content Brain Site Content Intelligence Framework
Common labels:
Surface Review
Basic Site Review
Multi Page Site Review
Full Supplied Page Review
Unknown Evidence Depth
Content Brain Site Content Intelligence Report Generator Specification
Common labels:
Basic Site Review
Multi Page Site Review
Full Supplied Page Review
Source Material Review
Offer Page Review
VSL Claim Review
User Supplied Context
Search Intelligence Required
Research Required
Compliance Review Required
Content Brain Content Briefs
Common labels:
Source Material Review
User Supplied Context
Basic Site Review
Research Required
Unknown Evidence Depth
Content Brain SEO Content Briefs
Common labels:
Basic Site Review
Multi Page Site Review
Search Intelligence Required
Verified External Research
Unknown Evidence Depth
Content Brain Affiliate Content Packs
Common labels:
Offer Page Review
VSL Claim Review
User Supplied Context
Source Material Review
Research Required
Compliance Review Required
Content Brain Affiliate Funnel Support
Common labels:
Offer Page Review
VSL Claim Review
Source Material Review
Compliance Review Required
Content Brain Publishing Readiness
Common labels:
Full Supplied Page Review
Source Material Review
Offer Page Review
VSL Claim Review
Compliance Review Required
Unsupported
Conflicting Evidence
Content Brain Refresh
Common labels:
Full Supplied Page Review
Basic Site Review
Multi Page Site Review
Verified External Research
Unknown Evidence Depth
Content Brain Repurposing
Common labels:
Full Supplied Page Review
Source Material Review
User Supplied Context
Compliance Review Required
Content Brain Internal Linking
Common labels:
Basic Site Review
Multi Page Site Review
Full Supplied Page Review
Search Intelligence Required
When Source Depth Must Be Recorded
Source depth should be recorded when:
content includes claims
content supports an affiliate offer
content supports a campaign
content may be published externally
content may be used in ads
content may support a VSL
content involves health, wellness, finance, safety, legal, income, or disaster topics
content is being refreshed
content is being used for publishing readiness
content may be handed to another Brain
content may influence future build planning
content may become a specification candidate
content is based on external website review
content is based on user supplied context only
content has uncertain evidence
Source depth does not need to be recorded for every tiny internal note.
Use judgement.
When Evidence Must Be Escalated
Escalate evidence when:
claim risk exists
source depth is shallow
evidence is unsupported
evidence is conflicting
offer evidence is missing
VSL claims are unclear
compliance sensitivity exists
search validation is needed
Research Brain evidence is required
Affiliate Brain offer logic is unclear
HeadOffice priority is unclear
publishing risk is high
the content may be used in paid traffic
the content may influence a public facing asset
Escalation should go to the correct Brain.
Research Brain owns evidence quality.
Search Intelligence Brain owns search validation.
Affiliate Brain owns offer logic.
Compliance Brain owns compliance interpretation.
HeadOffice owns priority and final direction.
What This Page Must Not Do
This page must not:
replace Research Brain
replace Search Intelligence Brain
replace Compliance Brain
replace Affiliate Brain
replace HeadOffice
treat labels as proof
treat shallow evidence as verified evidence
approve publishing
approve claims
approve affiliate content
approve ad content
approve VSL support content
approve technical build work
create database fields
create UI labels
create automation triggers
create Supabase schema
create M handoff instructions
These labels are for manual judgement and future planning only.
Relationship To Publishing Readiness Status Values Framework
Publishing Readiness Status Values define whether an asset is ready, blocked, parked, or requires another review path.
This Source Depth And Evidence Label Framework defines how strong the evidence behind that decision is.
Together, they help Content Brain say:
what the status is
why that status applies
how deep the evidence review was
whether confidence is strong enough to move forward
Example:
Status:
Needs Source Review
Source Depth:
Surface Review
Evidence Quality:
Weak Evidence
This is much clearer than saying:
Not ready
Relationship To Site Content Intelligence
Site Content Intelligence reviews existing site context.
This framework tells Content Brain how deeply that site was reviewed.
Example:
A page list review should not be labelled as a Multi Page Site Review.
A quick homepage glance should not be treated as a full site intelligence report.
A full supplied page review can support stronger recommendations than a surface review.
This prevents Site Content Intelligence from becoming overconfident.
Relationship To Affiliate Content Packs
Affiliate Product Content Packs often depend on offer evidence.
This framework helps Content Brain distinguish between:
what the sales page claims
what the VSL claims
what the operator supplied
what has been independently verified
what needs Compliance Brain review
what needs Research Brain review
what needs Affiliate Brain review
This prevents affiliate content from treating promotional claims as verified facts.
Relationship To Content Refresh
Content Refresh often depends on knowing whether existing content is outdated, weak, duplicated, unsupported, or risky.
This framework helps label whether the refresh recommendation is based on:
surface review
full supplied page review
source material review
verified external research
unknown evidence depth
This prevents weak refresh recommendations from being treated as final.
Relationship To Future Report Generator
The future Site Content Intelligence Report Generator should eventually include source depth labels.
This framework supplies the manual logic for those labels.
However, this page does not authorise the generator build.
It only supports future planning.
Relationship To Future Fields
This page may later inform future fields such as:
Source Depth Label
Evidence Quality Label
Evidence Risk Level
Evidence Review Notes
Source Review Required
Research Brain Required
Search Intelligence Required
Compliance Review Required
Offer Evidence Required
Claim Evidence Status
These are future field candidates only.
They are not approved database fields.
They are not approved UI fields.
They are not approved Supabase fields.
They are not automation triggers.
Relationship To M Handoff
This page is not an M handoff pack.
Do not give this page to M as implementation instructions.
M should not build from this page.
This page may later support a build ready technical specification if HeadOffice approves that step.
Until then, this page is only manual evidence labelling logic.
Drift Protection
This framework prevents:
overconfident recommendations
unsupported claims
weak evidence being treated as strong evidence
surface reviews being treated as deep reviews
sales page claims being treated as verified facts
VSL claims being used without review
user supplied context being treated as independent evidence
unknown evidence being treated as known evidence
Search Intelligence being bypassed
Research Brain being bypassed
Compliance Brain being bypassed
Affiliate Brain being bypassed
Publishing Readiness being bypassed
claim sensitive content being approved too easily
affiliate content being created without offer evidence
site intelligence reports overstating confidence
future generators being designed without evidence labels
future fields being created before manual logic is stable
M receiving unclear evidence logic
Recommended Next Step
Use this framework manually when Content Brain outputs rely on evidence depth.
Apply source depth labels to:
Site Content Intelligence Reports
Content Briefs
SEO Content Briefs
Affiliate Content Packs
Refresh Reviews
Repurposing Reviews
Publishing Readiness Reviews
Bridge Page Reviews
Landing Page Refresh Reviews
Future Specification Candidate Pages
Do not build UI.
Do not build queues.
Do not build dashboards.
Do not build generators.
Do not build AI Employees.
Do not create Supabase fields.
Do not create database schema.
Do not create M handoff instructions.
Registry update:
Deferred until end of day batch update.
Pending registry entry:
Content Brain Source Depth And Evidence Label Framework
Status:
Active Reference Framework
Version:
v1.0
Parent:
Content Brain
Expected page count impact:
Previous expected page count:
43 pages
New expected page count:
44 pages
Change Impact Declaration
Pages Created:
Content Brain Source Depth And Evidence Label Framework
Pages Updated:
None immediately
Pages Renamed:
None
Pages Deleted:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry at end of day batch update
Canon Version Update Required:
No
Architecture Version Update Required:
No
Manual Workflow Test Log Update Required:
No
Manual Workflow Synthesis Report Update Required:
No
Build Readiness Shortlist Update Required:
No
Plugin UI Impact:
None
Supabase Impact:
None
Brain Room Routing Impact:
None
Automation Impact:
None
Queue Impact:
None
Dashboard Impact:
None
Generator Build Impact:
None
AI Employee Impact:
None
Cross Brain Routing Impact:
None
M Active Build Impact:
None
Page Count Impact:
Previous expected page count:
43 pages
New expected page count:
44 pages
Registry update timing:
Deferred until end of day batch update
Change Log
Version: v1.0
Date: 2026-06-08
Author: HeadOffice
Change:
Created Content Brain Source Depth And Evidence Label Framework as an Active Reference Framework.
Defined controlled source depth labels and evidence quality labels for Content Brain manual workflows.
Added primary source depth labels including Surface Review, Basic Site Review, Multi Page Site Review, Full Supplied Page Review, Source Material Review, Offer Page Review, VSL Claim Review, User Supplied Context, Manual Workflow Evidence, Verified External Research, Search Intelligence Required, Research Required, Compliance Review Required, and Unknown Evidence Depth.
Added evidence quality labels including Strong Evidence, Moderate Evidence, Weak Evidence, Unsupported, and Conflicting Evidence.
Added evidence label combination rule, confidence language rule, source depth by workflow, when source depth must be recorded, when evidence must be escalated, relationship to Publishing Readiness Status Values Framework, relationship to Site Content Intelligence, relationship to Affiliate Content Packs, relationship to Content Refresh, relationship to future report generator, relationship to future fields, relationship to M handoff, drift protection, recommended next step, and change impact declaration.
Confirmed this page does not authorise plugin UI, Supabase, Brain Room routing, automation, queues, dashboards, generators, AI Employees, cross brain routing, or M implementation handoff.
End Of Day Save Point Template
Page list checked:
Yes / No
Content Brain Site Content Intelligence Report Generator Specification created:
Yes / No
Content Brain Publishing Readiness Status Values Framework created:
Yes / No
Content Brain Source Depth And Evidence Label Framework created:
Yes / No
Content Brain Page Registry updated today:
Yes / No
Registry update deferred:
Yes / No
Pages created:
Content Brain Site Content Intelligence Report Generator Specification
Content Brain Publishing Readiness Status Values Framework
Content Brain Source Depth And Evidence Label Framework
Pages updated:
None / Content Brain Page Registry if updated at closeout
Pages renamed:
None
Pages deleted:
None
Current expected page count:
44 pages / other
No plugin UI started:
Yes / No
No Supabase work started:
Yes / No
No Brain Room routing started:
Yes / No
No automation started:
Yes / No
No queue work started:
Yes / No
No dashboard work started:
Yes / No
No generator build started:
Yes / No
No AI Employee work started:
Yes / No
No cross brain routing started:
Yes / No
M’s active work untouched:
Yes / No
Target save point:
Content Brain — Source Depth And Evidence Label Framework Created / Registry Update Deferred / Build Readiness Planning Stage / Manual Workflow Only / Plugin UI Not Started
Final Rule
Content Brain must label evidence depth when source strength matters.
Do not treat a surface review as a deep review.
Do not treat sales page claims as verified facts.
Do not treat user supplied context as independent evidence.
Do not treat unknown evidence as known evidence.
Do not use strong claims when the source depth is weak.
Use source depth labels to protect content quality, publishing readiness, affiliate safety, compliance routing, and future build readiness.
These labels are manual operating language only.
They are not build approval.
END CONTENT BRAIN SOURCE DEPTH AND EVIDENCE LABEL FRAMEWORK v1.0