Brain Name: Content Brain
Document Type: Active Reference Framework
Status: Active Reference Framework
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, Content Brain Affiliate Content Packs, Content Brain Affiliate Funnel Support, Content Brain Publishing Readiness, Content Brain Content Briefs, Content Brain SEO Content Briefs, Content Brain Refresh, Content Brain Repurposing, Content Brain Site Content Intelligence Framework, Content Brain Site Content Intelligence Report Generator Specification, Content Brain Publishing Readiness Status Values Framework, Content Brain Source Depth And Evidence Label Framework, affiliate offer content planning, VSL support content, bridge page review, landing page refresh review, offer evidence review, claim risk review, Compliance Brain routing, Affiliate Brain routing, Research Brain routing, and future Content Brain build readiness planning
Parent: Content Brain
Last Reviewed: 2026-06-08
Content Brain Offer Evidence Requirements Framework
Purpose
The purpose of this page is to define what offer evidence Content Brain needs before creating, refreshing, repurposing, approving, or routing affiliate offer support content.
This page exists because Content Brain must not create affiliate content from weak, missing, promotional, or unverified offer information.
Affiliate content is more sensitive than ordinary educational content.
It often involves:
product claims
VSL claims
mechanism claims
benefit claims
testimonial claims
comparison claims
urgency claims
scarcity claims
guarantee claims
price claims
income claims
health claims
wellness claims
safety claims
proof claims
reader expectation setting
ad to page match
bridge page trust
affiliate disclosures
Content Brain needs a clear standard for identifying what offer evidence exists, what is missing, what is risky, and what must be routed to another Brain before content moves forward.
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 offer evidence review before Content Brain creates or approves affiliate 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
Affiliate support tested
Bridge page refresh tested
Landing page refresh tested
Offer evidence logic needs 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 supports affiliate campaigns, bridge pages, product content packs, VSL support content, SEO content, refresh work, and publishing readiness decisions.
Many of these workflows depend on offer evidence.
If offer evidence is weak, Content Brain may accidentally create content that:
overstates the offer
misrepresents the mechanism
copies vendor claims without review
uses unsafe claims
creates compliance risk
sets the wrong reader expectation
creates poor ad to page match
pushes product too early
creates weak trust
creates unsupported comparison content
uses testimonials incorrectly
ignores affiliate disclosure needs
routes content incorrectly
treats promotional material as verified evidence
Content Brain must know the difference between:
what the offer says
what the VSL says
what the affiliate page says
what the vendor proves
what the user supplied
what has been independently verified
what still needs review
Core Principle
Content Brain must not treat offer claims as verified facts.
An offer page is evidence of how the vendor markets the offer.
It is not automatically proof that the claim is true.
A VSL is evidence of the offer’s sales message.
It is not automatically independent evidence.
A testimonial is evidence of a claimed customer experience.
It is not automatically general proof.
A guarantee is evidence of a vendor promise.
It is not automatically proof of product performance.
Content Brain may use offer evidence to understand positioning, reader expectations, funnel logic, and support content needs.
Content Brain must not use weak offer evidence to create strong claims.
Offer Evidence Review Rule
Before Content Brain creates or approves affiliate offer support content, it should identify:
what offer evidence is available
what offer evidence is missing
what claims appear in the offer
what claims appear in the VSL
what claims are sensitive
what claims need source review
what claims need compliance review
what claims should be softened
what disclosures may be needed
what content can safely be created
what content should be parked
what should be routed to another Brain
This protects Content Brain from building content around unsafe or unsupported offer assumptions.
Primary Offer Evidence Categories
Use the following categories when reviewing affiliate offer evidence.
Offer Identity Evidence
This identifies the basic offer.
Required where possible:
offer name
vendor name
affiliate network
offer URL
affiliate URL where relevant
sales page URL
VSL URL where relevant
product category
niche
primary audience
primary promise
primary mechanism
primary call to action
affiliate disclosure requirement
Use this evidence to identify what offer is being discussed.
Do not use identity evidence as proof of claims.
Vendor Evidence
This identifies who is behind the offer.
Useful evidence may include:
vendor name
company name
brand name
public website
support details
refund policy
guarantee policy
contact details
affiliate resource page
vendor history where known
known rebrands where known
Use this evidence to understand trust and accountability.
If vendor evidence is missing, Content Brain should avoid strong trust language.
Offer Page Evidence
This identifies what the sales page says.
Useful evidence may include:
headline
subheadline
primary promise
product explanation
mechanism explanation
benefit claims
proof claims
testimonials
guarantee language
price language if approved for use
urgency or scarcity language
CTA language
disclaimers
FAQ content
risk reversal
comparison language
Use this evidence to understand sales message and reader expectation.
Do not treat offer page claims as independently verified facts.
VSL Evidence
This identifies what the VSL says or implies.
Useful evidence may include:
VSL hook
opening problem
mechanism claim
story arc
scientific claims
expert claims
testimonial claims
proof stack
fear or urgency language
before and after implications
viewer expectation
CTA transition
purchase promise
disclaimers
compliance sensitive language
Use this evidence to understand how the offer persuades.
Do not copy VSL claims into Content Brain assets without source depth review and compliance judgement.
Mechanism Evidence
This identifies how the offer claims to work.
Useful evidence may include:
stated mechanism
ingredient or component explanation
process explanation
method explanation
technology explanation
training method
system method
routine or protocol
scientific explanation
unique mechanism claim
reason why it works
Use this evidence carefully.
If the mechanism is unverified, use cautious language.
If the mechanism is health, wellness, finance, legal, safety, or income related, route to Compliance Brain or Research Brain before using strong claims.
Benefit Evidence
This identifies what outcome the offer claims to support.
Useful evidence may include:
primary benefit
secondary benefits
speed of result
ease of use
effort required
time required
audience fit
problem solved
pain point addressed
transformation promised
limitations
qualifiers
disclaimers
Use benefit evidence to plan content support.
Do not overstate benefits.
Do not remove qualifiers.
Do not turn possibility into certainty.
Proof Evidence
This identifies what proof the offer uses.
Useful evidence may include:
case studies
testimonials
reviews
demonstrations
screenshots
expert endorsements
scientific references
media mentions
before and after examples
data points
user numbers
vendor claims
guarantee details
disclosures
Use proof evidence with caution.
Promotional proof should not be treated as independent proof.
If proof is weak, label it as weak.
If proof is sensitive, route to Compliance Brain.
Risk And Disclaimer Evidence
This identifies limitations, warnings, and compliance context.
Useful evidence may include:
earnings disclaimers
health disclaimers
medical disclaimers
financial disclaimers
results not typical notes
affiliate disclosures
refund terms
guarantee conditions
eligibility limits
age restrictions
regional restrictions
usage limitations
safety warnings
privacy notes
terms and conditions
Content Brain must preserve important disclaimers and limitations.
Do not create content that removes or hides risk context.
Audience Evidence
This identifies who the offer is for.
Useful evidence may include:
target audience
awareness stage
problem stage
buyer stage
skill level
experience level
age range if relevant and safe
location if relevant
pain points
objections
desires
beliefs
urgency level
financial capacity where relevant
Use audience evidence to plan content tone and content support.
Do not invent audience traits.
Do not target sensitive traits irresponsibly.
Funnel Evidence
This identifies how the offer fits into the funnel.
Useful evidence may include:
ad angle
pre sell angle
bridge page
landing page
VSL transition
email follow up
retargeting path
affiliate content pack
comparison page
FAQ page
trust support page
objection handling page
upsell or backend path where known
Use funnel evidence to support reader journey and message match.
If funnel evidence is missing, Content Brain should avoid assuming the right content path.
Required Minimum Evidence By Content Type
Different content types need different evidence depth.
General Educational Content
Minimum evidence needed:
topic
audience
site context where relevant
source depth label
claim sensitivity check
Required before publishing:
Publishing Readiness review
Affiliate Soft Support Content
Minimum evidence needed:
offer name
offer category
audience problem
general offer role
affiliate disclosure awareness
claim sensitivity check
Required before publishing:
Offer evidence review
Publishing Readiness review
Compliance review if claims appear
Affiliate Product Content Pack
Minimum evidence needed:
offer identity
vendor or network context
sales page or VSL context
primary promise
audience
mechanism summary
benefit claims
proof evidence
risk or disclaimer notes
content support gaps
claim risk notes
Required before use:
Affiliate Brain review if offer logic is unclear
Research Brain review if evidence is missing
Compliance Brain review if claims are sensitive
Publishing Readiness review before public use
Affiliate Bridge Page
Minimum evidence needed:
ad angle
offer promise
VSL transition
reader awareness stage
claim sensitivity
CTA expectation
affiliate disclosure requirement
proof support
risk language
Required before use:
Ad to page match review
Offer evidence review
Compliance review if claims or urgency appear
Publishing Readiness review
HeadOffice approval where campaign sensitive
VSL Support Content
Minimum evidence needed:
VSL hook
VSL promise
VSL mechanism
VSL claim set
VSL proof structure
VSL CTA
VSL disclaimers
viewer expectation
Required before use:
VSL claim review
Compliance review
Affiliate Brain review if offer logic is unclear
Publishing Readiness review
Comparison Content
Minimum evidence needed:
offer identity
comparison target
comparison criteria
source evidence for each comparison point
disclosure requirements
claim sensitivity
fairness notes
Required before use:
Research Brain review where facts are uncertain
Compliance Brain review where claims are sensitive
Publishing Readiness review
Content Refresh For Affiliate Page
Minimum evidence needed:
existing page content
current offer context
current VSL context if relevant
claim risk review
outdated claims
unsupported claims
reader journey notes
internal linking notes
Required before use:
Refresh review
Offer evidence review
Compliance review where needed
Publishing Readiness review
Offer Evidence Status Values
Use these status values during manual Content Brain workflows.
Offer Evidence Complete Enough For Planning
Meaning:
Enough evidence exists to plan content manually.
This does not mean content is approved for publishing.
Use when:
offer identity is clear
audience is clear
primary promise is clear
basic claims are visible
source depth is labelled
risk areas are noted
next workflow is clear
Offer Evidence Incomplete
Meaning:
Key offer information is missing.
Use when:
offer name is unclear
vendor is unclear
affiliate network is unclear
sales page is missing
VSL context is missing
mechanism is unclear
proof is missing
disclaimers are missing
Do not create strong affiliate content until resolved.
Offer Claims Need Review
Meaning:
Offer claims exist but need source or compliance review.
Use when:
claims are strong
claims are sensitive
claims are promotional
claims lack proof
claims may be exaggerated
claims appear in VSL or sales page only
Route to Research Brain or Compliance Brain.
Offer Proof Weak
Meaning:
The offer uses proof, but the proof is not strong enough to support strong content claims.
Use when:
proof is testimonial only
proof is vendor supplied only
proof lacks details
proof is unclear
proof is not independently verified
Use cautious language.
Do not create strong proof claims.
Offer Context Suitable For Soft Content Only
Meaning:
Content can discuss the general problem, audience education, or pre sell context, but should not make strong offer claims.
Use when:
offer evidence is incomplete
claim risk exists
proof is weak
mechanism is unclear
but the general topic is still useful
Use for educational or problem aware content only.
Offer Not Ready For Content
Meaning:
Content Brain should not create offer support content yet.
Use when:
offer identity is unclear
claims are risky
evidence is missing
compliance risk is high
VSL context is unknown
disclosure requirements are unclear
the offer may not be suitable
Park or route to another Brain.
Offer Evidence Escalation Required
Meaning:
The offer requires review by another Brain before content continues.
Use when:
Affiliate Brain needs to validate offer logic
Research Brain needs to validate evidence
Compliance Brain needs to review claims
HeadOffice needs to decide priority
Do not move forward until escalation is resolved.
Claim Strength Rules
Content Brain must match claim strength to evidence strength.
If evidence is weak, use soft language.
Soft language may include:
may help
may support
designed to
intended to
aims to
can help some people
could be useful for
is positioned as
the vendor claims
the offer presents itself as
Avoid strong language unless evidence is strong and approval is clear.
Do not say:
proves
guarantees
will
always
cures
fixes
eliminates
scientifically proven
risk free
works for everyone
instant
effortless
no fail
guaranteed results
unless the claim is properly supported, compliant, and approved.
Offer Claim Risk Categories
The following claim categories require caution.
Health And Wellness Claims
Examples:
pain relief
weight loss
mental health
energy
sleep
blood sugar
menopause
inflammation
disease related claims
medical adjacent claims
Required action:
Compliance review and evidence review.
Financial And Income Claims
Examples:
make money
passive income
profit
ROI
business growth
investment returns
debt relief
credit improvement
Required action:
Compliance review and evidence review.
Performance Claims
Examples:
works faster
best
highest converting
guaranteed
proven system
high success rate
Required action:
Evidence review and claim softening.
Safety Claims
Examples:
safe
risk free
protects
prevents harm
emergency ready
disaster proof
Required action:
Compliance review.
Comparison Claims
Examples:
better than
safer than
cheaper than
more effective than
beats competitors
Required action:
Research review and fairness review.
Scarcity And Urgency Claims
Examples:
limited time
urgent
before it is too late
act now
last chance
Required action:
Compliance and platform safety review.
Testimonial Claims
Examples:
customer results
personal stories
before and after
unusual outcomes
Required action:
Disclaimer and representativeness review.
Evidence Routing Rules
Route to Affiliate Brain when:
offer logic is unclear
offer fit is unclear
commission model matters
affiliate network details matter
VSL to offer relationship is unclear
offer lifecycle status matters
offer risk needs affiliate evaluation
Route to Research Brain when:
claims need evidence
market context is unclear
audience facts are missing
scientific or factual support is needed
comparison points need validation
external sources are required
Route to Compliance Brain when:
claim risk exists
health, wellness, finance, safety, legal, or income claims appear
urgency or scarcity may be risky
testimonial use is unclear
affiliate disclosure requirements are unclear
platform policy risk exists
Route to Search Intelligence Brain when:
SEO intent is unclear
keyword opportunity is uncertain
SERP fit matters
comparison search terms matter
topic cluster search demand matters
Route to HeadOffice when:
priority is unclear
offer should be rejected or parked
content direction affects strategy
build readiness decisions are involved
cross brain authority is unclear
the operator needs final direction
Offer Evidence Review Process
Step 1: Identify Offer
Record:
offer name
vendor
network
offer URL
sales page
VSL where relevant
niche
audience
primary promise
Step 2: Identify Source Depth
Label the evidence using the Source Depth And Evidence Label Framework.
Examples:
Offer Page Review
VSL Claim Review
User Supplied Context
Source Material Review
Unknown Evidence Depth
Step 3: Extract Main Claims
Record:
primary promise
mechanism
benefits
proof claims
testimonial claims
urgency claims
guarantee claims
comparison claims
disclaimer language
Step 4: Identify Missing Evidence
Check whether missing evidence affects content safety.
Missing evidence may include:
vendor proof
mechanism support
claim support
VSL details
disclaimers
affiliate disclosure
audience fit
price or guarantee details
Step 5: Classify Claim Risk
Classify risk as:
Low Risk
Moderate Risk
High Risk
Compliance Review Required
Step 6: Decide Content Permission
Choose one:
Offer Evidence Complete Enough For Planning
Offer Evidence Incomplete
Offer Claims Need Review
Offer Proof Weak
Offer Context Suitable For Soft Content Only
Offer Not Ready For Content
Offer Evidence Escalation Required
Step 7: Route If Needed
Route to the correct Brain if the evidence is not enough.
Step 8: Record Next Manual Step
Possible next steps:
create soft educational content
create content brief
create affiliate content pack
refresh existing page
route to Affiliate Brain
route to Research Brain
route to Compliance Brain
route to HeadOffice
park offer content
do not use offer claims
What Content Brain Can Safely Do With Limited Offer Evidence
When offer evidence is limited, Content Brain may still be able to create:
problem awareness content
general education content
neutral topic explanation
reader question lists
content gap notes
site intelligence notes
internal planning notes
soft pre sell structure
claim safe FAQ draft
research request
compliance review request
Affiliate Brain review request
Content Brain should avoid:
strong product claims
hard recommendations
comparison claims
guaranteed outcomes
strong CTA pressure
testimonial based persuasion
unsupported mechanism explanations
VSL claim repetition
sensitive claims
What Content Brain Must Not Do With Weak Offer Evidence
Content Brain must not:
invent proof
invent testimonials
invent mechanisms
invent vendor credibility
invent scientific backing
invent user results
invent refund details
invent guarantee terms
invent price details
invent urgency
invent scarcity
invent authority
invent customer numbers
invent success rates
invent comparison facts
copy strong VSL claims without review
turn vendor claims into verified facts
remove disclaimers
hide affiliate context
push readers toward an offer without proper context
Offer Evidence And Publishing Readiness
Publishing readiness must check offer evidence before public use.
If offer evidence is incomplete, Publishing Readiness should use one of these statuses:
Needs Offer Evidence
Needs Source Review
Needs Compliance Review
Ready For HeadOffice Review
Do Not Use
Offer content should not receive Approved For Next Manual Step unless the next step is clearly defined and safe.
Approved For Next Manual Step does not mean approved for publishing.
Offer Evidence And Site Content Intelligence
Site Content Intelligence may identify affiliate support gaps.
However, affiliate support gaps do not automatically mean new affiliate content should be created.
Site Content Intelligence should check:
does the site already support the offer
does the site have trust content
does the site have problem awareness content
does the site have product education content
does the site have comparison content
does the site have disclosure clarity
does the site have internal link support
does the site have enough evidence to support offer claims
If offer evidence is missing, route before creating strong affiliate content.
Offer Evidence And Affiliate Product Content Packs
Affiliate Product Content Packs should not be built on weak offer evidence.
Before creating a full content pack, Content Brain should know:
what the offer is
who the audience is
what the promise is
what the mechanism is
what proof exists
what risks exist
what claims are safe
what claims need review
what supporting content is needed
what content should not be created yet
If this evidence is incomplete, create a partial planning pack or route to Affiliate Brain, Research Brain, Compliance Brain, or HeadOffice.
Offer Evidence And Bridge Page Review
Bridge pages require extra care because they connect paid or organic traffic to a VSL or offer.
Bridge page evidence should include:
ad angle
headline promise
page promise
VSL promise
CTA destination
reader expectation
claim risk
curiosity level
urgency level
disclosure needs
offer evidence status
A bridge page may be structurally strong but still not ready if offer evidence is weak.
Offer Evidence And VSL Support
VSL support content must preserve accurate expectation setting.
Content Brain should not:
oversell the VSL
restate strong claims without review
make the VSL sound more proven than it is
hide limitations
create false curiosity
create misleading urgency
promise outcomes before the viewer sees the VSL
VSL support content should prepare the reader honestly.
Offer Evidence And Compliance Brain
Compliance Brain should be involved when offer claims may create policy or legal risk.
Content Brain should not wait until final publishing review if obvious compliance risk appears early.
Compliance routing should happen as soon as risk is identified.
Offer Evidence And Research Brain
Research Brain should be involved when factual support is needed.
Content Brain should route to Research Brain when:
claims need verification
market context is unclear
evidence is missing
comparison content needs facts
scientific references are needed
audience claims need support
Search results or external sources are required
Offer Evidence And Affiliate Brain
Affiliate Brain should be involved when offer logic matters.
Content Brain should route to Affiliate Brain when:
offer viability is unclear
offer positioning is unclear
commission or funnel structure matters
audience fit is unclear
offer lifecycle risk exists
affiliate content pack depends on offer strategy
offer should possibly be rejected or parked
Offer Evidence And HeadOffice
HeadOffice should be involved when the decision is strategic.
Route to HeadOffice when:
priority is unclear
offer is risky
content direction affects campaign strategy
offer should be accepted, parked, or rejected
cross brain authority is unclear
manual decision confidence is low
future build readiness implications exist
Relationship To Source Depth And Evidence Label Framework
This page works with Content Brain Source Depth And Evidence Label Framework.
Source Depth labels how deeply the evidence was reviewed.
Offer Evidence Requirements define what type of offer evidence is needed.
Example:
Source Depth:
Offer Page Review
Evidence Quality:
Weak Evidence
Offer Status:
Offer Claims Need Review
Next Step:
Route to Compliance Brain and Research Brain before strong content is created.
Relationship To Publishing Readiness Status Values Framework
This page works with Content Brain Publishing Readiness Status Values Framework.
When offer evidence is missing, use these statuses:
Needs Offer Evidence
Needs Source Review
Needs Compliance Review
Ready For HeadOffice Review
Do Not Use
Do not use vague labels such as ready, good, approved, or done.
Relationship To Future Site Content Intelligence Report Generator
The future Site Content Intelligence Report Generator may eventually include offer evidence sections when a site supports affiliate offers.
Potential future report sections:
Offer Evidence Status
Offer Identity
Primary Promise
Mechanism Summary
Claim Risk Notes
Proof Evidence
Disclosure Notes
Affiliate Support Gaps
VSL Support Needs
Bridge Page Risks
Compliance Routing Needs
Recommended Next Action
This page supplies the manual logic for those sections.
It does not authorise the generator build.
Relationship To Future Fields
This page may later inform future fields such as:
Offer Name
Vendor Name
Affiliate Network
Offer URL
VSL URL
Primary Promise
Primary Mechanism
Offer Evidence Status
Claim Risk Level
Proof Evidence Status
VSL Claim Review Required
Compliance Review Required
Research Review Required
Affiliate Brain Review Required
Disclosure Required
Offer Context Suitable For Soft Content Only
Offer Not Ready For Content
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 offer evidence logic.
Drift Protection
This framework prevents:
affiliate content being created without offer evidence
sales page claims being treated as verified facts
VSL claims being repeated without review
weak proof being treated as strong proof
disclaimers being ignored
affiliate disclosures being missed
unsupported claims entering content briefs
claim sensitive content bypassing Compliance Brain
evidence gaps bypassing Research Brain
offer logic bypassing Affiliate Brain
strategic offer risk bypassing HeadOffice
bridge pages being approved without offer context
VSL support content overstating the offer
comparison content being created without evidence
future generators being designed without offer evidence rules
future fields being created before manual logic is stable
M receiving unclear offer evidence logic
Recommended Next Step
Use this framework manually whenever Content Brain content depends on an affiliate offer, product, VSL, bridge page, or campaign.
Apply offer evidence review to:
Affiliate Product Content Packs
Affiliate Funnel Support
Bridge Page Reviews
Landing Page Refresh Reviews
VSL Support Content
Comparison Content
Publishing Readiness Reviews
Site Content Intelligence Reports where affiliate support gaps exist
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 Offer Evidence Requirements Framework
Status:
Active Reference Framework
Version:
v1.0
Parent:
Content Brain
Expected page count impact:
Previous expected page count:
44 pages
New expected page count:
45 pages
Change Impact Declaration
Pages Created:
Content Brain Offer Evidence Requirements 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:
44 pages
New expected page count:
45 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 Offer Evidence Requirements Framework as an Active Reference Framework.
Defined the offer evidence Content Brain needs before creating, refreshing, repurposing, approving, or routing affiliate offer support content.
Added offer evidence categories including Offer Identity Evidence, Vendor Evidence, Offer Page Evidence, VSL Evidence, Mechanism Evidence, Benefit Evidence, Proof Evidence, Risk And Disclaimer Evidence, Audience Evidence, and Funnel Evidence.
Added required minimum evidence by content type, offer evidence status values, claim strength rules, offer claim risk categories, evidence routing rules, offer evidence review process, safe use of limited offer evidence, what Content Brain must not do with weak offer evidence, relationship to Publishing Readiness, relationship to Site Content Intelligence, relationship to Affiliate Product Content Packs, relationship to Bridge Page Review, relationship to VSL Support, relationship to Compliance Brain, Research Brain, Affiliate Brain, HeadOffice, Source Depth And Evidence Label Framework, Publishing Readiness Status Values Framework, future Site Content Intelligence Report Generator, future fields, M handoff, drift protection, and recommended next step.
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 Offer Evidence Requirements 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
Content Brain Offer Evidence Requirements Framework
Pages updated:
None / Content Brain Page Registry if updated at closeout
Pages renamed:
None
Pages deleted:
None
Current expected page count:
45 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 — Offer Evidence Requirements Framework Created / Registry Update Deferred / Build Readiness Planning Stage / Manual Workflow Only / Plugin UI Not Started
Final Rule
Content Brain must not create strong affiliate content from weak offer evidence.
Do not treat offer page claims as verified facts.
Do not treat VSL claims as independent evidence.
Do not invent proof, mechanisms, testimonials, guarantees, prices, urgency, or authority.
If offer evidence is incomplete, use cautious language, create only safe support content, or route to the correct Brain.
These rules are manual operating language only.
They are not build approval.
END CONTENT BRAIN OFFER EVIDENCE REQUIREMENTS FRAMEWORK v1.0