Brain Name: Content Brain
Document Type: Active Operational Template
Status: Active Operational Template
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 Status Values Framework, Content Brain Source Depth And Evidence Label Framework, Content Brain Offer Evidence Requirements Framework, Content Brain Compliance Routing Needs Framework, Content Brain Human Approval Points Framework, Content Brain Future Fields To Define Later Framework, existing website content reviews, affiliate site reviews, campaign site reviews, bridge page reviews, landing page refresh reviews, content inventory reviews, content gap analysis, internal linking reviews, refresh opportunity reviews, repurposing opportunity reviews, affiliate support gap reviews, trust gap reviews, and future Content Brain build readiness planning
Parent: Content Brain
Last Reviewed: 2026-06-08
Content Brain Site Content Intelligence Report Template
Purpose
The purpose of this page is to define the manual report template Content Brain should use when reviewing an existing website before creating, refreshing, repurposing, linking, briefing, or approving content.
This page turns the Site Content Intelligence Framework into a practical operator-ready report format.
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 make manual Site Content Intelligence reviews more consistent, useful, and easier to compare across sites.
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 Operational Template
Current maturity status:
Workflow usable
Evidence backed
Manual ready
Site aware
Affiliate support tested
Bridge page refresh tested
Landing page refresh tested
Source depth labels created
Offer evidence requirements created
Compliance routing logic created
Human approval points created
Future field parking discipline created
Manual Site Content Intelligence report format now standardised
Future generator not authorised
Future UI not authorised
Future M handoff not authorised
This page is a manual report template only.
Why This Page Is Needed
Content Brain now has a clear Site Content Intelligence Framework and a future Site Content Intelligence Report Generator Specification.
However, before any generator is built, Content Brain needs a consistent manual report format.
Without a standard report template, site reviews may become inconsistent.
Different reviews may use different sections, different labels, different confidence language, different approval notes, and different next step recommendations.
This creates risk.
It may lead to:
unclear site intelligence reports
missing source depth labels
missing offer evidence notes
missing compliance routing notes
weak next actions
unclear human approval points
inconsistent content gap lists
overconfident recommendations
duplicate content recommendations
missed refresh opportunities
missed internal linking opportunities
missed affiliate support gaps
future generator planning based on inconsistent manual outputs
This template solves that problem.
Core Principle
A Site Content Intelligence Report should help Content Brain understand the site before creating or improving content.
The report should be useful, not bloated.
The report should identify what exists, what is missing, what should be refreshed, what should be linked, what should be created, what should be avoided, what needs evidence, what needs compliance review, and what the next manual step should be.
The report should not pretend to be a full SEO audit, full compliance review, full affiliate offer review, or full technical site audit.
It is a Content Brain intelligence report.
It supports content decisions.
It does not replace other Brains.
When To Use This Template
Use this template when:
working on an existing website
creating content for a site with existing pages
refreshing existing content
reviewing an affiliate site
reviewing a campaign site
reviewing a bridge page
reviewing a landing page
planning internal links
planning topic clusters
planning affiliate content support
planning SEO content after site context is needed
checking whether new content would duplicate existing pages
checking whether content gaps are real
checking whether site tone matters
checking whether trust signals are missing
checking whether affiliate support gaps exist
checking whether offer evidence or compliance routing is needed
Do not use this template when:
there is no existing site
the content is purely internal planning
the task is a tiny note
the request does not depend on site context
the operator already has enough context and a full report would create unnecessary friction
Use judgement.
Site Content Intelligence Report Format
Use the following format for manual reports.
Report Title
Use this format:
Site Content Intelligence Report: [Site Name Or Domain]
Example:
Site Content Intelligence Report: MWMSContentBrain.site
Report Header
Brain Name: Content Brain
Report Type: Site Content Intelligence Report
Status: Draft Manual Review / Active Manual Review / Completed Manual Review / Parked Pending Clarity
Version: v1.0
Authority: HeadOffice
Site Reviewed:
Site URL:
Review Date:
Reviewer:
Parent Workflow: Content Brain Site Content Intelligence Framework
Source Depth Label:
Evidence Quality Label:
Primary Purpose:
Recommended Next Operational Page:
Human Approval Required: Yes / No
Section 1: Site Purpose Summary
Purpose:
Define what the site appears to exist to do.
Include:
what the site is about
who the site appears to serve
what business model it supports
what offer or service it supports
what action the visitor is likely expected to take
what kind of content the site appears to publish
Use cautious language if the source depth is shallow.
Template:
The site appears to exist to:
The primary audience appears to be:
The site appears to support:
The main visitor action appears to be:
The current content role appears to be:
Confidence level:
Notes:
Section 2: Source Depth And Evidence Quality
Purpose:
Label how deeply the site was reviewed and how reliable the evidence appears.
Use labels from Content Brain Source Depth And Evidence Label Framework.
Template:
Source Depth Label:
Evidence Quality Label:
Reviewed Sources:
Pages Reviewed:
Source Limitations:
Evidence Gaps:
Confidence Notes:
Recommended Evidence Next Step:
Allowed labels may include:
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
Unknown Evidence Depth
Section 3: Current Content Inventory
Purpose:
Record the most important visible or supplied content assets.
This does not need to be a perfect crawl.
A lightweight inventory is better than no inventory.
Template:
Page Title:
URL:
Content Type:
Primary Topic:
Audience Stage:
Primary Intent:
Related Offer:
Internal Links Noted:
Refresh Need:
Repurposing Potential:
Risk Notes:
Status:
Repeat as needed.
Inventory Status:
Lightweight Inventory
Partial Inventory
Multi Page Inventory
Full Supplied Inventory
Inventory Incomplete
Section 4: Site Voice And Tone Summary
Purpose:
Identify how the site currently sounds.
Template:
Overall Tone:
Formality Level:
Energy Level:
Trust Style:
Sales Intensity:
Education Depth:
Technical Level:
Personality Level:
Common Phrases:
Phrases To Avoid:
Tone Strengths:
Tone Weaknesses:
Recommended Tone Direction:
Notes:
Use this section to help future content sound like it belongs on the site.
Do not preserve bad writing just because it exists.
Preserve useful consistency while improving quality.
Section 5: Topic Coverage Map
Purpose:
Identify what topics the site already covers.
Template:
Main Topic Areas:
Supporting Topics:
Strong Topic Areas:
Weak Topic Areas:
Missing Topics:
Overdeveloped Topics:
Underdeveloped Topics:
Orphan Topics:
Affiliate Support Topics:
Trust Topics:
FAQ Topics:
Comparison Topics:
Topic Cluster Notes:
Hub Page Candidates:
Spoke Page Candidates:
Notes:
This section helps Content Brain avoid random content creation.
Section 6: Content Gap List
Purpose:
Identify useful missing content.
A content gap should serve a real purpose.
Do not list gaps only because more content could exist.
Template:
Gap Name:
Gap Type:
Why It Matters:
Audience Stage:
Supported Workflow:
Related Offer:
Related Existing Page:
Risk Level:
Evidence Needed:
Recommended Action:
Priority:
Gap types may include:
Problem Awareness Gap
Solution Awareness Gap
Product Education Gap
FAQ Gap
Trust Gap
Comparison Gap
Internal Linking Gap
Refresh Gap
Repurposing Gap
Affiliate Support Gap
Publishing Readiness Gap
Reader Journey Gap
Section 7: Duplicate Or Overlap Warnings
Purpose:
Identify where proposed new content may duplicate or overlap existing content.
Template:
Potential Duplicate Topic:
Existing Page:
Proposed New Page Or Idea:
Overlap Type:
Risk:
Recommended Action:
Options:
refresh existing page
merge content
expand existing page
create different angle
create supporting spoke page
park the request
do not create new content
Overlap types may include:
same topic
same search intent
same audience
same content purpose
same offer support role
same keyword focus
same funnel stage
same FAQ coverage
same comparison angle
Section 8: Thin Content Warnings
Purpose:
Identify pages or proposed assets that may not add enough useful value.
Template:
Page Or Asset:
Thin Content Risk:
Reason:
Information Gain Gap:
Trust Gap:
Example Gap:
Internal Linking Gap:
Reader Value Gap:
Recommended Action:
Options:
improve
merge
refresh
expand
retire
park
do not create
Thin content risk may appear when content:
repeats generic information
has no information gain
has no clear purpose
has weak examples
has weak internal links
has no trust support
has no useful next step
exists only because AI can generate it
Section 9: Refresh Opportunities
Purpose:
Identify existing pages that should be improved before new content is created.
Template:
Page:
Refresh Trigger:
Current Issue:
Recommended Refresh Type:
Evidence Needed:
Compliance Risk:
Offer Evidence Needed:
Internal Linking Needed:
Priority:
Recommended Next Step:
Refresh triggers may include:
outdated information
thin content
weak structure
poor intent match
weak internal links
old claims
missing trust signals
duplicated sections
poor information gain
changed offer context
changed search intent
weak publishing readiness
Section 10: Repurposing Opportunities
Purpose:
Identify existing approved content that may be safely reused in other formats.
Template:
Source Asset:
Possible New Format:
Repurposing Purpose:
Audience Stage:
Meaning Preservation Risk:
Claim Strength Risk:
Compliance Risk:
Approval Required:
Recommended Next Step:
Possible repurposing paths:
article to email
article to social post
article to YouTube description
article to VEO3 support
guide to checklist
FAQ to support content
comparison to internal training
framework to client facing explanation
Repurposing must preserve meaning.
It must not strengthen claims.
It must not change audience stage in a risky way.
Section 11: Internal Linking Opportunities
Purpose:
Identify where pages should connect.
Template:
Source Page:
Target Page:
Link Purpose:
Reader Journey Role:
SEO Support Role:
Trust Support Role:
Affiliate Support Role:
Risk Notes:
Priority:
Recommended Anchor Direction:
Link types may include:
hub to spoke
spoke to hub
related article
trust support
FAQ support
comparison support
affiliate support
refresh related
reader journey
orphan page fix
Internal links should help the reader first.
SEO benefit should come from useful structure.
Section 12: Trust Signal Summary
Purpose:
Identify what trust signals already exist and what is missing.
Template:
Existing Trust Signals:
Missing Trust Signals:
Weak Trust Areas:
Author Or Brand Clarity:
Disclosure Clarity:
Proof Clarity:
Contact Or Support Clarity:
Transparency Notes:
Claim Safety Notes:
Recommended Trust Content:
Trust signals may include:
clear author or brand identity
experience signals
case studies
testimonials
FAQ sections
disclosures
transparent limitations
contact information
support pages
proof explanations
comparison fairness
clear expectation setting
safe claim handling
Section 13: Affiliate Support Gap Review
Purpose:
Identify whether the site properly supports affiliate offers, VSLs, bridge pages, or product education.
Template:
Affiliate Offer Present:
Offer Name:
Affiliate Network:
Vendor:
Offer Evidence Status:
VSL Context Known:
Affiliate Disclosure Present:
Problem Awareness Content Present:
Solution Awareness Content Present:
Product Education Present:
FAQ Support Present:
Trust Support Present:
Comparison Content Present:
Objection Handling Present:
VSL Preparation Present:
Bridge Page Support Present:
Affiliate Support Gaps:
Recommended Affiliate Content Assets:
Routing Required:
Do not invent offer evidence.
If offer evidence is incomplete, use Content Brain Offer Evidence Requirements Framework.
Section 14: Offer Evidence Notes
Purpose:
Record whether offer evidence is strong enough for content planning.
Template:
Offer Evidence Status:
Offer Identity Clear:
Vendor Clear:
Affiliate Network Clear:
Sales Page Reviewed:
VSL Reviewed:
Primary Promise Known:
Mechanism Known:
Benefit Claims Known:
Proof Evidence Known:
Disclaimers Known:
Disclosure Needs Known:
Claim Risk Level:
Recommended Next Step:
Possible status values:
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
Section 15: Compliance Routing Notes
Purpose:
Record whether compliance review is needed.
Template:
Compliance Routing Required:
Compliance Risk Level:
Claim Risk Categories:
Disclosure Review Required:
Needs Claim Softening:
Needs Evidence Before Compliance:
VSL Claim Risk:
Ad To Page Match Risk:
Urgency Risk:
Comparison Risk:
Testimonial Risk:
Misleading Curiosity Risk:
Recommended Compliance Route:
Notes:
Possible routing statuses:
Needs Compliance Review
Needs Claim Softening
Needs Disclosure Review
Needs Evidence Before Compliance
Compliance Risk Low
Compliance Risk Moderate
Compliance Risk High
Do Not Use Until Reviewed
Section 16: Reader Journey Notes
Purpose:
Identify how a visitor may move through the site and where content support is needed.
Template:
Likely Entry Point:
Reader Awareness Stage:
Reader Problem:
Reader Needs Next:
Current Journey Gap:
Missing Internal Link:
Missing Trust Support:
CTA Timing Issue:
Offer Transition Issue:
Recommended Journey Fix:
Notes:
Reader journey notes help Content Brain create content that fits the site’s natural flow.
Section 17: SEO Structure Notes
Purpose:
Record SEO-related structure observations without replacing Search Intelligence Brain.
Template:
Main Search Topics:
Possible Hub Pages:
Possible Spoke Pages:
Search Intent Unclear:
Keyword Cannibalisation Risk:
SERP Validation Needed:
Entity Coverage Gap:
Topic Cluster Gap:
SEO Content Opportunity:
Search Intelligence Required:
Notes:
Content Brain can record SEO structure notes.
Search Intelligence Brain owns search validation.
Section 18: Recommended Next Content Assets
Purpose:
List the most useful next content assets.
Template:
Recommended Asset:
Asset Type:
Purpose:
Audience Stage:
Related Existing Page:
Related Offer:
Evidence Needed:
Compliance Routing Needed:
Recommended Operational Page:
Priority:
Reason:
Asset types may include:
Content Brief
SEO Content Brief
Affiliate Product Content Pack
Affiliate Funnel Support Asset
Refresh Plan
Internal Linking Plan
Repurposing Plan
Trust Content
FAQ Content
Comparison Content
Bridge Page Refresh
Landing Page Refresh
Research Request
Compliance Review Request
Section 19: Pages To Avoid Creating
Purpose:
Prevent unnecessary, duplicate, thin, or risky content creation.
Template:
Page Or Topic To Avoid:
Reason:
Existing Page Conflict:
Evidence Gap:
Risk:
Better Action:
Options:
refresh existing page
merge
create different angle
wait for evidence
route to another Brain
do not create
This section is important because good Content Brain work includes knowing what not to create.
Section 20: Site Specific Content Instructions
Purpose:
Provide instructions for future briefs and drafts.
Template:
Use This Tone:
Avoid This Tone:
Use These Terms:
Avoid These Terms:
Link To These Pages:
Do Not Duplicate These Pages:
Refresh These Pages First:
Use These Trust Signals:
Avoid These Claims:
Audience Awareness Level:
Recommended CTA Style:
Recommended Content Depth:
Notes:
These instructions help future content feel like it belongs on the site.
Section 21: Recommended Routing
Purpose:
Identify which Brain or workflow should receive the next action.
Template:
Recommended Next Operational Page:
Recommended Next Brain:
Routing Reason:
Urgency:
Human Approval Required:
Approval Owner:
Notes:
Possible next operational pages:
Content Brain Workflow
Content Brain Content Briefs
Content Brain SEO Content Briefs
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
Content Brain Publishing Readiness
Content Brain Internal Linking
Content Brain Refresh
Content Brain Repurposing
Possible Brain routes:
HeadOffice Brain
Research Brain
Search Intelligence Brain
Affiliate Brain
Ads Brain
Experimentation Brain
Conversion Brain
Compliance Brain
Data Brain
Finance Brain
Strategy Brain
SIT Brain
Section 22: Human Approval Points
Purpose:
Identify where human approval is required.
Template:
Human Approval Required:
Approval Owner:
Approval Scope:
Approval Reason:
Approved For:
Not Approved For:
Decision Needed:
Notes:
Use precise approval language.
Do not use vague approval language.
Examples:
Approved For Manual Planning
Approved For Drafting
Approved For Review
Approved For Publishing Review
Approved For Public Use
Approved For Campaign Use
Approved For Future Specification Planning
Approved For M Handoff
Do Not Approve
Section 23: Final Readiness Status
Purpose:
Give the report a clear final manual status.
Template:
Final Readiness Status:
Reason:
Blocking Issues:
Recommended Next Action:
Registry Update Needed:
Build Work Authorised:
M Work Authorised:
Notes:
Allowed statuses may include:
Needs Site Intelligence
Needs Source Review
Needs Offer Evidence
Needs Compliance Review
Needs Search Validation
Needs Internal Linking Review
Needs Refresh Instead
Needs Repurposing Review
Duplicate Risk
Thin Content Risk
Parked Pending Clarity
Ready For HeadOffice Review
Ready For Publishing Review
Approved For Next Manual Step
Do Not Use
Section 24: Report Change Log
Template:
Version: v1.0
Date:
Author: HeadOffice
Change:
Created Site Content Intelligence Report for [site name or domain].
Reviewed source depth, evidence quality, site purpose, content inventory, voice and tone, topic coverage, content gaps, duplicate risks, thin content risks, refresh opportunities, repurposing opportunities, internal linking opportunities, trust signals, affiliate support gaps, offer evidence notes, compliance routing notes, reader journey notes, SEO structure notes, recommended next content assets, pages to avoid creating, site specific content instructions, recommended routing, human approval points, and final readiness status.
Section 25: Report Final Rule
Use this final rule at the bottom of each report:
This Site Content Intelligence Report is a manual content planning document.
It is not a full SEO audit.
It is not a full compliance review.
It is not a full affiliate offer review.
It is not publishing approval.
It is not campaign approval.
It is not technical build approval.
It is not an M handoff pack.
It exists to help Content Brain understand the site before creating, refreshing, repurposing, linking, briefing, or approving content.
END SITE CONTENT INTELLIGENCE REPORT
Short Form Report Option
If the full report is too heavy for the task, use the short form.
Short Form Template:
Site Reviewed:
Source Depth Label:
Evidence Quality Label:
Site Purpose:
Primary Audience:
Main Content Types:
Tone Summary:
Main Topics:
Content Gaps:
Refresh Opportunities:
Internal Linking Opportunities:
Affiliate Support Gaps:
Offer Evidence Status:
Compliance Routing Needed:
Recommended Next Content Assets:
Pages To Avoid Creating:
Recommended Next Operational Page:
Human Approval Required:
Final Readiness Status:
Notes:
Use the short form when:
the site review is lightweight
the task is early stage
only directional guidance is needed
the operator does not need a full report
the full report would create unnecessary friction
Use the full form when:
affiliate content is involved
claim risk exists
publishing decisions matter
bridge pages are involved
landing pages are involved
site architecture matters
future build evidence matters
multiple downstream workflows depend on the review
Report Quality Rules
A good Site Content Intelligence Report should be:
clear
practical
source labelled
evidence aware
site specific
not generic
useful for the next workflow
honest about limits
careful with claims
clear about routing
clear about human approval
clear about what not to create
A poor report is:
generic
overconfident
too long without purpose
missing source depth
missing evidence quality
missing offer evidence notes
missing compliance routing
unclear on next steps
unclear on approval
treats a surface review as a deep review
recommends content without checking existing pages
creates content gaps just because more content could exist
Relationship To Site Content Intelligence Framework
The Site Content Intelligence Framework defines the logic.
This template defines the manual report structure.
Use the framework to understand the principles.
Use this template to produce the report.
Relationship To Site Content Intelligence Report Generator Specification
The Site Content Intelligence Report Generator Specification defines what a future generator may eventually do.
This template gives the manual version of that output.
This template may later provide evidence for whether a future generator is useful.
It does not authorise the generator build.
Relationship To Publishing Readiness Status Values Framework
This template uses Publishing Readiness status values to define final readiness and next steps.
It should not use vague labels such as ready, done, approved, or good.
Always define what the asset is ready for.
Relationship To Source Depth And Evidence Label Framework
This template must include source depth and evidence quality when the decision depends on evidence.
Do not treat source depth as optional when claims, affiliate offers, VSLs, public publishing, or campaign content are involved.
Relationship To Offer Evidence Requirements Framework
This template must include offer evidence notes when the site supports an affiliate offer, product, VSL, bridge page, or campaign.
Do not create strong affiliate support recommendations if offer evidence is incomplete.
Relationship To Compliance Routing Needs Framework
This template must include compliance routing notes when claim risk, disclosure risk, VSL risk, ad to page risk, urgency risk, comparison risk, testimonial risk, or sensitive topic risk appears.
Content Brain may route.
Content Brain does not clear compliance.
Relationship To Human Approval Points Framework
This template must identify whether human approval is required.
It must state approval scope clearly.
Do not use vague approval language.
Relationship To Future Fields To Define Later Framework
This template may reveal useful future fields.
Those fields should be treated as future candidates only.
Do not convert report sections into database fields without later consolidation and HeadOffice approval.
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 future generator planning only if HeadOffice approves the next maturity step.
Drift Protection
This template prevents:
site reviews becoming inconsistent
generic content planning
content being created without site context
source depth being ignored
offer evidence being ignored
compliance routing being ignored
human approval being skipped
content gaps being invented without purpose
duplicate content being recommended
thin content being created
internal linking opportunities being missed
refresh opportunities being ignored
repurposing opportunities being missed
affiliate support gaps being missed
site tone being ignored
future generator planning being based on inconsistent reports
M receiving premature implementation instructions
Recommended Next Step
Use this template for the next real Site Content Intelligence manual review.
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 Site Content Intelligence Report Template
Status:
Active Operational Template
Version:
v1.0
Parent:
Content Brain
Expected page count impact:
Previous expected page count:
48 pages
New expected page count:
49 pages
Change Impact Declaration
Pages Created:
Content Brain Site Content Intelligence Report Template
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:
48 pages
New expected page count:
49 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 Site Content Intelligence Report Template as an Active Operational Template.
Defined the manual report format Content Brain should use when reviewing an existing website before creating, refreshing, repurposing, linking, briefing, or approving content.
Added full report structure including report header, site purpose summary, source depth and evidence quality, current content inventory, site voice and tone summary, topic coverage map, content gap list, duplicate or overlap warnings, thin content warnings, refresh opportunities, repurposing opportunities, internal linking opportunities, trust signal summary, affiliate support gap review, offer evidence notes, compliance routing notes, reader journey notes, SEO structure notes, recommended next content assets, pages to avoid creating, site specific content instructions, recommended routing, human approval points, final readiness status, report change log, and report final rule.
Added short form report option, report quality rules, relationships to Site Content Intelligence Framework, Site Content Intelligence Report Generator Specification, Publishing Readiness Status Values Framework, Source Depth And Evidence Label Framework, Offer Evidence Requirements Framework, Compliance Routing Needs Framework, Human Approval Points Framework, Future Fields To Define Later Framework, 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 Human Approval Points Framework created:
Yes / No
Content Brain Future Fields To Define Later Framework created:
Yes / No
Content Brain Site Content Intelligence Report Template 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
Content Brain Human Approval Points Framework
Content Brain Future Fields To Define Later Framework
Content Brain Site Content Intelligence Report Template
Pages updated:
None / Content Brain Page Registry if updated at closeout
Pages renamed:
None
Pages deleted:
None
Current expected page count:
49 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 — Site Content Intelligence Report Template Created / Registry Update Deferred / Build Readiness Planning Stage / Manual Workflow Only / Plugin UI Not Started
Final Rule
Before Content Brain creates important content for an existing site, it should understand the site.
Use this template when site context matters.
Use source depth labels.
Use offer evidence notes when affiliate content is involved.
Use compliance routing notes when claims or disclosure risk appears.
Use human approval points when public use, campaign use, or build readiness could be affected.
The report supports better content decisions.
It does not approve publishing.
It does not approve campaigns.
It does not approve build work.
END CONTENT BRAIN SITE CONTENT INTELLIGENCE REPORT TEMPLATE v1.0