Brain Name: Content Brain
Document Type: Active Reference Framework
Status: Active Reference Framework
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, Content Brain Publishing Readiness, Content Brain Affiliate Content Packs, Content Brain Affiliate Funnel Support, 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, Content Brain Offer Evidence Requirements Framework, affiliate content planning, VSL support content, bridge page review, landing page refresh review, claim risk review, compliance routing, Compliance Brain handoff, HeadOffice review, and future Content Brain build readiness planning
Parent: Content Brain
Last Reviewed: 2026-06-08
Content Brain Compliance Routing Needs Framework
Purpose
The purpose of this page is to define when Content Brain should route content, claims, offer support material, bridge pages, VSL support content, refresh work, or publishing readiness decisions to Compliance Brain or HeadOffice before moving forward.
This page exists because Content Brain creates and improves content that may involve claim risk, affiliate risk, platform policy risk, ad to page risk, VSL claim risk, disclosure risk, urgency risk, and audience expectation risk.
Content Brain must not treat compliance-sensitive content as normal content.
Content Brain must be able to recognise when a content asset needs compliance review before it is drafted, published, refreshed, repurposed, used in ads, handed to another Brain, or treated as ready.
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 compliance routing discipline before Content Brain creates or approves 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
Publishing readiness status values created
Source depth labels created
Offer evidence requirements created
Compliance routing logic now requires 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 many public facing and campaign supporting assets.
These assets may include:
blog posts
SEO content
affiliate support articles
affiliate product content packs
bridge pages
landing page refresh plans
VSL support content
comparison content
FAQ content
email support content
YouTube descriptions
ad support content
pre sell content
internal linking recommendations
repurposed content
publishing readiness checks
Many of these assets can create compliance risk if claims are too strong, evidence is weak, disclaimers are missing, or reader expectations are mismanaged.
Without a clear routing framework, Content Brain may accidentally:
approve unsafe claims
repeat VSL claims without review
create unsupported affiliate content
soften disclaimers too much
use pressure language
create misleading curiosity
use urgency incorrectly
make unverified comparison claims
make health or wellness claims too strongly
make income or financial claims too strongly
publish content without evidence depth
route content to the wrong Brain
treat content as ready before risk has been reviewed
This framework defines when Content Brain must pause and route.
Core Principle
Content Brain may identify compliance risk.
Content Brain may flag compliance risk.
Content Brain may soften obvious risky language.
Content Brain may recommend Compliance Brain review.
Content Brain may recommend HeadOffice review.
Content Brain must not act as final compliance authority.
Compliance Brain owns compliance interpretation.
HeadOffice owns final direction and priority.
Content Brain owns content structure, content usefulness, publishing readiness support, and routing discipline.
If a content decision involves claim risk, sensitive category risk, affiliate disclosure risk, platform policy risk, or public trust risk, Content Brain should route instead of pretending the issue is solved.
Compliance Routing Rule
Content Brain should route to Compliance Brain when a content asset includes or may include:
health claims
wellness claims
medical adjacent claims
financial claims
income claims
legal claims
safety claims
environmental claims
disaster claims
performance claims
guarantee claims
testimonial claims
comparison claims
scientific claims
authority claims
scarcity claims
urgency claims
risk reversal claims
refund claims
VSL claims
affiliate offer claims
ad to page promise mismatch
misleading curiosity
high pressure CTA language
unsupported proof
weak disclaimers
missing affiliate disclosure
sensitive audience targeting
platform policy concerns
If the operator is unsure whether compliance risk exists, Content Brain should use a cautious status:
Needs Compliance Review
Ready For HeadOffice Review
Parked Pending Clarity
Do Not Use
Primary Compliance Risk Categories
Use the following categories when reviewing Content Brain outputs for routing needs.
Health And Wellness Claim Risk
This includes claims related to:
pain
energy
sleep
stress
anxiety
weight loss
blood sugar
hormones
menopause
inflammation
mobility
cognitive performance
mental health
disease prevention
disease improvement
medical treatment
physical transformation
wellness outcomes
Required action:
Route to Compliance Brain when claims are specific, strong, implied, comparative, or product linked.
Content Brain may safely create general education only when claims are soft, evidence is labelled, and the content avoids medical certainty.
Income And Financial Claim Risk
This includes claims related to:
making money
profit
ROI
passive income
business growth
investment returns
debt relief
credit improvement
financial freedom
guaranteed earnings
side hustle outcomes
client acquisition outcomes
campaign profitability
Required action:
Route to Compliance Brain when claims imply likely financial outcomes, guaranteed results, unusually fast returns, low effort income, or performance certainty.
Content Brain may safely create general education only when results are clearly framed as variable and not guaranteed.
Legal Or Regulatory Claim Risk
This includes claims related to:
legal rights
contracts
warranties
government rules
tax treatment
financial regulation
health regulation
consumer protection
platform compliance
privacy obligations
data handling
Required action:
Route to Compliance Brain or HeadOffice when legal interpretation may affect public facing content, client advice, or platform risk.
Content Brain should not present legal conclusions as final authority.
Safety And Protection Claim Risk
This includes claims related to:
risk reduction
emergency readiness
water security
home safety
personal safety
disaster protection
cybersecurity
data safety
fraud prevention
physical protection
survival claims
Required action:
Route to Compliance Brain when content implies protection from harm, guaranteed safety, emergency preparedness certainty, or fear based urgency.
Environmental And Disaster Claim Risk
This includes claims related to:
climate events
drought
water shortages
storms
natural disasters
pollution
contamination
resource scarcity
emergency planning
government failure
Required action:
Route to Compliance Brain when claims could create fear, urgency, exaggeration, or unsupported environmental conclusions.
Use evidence labels and cautious language.
Performance Claim Risk
This includes claims related to:
best
fastest
highest converting
most effective
works better
proven system
guaranteed improvement
measurable result
conversion lift
ranking improvement
traffic increase
sales increase
Required action:
Route to Compliance Brain or Research Brain when performance claims need evidence.
Use caution when performance evidence is weak or user supplied only.
Comparison Claim Risk
This includes claims related to:
better than
safer than
cheaper than
more effective than
outperforms
alternative to
replaces
beats competitors
superior to
Required action:
Route to Research Brain for evidence and Compliance Brain for claim safety when comparison content is public facing or campaign sensitive.
Testimonial And Social Proof Risk
This includes claims related to:
customer results
before and after stories
success stories
reviews
case studies
rankings
user numbers
community claims
screenshots
expert endorsements
Required action:
Route to Compliance Brain when testimonials imply typical results, unusual outcomes, health results, financial results, or unsupported performance claims.
Preserve limitations and disclaimers.
Scientific And Authority Claim Risk
This includes claims related to:
scientifically proven
doctor recommended
expert backed
research supported
clinical
NASA
university backed
government backed
official
certified
patented
lab tested
Required action:
Route to Research Brain for evidence and Compliance Brain for claim safety.
Do not use authority references unless evidence is clear and approved.
Urgency And Scarcity Risk
This includes claims related to:
limited time
last chance
before it is too late
act now
urgent
scarce
running out
deadline
fear of missing out
supply shortage
crisis language
Required action:
Route to Compliance Brain or HeadOffice when urgency may be misleading, exaggerated, fear based, or platform sensitive.
Affiliate Disclosure Risk
This includes situations where:
affiliate links are used
commission may be earned
product recommendation is monetised
review content supports an offer
comparison content supports an offer
VSL link is used
bridge page routes to affiliate offer
Required action:
Ensure affiliate disclosure awareness exists.
Route to Compliance Brain if disclosure wording, placement, or clarity is unclear.
VSL Claim Risk
This includes situations where:
content supports a VSL
content introduces a VSL
content repeats a VSL promise
content previews a mechanism
content prepares a viewer for a sales argument
content creates curiosity around the VSL
content transitions from bridge page to VSL
Required action:
Route to Compliance Brain when VSL claims are strong, sensitive, implied, or unsupported.
Route to Affiliate Brain if offer logic is unclear.
Route to Research Brain if evidence is missing.
Ad To Page Match Risk
This includes situations where:
ad promise differs from page promise
headline overstates the offer
bridge page changes the claim
curiosity hook misleads the reader
VSL expectation is different from ad expectation
CTA pressure is too high
the page hides the affiliate nature of the pathway
Required action:
Route to Compliance Brain or HeadOffice when mismatch may create platform policy risk or trust risk.
Misleading Curiosity Risk
This includes content that:
withholds too much information
uses mystery to hide the product
implies a secret without evidence
creates fear without support
suggests suppressed information
implies authority without proof
makes the reader click to understand basic facts
Required action:
Route to Compliance Brain or HeadOffice when curiosity may be misleading or platform risky.
Content Brain should prefer clear curiosity over deceptive curiosity.
Compliance Routing Status Values
Use the following status values during manual Content Brain workflows.
Needs Compliance Review
Meaning:
The asset contains claim risk or policy sensitive content that should be reviewed by Compliance Brain before moving forward.
Use when:
claims are strong
claims are sensitive
evidence is weak
disclosures are unclear
urgency is risky
VSL claims appear
affiliate claims appear
comparison claims appear
health, wellness, finance, safety, legal, or income claims appear
Next action:
Route to Compliance Brain.
Needs Claim Softening
Meaning:
The claim appears too strong and should be softened before further review or publishing readiness.
Use when:
the claim may be acceptable if toned down
the evidence is moderate or weak
the claim uses certainty language
the claim implies guaranteed results
the claim can be reframed safely
Next action:
Revise claim language, then reassess whether Compliance Brain review is still needed.
Needs Disclosure Review
Meaning:
Affiliate, risk, limitation, or results disclosure may be required or unclear.
Use when:
affiliate link exists
review content supports monetised offer
testimonial content appears
health or income claims appear
results vary
guarantee terms are mentioned
limitations are missing
Next action:
Route to Compliance Brain or HeadOffice.
Needs Evidence Before Compliance
Meaning:
Compliance review would be weak because evidence is missing.
Use when:
claims need source support first
offer evidence is incomplete
comparison facts are missing
scientific references are missing
testimonial details are unclear
Next action:
Route to Research Brain or Affiliate Brain before Compliance Brain if appropriate.
Compliance Risk Low
Meaning:
The asset appears low risk after manual review.
Use when:
content is educational
claims are soft
no sensitive claim category appears
no affiliate offer is pushed
no urgency or scarcity appears
disclosures are not needed or are already clear
Next action:
Proceed to normal Publishing Readiness review.
Compliance Risk Moderate
Meaning:
The asset has some risk but may be manageable with review, softening, or evidence.
Use when:
claims are present but not extreme
affiliate support exists
offer evidence is partial
some disclaimer context exists
content is not aggressive
Next action:
Review, soften, or route depending on use case.
Compliance Risk High
Meaning:
The asset should not move forward without Compliance Brain or HeadOffice review.
Use when:
claims are strong
claims are sensitive
claims are unsupported
VSL claims are repeated
urgency is strong
testimonial proof is risky
disclosures are missing
ad to page mismatch exists
Next action:
Route to Compliance Brain or HeadOffice.
Do Not Use Until Reviewed
Meaning:
The asset should not be used in its current form.
Use when:
risk is too high
claims may mislead
evidence is missing
disclosures are missing
platform risk is likely
trust risk is high
Next action:
Park, revise, or route.
Compliance Routing Decision Flow
Use this manual decision flow.
Step 1:
Does the content include a claim?
If yes, identify claim type.
Step 2:
Is the claim sensitive?
Check health, wellness, finance, income, legal, safety, environment, disaster, performance, comparison, testimonial, scientific, urgency, scarcity, and affiliate categories.
Step 3:
Is the claim supported?
Check source depth and evidence quality.
Step 4:
Is the content offer related?
Check offer evidence requirements.
Step 5:
Is the content VSL related?
Check whether VSL claims are being repeated, teased, strengthened, or reframed.
Step 6:
Is the content used in an ad pathway?
Check ad to page match, curiosity, CTA pressure, and expectation setting.
Step 7:
Are disclosures needed?
Check affiliate, testimonial, guarantee, risk, results, or limitation disclosures.
Step 8:
Can the issue be softened manually?
If yes, use Needs Claim Softening.
Step 9:
Does the issue need evidence first?
If yes, use Needs Evidence Before Compliance.
Step 10:
Does the asset require Compliance Brain review?
If yes, use Needs Compliance Review.
Step 11:
Does the issue require strategic direction?
If yes, use Ready For HeadOffice Review.
Step 12:
If risk is high and unresolved, use Do Not Use Until Reviewed.
Content Brain Allowed Actions
Content Brain may:
identify claim risk
label claim risk
soften obvious overstatements
remove unsupported certainty
preserve disclaimers
recommend Compliance Brain review
recommend Research Brain review
recommend Affiliate Brain review
recommend HeadOffice review
park risky content
mark content as not ready
recommend safer educational framing
recommend source review
recommend offer evidence review
recommend publishing readiness review
Content Brain must stay within manual review and routing authority.
Content Brain Prohibited Actions
Content Brain must not:
approve sensitive claims
approve legal claims
approve health claims
approve income claims
approve financial claims
approve safety claims
approve VSL claims
approve testimonial claims
approve comparison claims
approve scientific claims
approve urgency or scarcity claims
invent disclaimers
hide risk
remove important qualifiers
turn weak claims into strong claims
treat sales page claims as proof
treat VSL claims as proof
treat user supplied context as independent evidence
treat content as publishable because it reads well
replace Compliance Brain
replace HeadOffice
approve paid traffic use
approve M handoff
create technical build instructions
Relationship To Publishing Readiness
Publishing Readiness should use this framework when deciding whether content is ready for use or requires compliance routing.
If compliance risk exists, Publishing Readiness should not mark the asset as approved.
Use status values such as:
Needs Compliance Review
Needs Claim Softening
Needs Disclosure Review
Needs Evidence Before Compliance
Compliance Risk High
Do Not Use Until Reviewed
Ready For HeadOffice Review
Ready For Publishing Review should only be used after unresolved compliance risks have been addressed, routed, or clearly marked.
Relationship To Publishing Readiness Status Values Framework
Publishing Readiness Status Values define the general readiness state.
This framework defines the compliance-specific routing logic.
Example:
Status:
Needs Compliance Review
Reason:
Affiliate bridge page includes urgency and VSL claims.
Source Depth:
Offer Page Review / VSL Claim Review
Evidence Quality:
Weak Evidence
Next Step:
Route to Compliance Brain before public use.
Relationship To Source Depth And Evidence Label Framework
Source depth matters before compliance decisions.
A shallow source review should not support strong claims.
Examples:
Surface Review plus health claim equals Needs Compliance Review.
Offer Page Review plus income claim equals Needs Compliance Review.
VSL Claim Review plus strong mechanism claim equals Needs Evidence Before Compliance or Needs Compliance Review.
Unknown Evidence Depth plus performance claim equals Do Not Use Until Reviewed.
Relationship To Offer Evidence Requirements Framework
Offer evidence affects compliance routing.
If offer evidence is incomplete, Content Brain should avoid strong offer support content.
If offer claims are strong, Content Brain should route.
If VSL claims are unclear, Content Brain should route.
If proof evidence is weak, Content Brain should avoid strong proof language.
If affiliate disclosure is unclear, Content Brain should route.
Relationship To Site Content Intelligence
Site Content Intelligence may identify compliance risks across a site.
Examples:
unsupported trust claims
old health claims
weak affiliate disclosures
aggressive bridge page language
misleading comparison language
thin content with strong claims
outdated offer claims
unsafe urgency
Site Content Intelligence should flag these risks and recommend routing.
It should not resolve final compliance interpretation.
Relationship To Affiliate Content Packs
Affiliate Product Content Packs must use this framework when claims, offers, VSLs, proof, or disclosures appear.
A content pack should not move to public use if:
offer evidence is missing
claim risk is unresolved
affiliate disclosure is unclear
VSL claims are repeated without review
proof is weak
urgency is misleading
comparison claims are unsupported
Relationship To Bridge Page Review
Bridge pages require close compliance review because they often sit between ads and VSLs.
Bridge page risk may include:
ad to page mismatch
misleading curiosity
unsupported headline promise
strong VSL preview
hidden product context
high pressure CTA
affiliate disclosure issue
urgency issue
claim escalation from ad to page
If any of these appear, route to Compliance Brain or HeadOffice.
Relationship To VSL Support Content
VSL support content should prepare the reader without overstating the VSL.
Route when:
VSL claims are strong
mechanism claims are sensitive
proof claims are weak
urgency is high
the content repeats claims without evidence
the content makes the VSL sound more proven than it is
the transition hides offer context
Relationship To Research Brain
Route to Research Brain when compliance review depends on missing evidence.
Examples:
scientific claim needs evidence
comparison claim needs evidence
market statistic needs evidence
audience claim needs evidence
performance claim needs evidence
testimonial representativeness is unclear
Research Brain owns evidence quality.
Relationship To Affiliate Brain
Route to Affiliate Brain when compliance risk is tied to offer logic.
Examples:
offer promise is unclear
affiliate funnel is unclear
VSL role is unclear
offer viability is questionable
offer should possibly be parked
audience fit is unclear
affiliate content pack depends on offer strategy
Affiliate Brain owns offer logic.
Relationship To Compliance Brain
Route to Compliance Brain when policy or claim interpretation is needed.
Examples:
health claim
income claim
financial claim
safety claim
legal claim
testimonial claim
comparison claim
urgency claim
affiliate disclosure
VSL claim
platform risk
Compliance Brain owns compliance interpretation.
Relationship To HeadOffice
Route to HeadOffice when the issue is strategic, priority based, or cross brain.
Examples:
high risk offer
campaign direction
public trust risk
brand risk
unclear Brain authority
whether to continue with offer
whether to park content
whether to approve future build candidate
HeadOffice owns final direction.
Relationship To Future Site Content Intelligence Report Generator
The future Site Content Intelligence Report Generator may eventually include compliance routing sections.
Potential future report sections:
Compliance Routing Needed
Claim Risk Notes
Disclosure Risk Notes
Offer Evidence Risk
VSL Claim Risk
Ad To Page Match Risk
Urgency Risk
Comparison Risk
Testimonial Risk
Recommended Compliance Route
Recommended HeadOffice Review
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:
Compliance Routing Required
Compliance Risk Level
Claim Risk Category
Disclosure Review Required
VSL Claim Review Required
Ad To Page Match Risk
Urgency Risk
Comparison Claim Risk
Testimonial Risk
Needs Claim Softening
Do Not Use Until Reviewed
HeadOffice Review Required
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 compliance routing logic.
Drift Protection
This framework prevents:
Compliance Brain being bypassed
HeadOffice being bypassed
claim risk being ignored
affiliate disclosures being missed
VSL claims being repeated without review
offer claims being treated as verified facts
sales page claims being treated as independent evidence
weak proof being treated as strong proof
health claims being approved too easily
income claims being approved too easily
financial claims being approved too easily
safety claims being approved too easily
comparison claims being approved without evidence
urgency being used without review
misleading curiosity being used in bridge pages
ad to page mismatch being ignored
publishing readiness approving risky content too early
future generators being designed without compliance routing logic
future fields being created before manual logic is stable
M receiving unclear compliance logic
Recommended Next Step
Use this framework manually whenever Content Brain work contains possible compliance risk.
Apply compliance routing 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
Content Refresh Reviews
Repurposing Reviews
SEO Content Briefs where claim risk appears
General Content Briefs where claim risk appears
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 Compliance Routing Needs Framework
Status:
Active Reference Framework
Version:
v1.0
Parent:
Content Brain
Expected page count impact:
Previous expected page count:
45 pages
New expected page count:
46 pages
Change Impact Declaration
Pages Created:
Content Brain Compliance Routing Needs 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:
45 pages
New expected page count:
46 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 Compliance Routing Needs Framework as an Active Reference Framework.
Defined when Content Brain should route content, claims, affiliate offer support material, bridge pages, VSL support content, refresh work, or publishing readiness decisions to Compliance Brain or HeadOffice before moving forward.
Added compliance risk categories including Health And Wellness Claim Risk, Income And Financial Claim Risk, Legal Or Regulatory Claim Risk, Safety And Protection Claim Risk, Environmental And Disaster Claim Risk, Performance Claim Risk, Comparison Claim Risk, Testimonial And Social Proof Risk, Scientific And Authority Claim Risk, Urgency And Scarcity Risk, Affiliate Disclosure Risk, VSL Claim Risk, Ad To Page Match Risk, and Misleading Curiosity Risk.
Added compliance routing status values, routing decision flow, allowed actions, prohibited actions, relationships to Publishing Readiness, Publishing Readiness Status Values Framework, Source Depth And Evidence Label Framework, Offer Evidence Requirements Framework, Site Content Intelligence, Affiliate Content Packs, Bridge Page Review, VSL Support Content, Research Brain, Affiliate Brain, Compliance Brain, HeadOffice, 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 Compliance Routing Needs 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
Content Brain Compliance Routing Needs Framework
Pages updated:
None / Content Brain Page Registry if updated at closeout
Pages renamed:
None
Pages deleted:
None
Current expected page count:
46 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 — Compliance Routing Needs Framework Created / Registry Update Deferred / Build Readiness Planning Stage / Manual Workflow Only / Plugin UI Not Started
Final Rule
Content Brain must route compliance-sensitive content instead of pretending compliance issues are solved.
Do not approve sensitive claims.
Do not repeat VSL claims without review.
Do not treat offer claims as verified facts.
Do not use misleading curiosity.
Do not ignore affiliate disclosure risk.
Do not mark content as ready if claim risk, evidence risk, disclosure risk, or platform risk remains unresolved.
Content Brain may identify, label, soften, park, or route risk.
Compliance Brain owns compliance interpretation.
HeadOffice owns final direction.
These rules are manual operating language only.
They are not build approval.
END CONTENT BRAIN COMPLIANCE ROUTING NEEDS FRAMEWORK v1.0