Brain Name: Content Brain
Document Type: Draft Future Supabase Planning Specification
Status: Draft Future Supabase Planning Specification
Version: v1.0
Authority: HeadOffice
Parent: Content Brain
Last Reviewed: 2026-06-10
Content Brain Site Intelligence Test Record Supabase Structure
Purpose
The purpose of this page is to define the future Supabase structure needed to store repeatable Content Brain Site Intelligence test records without continuing to create WordPress test pages.
This page exists because Site Intelligence Tests 1 to 5 proved that the workflow is useful, but also proved that WordPress is not the right long term storage location for repeatable test evidence.
WordPress should keep:
Core operating pages
Frameworks
Templates
Protocols
Short summary logs
Future specifications
Supabase should later hold:
Repeatable Site Intelligence test records
Structured evidence summaries
Test types
Sources reviewed
Results
Friction
Build readiness signals
Compliance risk
Offer evidence status
Routing recommendations
Recommended next actions
Status
Created date
Reviewed date
This page is planning only.
This page is not SQL.
This page is not a migration script.
This page is not a Supabase build instruction.
This page is not plugin UI approval.
This page is not dashboard approval.
This page is not automation approval.
This page is not worker approval.
This page is not Brain Room routing approval.
This page is not AI Employee approval.
This page is not cross brain task wiring approval.
This page is not M handoff approval.
Current Status
Content Brain remains:
Manual Workflow Only
Plugin UI Not Started
No Supabase Build 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 Research Brain Work Untouched
Current evidence stage:
Manual Workflow Evidence Stage
Current planning stage:
Future Supabase Structure Planning Stage
Current page role:
Draft Future Supabase Planning Specification
Current maturity status:
Useful workflow proven manually
Tests 1 to 5 recorded
Temporary WordPress test records allowed
Long term WordPress test page bloat identified
Future Supabase record structure needed
Future database build not authorised
Future UI design not authorised
Future worker setup not authorised
Future M handoff not authorised
Why This Page Is Needed
Content Brain has now created several individual Site Intelligence test records.
Those records were useful because they preserved evidence while the workflow was still being tested.
However, repeatable tests should not keep becoming WordPress pages.
If every Site Intelligence test becomes a page, Content Brain will create:
page bloat
registry bloat
parent cleanup work
copy and paste friction
version drift
test record management friction
WordPress JSON save risk
unclear page count changes
operator confusion
future migration debt
A structured Supabase table solves this later by storing each test as one record instead of one WordPress page.
Core Principle
Repeatable operational records belong in Supabase once the workflow is stable enough.
Core operating knowledge belongs in WordPress.
Site Intelligence tests are repeatable records.
Therefore, future Site Intelligence test records should move to Supabase after the structure is approved and build work is authorised.
This page defines the future structure.
It does not authorise the build.
Relationship To Current WordPress Test Records
Tests 1 to 5 may remain as short WordPress test records until Supabase storage exists.
Current temporary WordPress test records:
Content Brain Site Intelligence Test 1 MWMS Content Brain Site Review
Content Brain Site Intelligence Test 2 Emergency Preparedness Affiliate Support Review
Content Brain Site Intelligence Test 3 ProDentim Affiliate Page Review
Content Brain Site Intelligence Test 4 Heart Manifestation Thin Content Review
Content Brain Site Intelligence Test 5 The Blog Starter Refresh Before New Content Review
These pages should not be deleted automatically.
They may later be:
migrated into Supabase
kept as historical WordPress records
archived
retired
left untouched
Migration decisions must stay human controlled.
Recommended Future Table Name
content_brain_site_intelligence_tests
Naming Reason
This name follows MWMS Supabase naming discipline:
lowercase
snake_case
plural table name
Brain specific prefix
clear record purpose
machine readable
human readable
WordPress integration friendly
No spaces.
No hyphens.
No camelCase.
No PascalCase.
No special characters.
Table Purpose
The future content_brain_site_intelligence_tests table should store one structured record for each Content Brain Site Intelligence test.
Each row should represent one test outcome.
The table should support:
manual workflow evidence
future Content Brain UI
future filtering
future reporting
future migration from WordPress test pages
future build readiness analysis
future friction pattern review
future test history review
The table should not automatically:
create content briefs
create articles
create SEO briefs
create affiliate content packs
create bridge page rewrites
create Google Ads copy
route work to other Brains
create tasks
start automation
start workers
update WordPress pages
update the Registry
notify M
approve build work
Core Record Fields
id
Meaning:
Unique record ID.
Future Technical Type:
uuid
Required:
Yes
Human Controlled:
No
Notes:
System generated when the table is built later.
test_number
Meaning:
Visible Site Intelligence test number.
Example Display Value:
Site Intelligence Test 5
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Notes:
This keeps continuity with existing WordPress test records.
test_name
Meaning:
Short human readable test name.
Example Display Value:
The Blog Starter Refresh Before New Content Review
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
source_reviewed
Meaning:
The source reviewed during the test.
This may be a URL, page name, site name, pasted source, affiliate offer page, landing page, screenshot group, or internal Content Brain area.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
source_url
Meaning:
Optional URL reviewed during the test.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Notes:
Leave blank when the source is pasted text, screenshots, or internal WordPress material.
source_type
Meaning:
Classifies what kind of source was reviewed.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
internal_site
external_website
affiliate_offer_page
bridge_page
landing_page
authority_source
competitor_page
pasted_source_material
screenshot_review
mixed_source_review
unknown
Display Labels:
Internal Site
External Website
Affiliate Offer Page
Bridge Page
Landing Page
Authority Source
Competitor Page
Pasted Source Material
Screenshot Review
Mixed Source Review
Unknown
test_type
Meaning:
Primary type of Site Intelligence test.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
existing_mwms_content_site_review
affiliate_support_site_review
thin_content_site_review
refresh_before_new_content_review
bridge_page_review
seo_content_site_review
authority_content_site_review
internal_linking_and_topic_cluster_review
offer_evidence_stress_test
compliance_routing_stress_test
campaign_site_review
Display Labels:
Existing MWMS Content Site Review
Affiliate Support Site Review
Thin Content Site Review
Refresh Before New Content Review
Bridge Page Review
SEO Content Site Review
Authority Content Site Review
Internal Linking And Topic Cluster Review
Offer Evidence Stress Test
Compliance Routing Stress Test
Campaign Site Review
secondary_test_types_json
Meaning:
Optional list of secondary test types that also applied.
Future Technical Type:
jsonb
Required:
No
Human Controlled:
Yes
Notes:
Use jsonb because a test may have more than one secondary type.
result
Meaning:
Overall test outcome.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
passed
passed_with_friction
partially_passed
failed
parked_pending_clarity
Display Labels:
Passed
Passed With Friction
Partially Passed
Failed
Parked Pending Clarity
build_readiness_signal
Meaning:
How much the test supports future system planning.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
strong_build_signal
moderate_build_signal
weak_build_signal
no_build_signal
build_blocker_found
Display Labels:
Strong Build Signal
Moderate Build Signal
Weak Build Signal
No Build Signal
Build Blocker Found
build_readiness_verdict
Meaning:
Whether the test authorises build work.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Default Technical Value:
planning_evidence_only
Recommended Technical Values:
planning_evidence_only
not_build_ready
future_candidate_evidence
build_blocked
Display Labels:
Planning Evidence Only
Not Build Ready
Future Candidate Evidence
Build Blocked
Important Rule:
This field must not be used as automatic build approval.
A strong build signal is not build approval.
key_finding
Meaning:
Short summary of the main finding.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
evidence_summary
Meaning:
Short evidence summary only.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Important Rule:
Do not store full reports here.
Do not store long evidence here.
Use appendix_link or external evidence storage if needed later.
friction_found_json
Meaning:
List of friction points found during the test.
Future Technical Type:
jsonb
Required:
No
Human Controlled:
Yes
Recommended Technical Values:
template_too_heavy
report_too_long
operator_time_cost_too_high
offer_evidence_gap
compliance_routing_gap
search_intelligence_required_if_seo_is_goal
health_claim_risk
doctor_endorsement_verification_needed
google_ads_restriction_risk
affiliate_rule_restriction_risk
thin_content_risk
curiosity_claim_risk
emotional_vulnerability_risk
social_proof_verification_needed
entertainment_disclaimer_needed
google_ads_suitability_risk
relationship_outcome_claim_risk
refresh_scope_needed
internal_link_review_needed
serp_validation_needed_if_seo_is_goal
useful_but_not_build_ready
Notes:
Use jsonb because a test may have multiple friction points.
compliance_risk_level
Meaning:
Whether the test found compliance risk.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
none_found
low
moderate
high
unknown
Display Labels:
None Found
Low
Moderate
High
Unknown
compliance_risk_notes
Meaning:
Short note on compliance concerns.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
offer_evidence_status
Meaning:
Whether offer evidence was strong enough for downstream content or affiliate support.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Recommended Technical Values:
not_applicable
evidence_sufficient
evidence_gap
evidence_weak
evidence_unverified
evidence_high_risk
offer_not_reviewed
Display Labels:
Not Applicable
Evidence Sufficient
Evidence Gap
Evidence Weak
Evidence Unverified
Evidence High Risk
Offer Not Reviewed
routing_recommendation_json
Meaning:
Which Brain or authority should review the result before any downstream action.
Future Technical Type:
jsonb
Required:
No
Human Controlled:
Yes
Recommended Technical Values:
no_routing_needed
headoffice
affiliate_brain
compliance_brain
research_brain
search_intelligence_brain
ads_brain
conversion_brain
data_brain
finance_brain
strategy_brain
sit_brain
multiple_routing_needed
Notes:
Use jsonb because more than one Brain may be needed.
routing_notes
Meaning:
Short explanation of why routing is needed.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
recommended_next_action
Meaning:
The next human action recommended by the test.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
continue_manual_testing
record_evidence_only
do_not_create_downstream_content
route_before_content_work
refresh_review_needed
do_not_create_competing_page
create_content_brief_only_if_authorised
create_evidence_appendix_if_needed
park_pending_clarity
review_in_future_supabase_planning
no_further_action
Display Labels:
Continue Manual Testing
Record Evidence Only
Do Not Create Downstream Content
Route Before Content Work
Refresh Review Needed
Do Not Create Competing Page
Create Content Brief Only If Authorised
Create Evidence Appendix If Needed
Park Pending Clarity
Review In Future Supabase Planning
No Further Action
Approval And Build Control Fields
downstream_content_authorised
Meaning:
Whether the test authorises downstream content creation.
Future Technical Type:
boolean
Required:
Yes
Human Controlled:
Yes
Default Value:
false
Important Rule:
Default must always be false.
A Site Intelligence test does not automatically authorise content creation.
downstream_content_authorisation_scope
Meaning:
If downstream content is authorised later, this records the exact scope.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Example Display Values:
Approved For Manual Planning
Approved For Drafting
Approved For Publishing Review
Approved For Public Use
Approved For Campaign Use
Notes:
Must follow the Content Brain Human Approval Points Framework.
plugin_ui_authorised
Meaning:
Whether this test authorises plugin or UI work.
Future Technical Type:
boolean
Required:
Yes
Human Controlled:
Yes
Default Value:
false
supabase_build_authorised
Meaning:
Whether this test authorises Supabase table creation or build work.
Future Technical Type:
boolean
Required:
Yes
Human Controlled:
Yes
Default Value:
false
automation_authorised
Meaning:
Whether this test authorises automation.
Future Technical Type:
boolean
Required:
Yes
Human Controlled:
Yes
Default Value:
false
worker_authorised
Meaning:
Whether this test authorises worker setup.
Future Technical Type:
boolean
Required:
Yes
Human Controlled:
Yes
Default Value:
false
m_handoff_authorised
Meaning:
Whether this test authorises M handoff.
Future Technical Type:
boolean
Required:
Yes
Human Controlled:
Yes
Default Value:
false
approval_status
Meaning:
Current approval status for the test record or any next action.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Default Technical Value:
human_approval_required
Recommended Technical Values:
human_approval_required
approved_for_manual_planning
approved_for_drafting
approved_for_revision
approved_for_review
approved_for_publishing_review
approved_for_public_use
approved_for_campaign_use
approved_for_future_specification_planning
approved_for_build_ready_specification_planning
approved_for_m_handoff
do_not_approve
Display Labels:
Human Approval Required
Approved For Manual Planning
Approved For Drafting
Approved For Revision
Approved For Review
Approved For Publishing Review
Approved For Public Use
Approved For Campaign Use
Approved For Future Specification Planning
Approved For Build Ready Specification Planning
Approved For M Handoff
Do Not Approve
approval_owner
Meaning:
Human or Brain authority required for approval.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Recommended Technical Values:
martyn
headoffice
affiliate_brain
compliance_brain
research_brain
search_intelligence_brain
ads_brain
conversion_brain
data_brain
finance_brain
strategy_brain
sit_brain
unknown
Record Status Fields
status
Meaning:
Current record status.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Default Technical Value:
draft
Recommended Technical Values:
draft
completed
parked
needs_review
superseded
archived
Display Labels:
Draft
Completed
Parked
Needs Review
Superseded
Archived
created_at
Meaning:
Date and time the record was created.
Future Technical Type:
timestamptz
Required:
Yes
Human Controlled:
No
updated_at
Meaning:
Date and time the record was last updated.
Future Technical Type:
timestamptz
Required:
Yes
Human Controlled:
No
reviewed_at
Meaning:
Date and time the record was last human reviewed.
Future Technical Type:
timestamptz
Required:
No
Human Controlled:
Yes
created_by
Meaning:
Who created the record.
Future Technical Type:
text
Required:
Yes
Human Controlled:
Yes
Recommended Technical Values:
martyn
headoffice
content_brain_manual_workflow
reviewed_by
Meaning:
Who reviewed the record.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Recommended Technical Values:
martyn
headoffice
content_brain_manual_workflow
Linkage And Migration Fields
wordpress_record_link
Meaning:
Temporary link to a WordPress test record page if one exists.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Notes:
Useful while migrating Tests 1 to 5 later.
appendix_link
Meaning:
Optional link to longer supporting evidence if needed.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Notes:
Only use when long evidence exists outside the core record.
migration_status
Meaning:
Tracks whether a WordPress test page has been migrated to Supabase.
Future Technical Type:
text
Required:
No
Human Controlled:
Yes
Recommended Technical Values:
not_started
ready_to_migrate
migrated
checked
wordpress_page_can_stay
wordpress_page_can_retire_later
Display Labels:
Not Started
Ready To Migrate
Migrated
Checked
WordPress Page Can Stay
WordPress Page Can Retire Later
related_request_id
Meaning:
Optional future link to a MWMS Brain Request if the test is ever created from a formal request.
Future Technical Type:
uuid
Required:
No
Human Controlled:
No
Future Relationship:
mwms_brain_requests.id
Important Rule:
Do not require this for manual tests.
related_task_id
Meaning:
Optional future link to a MWMS Task if the test is ever created through the task system.
Future Technical Type:
uuid
Required:
No
Human Controlled:
No
Future Relationship:
mwms_tasks.id
Important Rule:
Do not require this for manual tests.
Do not create task system dependency before task routing is approved.
meta_json
Meaning:
Optional metadata for future use.
Future Technical Type:
jsonb
Required:
No
Human Controlled:
No
Default:
empty object
Important Rule:
Do not hide required business logic inside meta_json.
Use meta_json only for flexible non-core metadata.
Fields That Must Stay Human Controlled
The following fields must stay human controlled:
test_number
test_name
source_reviewed
source_url
source_type
test_type
secondary_test_types_json
result
build_readiness_signal
build_readiness_verdict
key_finding
evidence_summary
friction_found_json
compliance_risk_level
compliance_risk_notes
offer_evidence_status
routing_recommendation_json
routing_notes
recommended_next_action
downstream_content_authorised
downstream_content_authorisation_scope
plugin_ui_authorised
supabase_build_authorised
automation_authorised
worker_authorised
m_handoff_authorised
approval_status
approval_owner
status
reviewed_at
created_by
reviewed_by
wordpress_record_link
appendix_link
migration_status
Human control is required because these fields affect interpretation, authority, approval, routing, and build risk.
Fields That May Be System Generated Later
The following fields may be system generated later if a build is approved:
id
created_at
updated_at
related_request_id
related_task_id
meta_json
System generation must not replace human approval.
What This Structure Must Not Automate Yet
This future structure must not automatically:
create content briefs
create SEO briefs
create articles
create affiliate content packs
create bridge page rewrites
create landing page refresh drafts
create Google Ads copy
create campaign assets
approve publishing
approve claims
approve offer evidence
approve compliance
route to Brain Room
create tasks
start Supabase build
start plugin UI
start dashboards
start workers
notify M
update the Content Brain Page Registry
delete WordPress test pages
archive WordPress test pages
What This Structure Should Support Later
If approved later, this future structure should support:
manual Site Intelligence record storage
record filtering
record review
record migration from WordPress
test type analysis
friction pattern analysis
build readiness signal review
compliance risk review
offer evidence risk review
routing recommendation review
future UI list views
future dashboard summaries
future manual review queues
future migration decisions
future evidence review
Future Content Brain UI Relationship
A future Content Brain UI may later use this table to let Martyn:
create a Site Intelligence test record
select test type
enter source reviewed
enter source URL
record result
record friction
record build readiness signal
record key finding
flag compliance risk
flag offer evidence status
choose routing recommendation
record recommended next action
mark approval status
link to a WordPress test page if one exists
filter tests by type
filter tests by result
filter tests by compliance risk
filter tests by build readiness signal
filter tests needing review
filter records ready for migration
The future UI must not:
auto create public content
auto create content briefs
auto route to Brain Room
auto create tasks
auto approve build work
auto notify M
auto update WordPress pages
auto update the Registry
Future Dashboard Relationship
A future dashboard may later summarise:
total Site Intelligence tests
tests by result
tests by test type
tests by friction type
tests by compliance risk level
tests by offer evidence status
tests by build readiness signal
tests needing human review
tests ready for migration
WordPress records not yet migrated
The dashboard must not be built from this page.
A separate build ready technical specification would be required.
Future Worker Relationship
A future worker may later support low risk record handling only after approval.
Possible future worker support:
record timestamp update
record list sync
migration status reporting
safe filtering
dashboard summary refresh
Future worker must not:
interpret claims
approve compliance
approve offer evidence
approve publishing
create downstream content
create cross brain tasks
start M handoff
delete WordPress pages
Relationship To MWMS Supabase Naming Standard
This planning structure follows MWMS Supabase naming discipline.
Future identifiers should use:
lowercase
snake_case
plural table names
uuid primary keys
timestamptz timestamp fields
jsonb for JSON fields
clear lineage fields where needed
No spaces.
No hyphens.
No camelCase.
No PascalCase.
No special characters.
Relationship To MWMS Supabase Task Schema Standard
This table is not a canonical task table.
It does not replace:
mwms_brain_requests
mwms_tasks
mwms_task_events
mwms_task_artifacts
mwms_decision_records
mwms_lessons_learned
This future table may later connect to task lineage only through optional fields:
related_request_id
related_task_id
Manual Site Intelligence tests should not require task system linkage until Brain Room routing or formal task creation is approved.
Relationship To Content Brain Future Fields To Define Later Framework
The fields in this page are still planning fields.
They are not approved database fields yet.
They are not approved UI fields yet.
They are not approved automation triggers yet.
They are not approved M build instructions.
Field promotion must follow the future field path:
Manual Language Only
Future Field Candidate
Standardisation Needed
Manual Testing Required
Specification Candidate Field
Build Ready Field Candidate
Approved Technical Field
This page moves the Site Intelligence test fields into:
Specification Candidate Field
It does not move them into:
Approved Technical Field
Relationship To Content Brain Human Approval Points Framework
This structure protects human approval by making approval and build control fields explicit.
The following must default to false:
downstream_content_authorised
plugin_ui_authorised
supabase_build_authorised
automation_authorised
worker_authorised
m_handoff_authorised
Approval scope must remain clear.
A test may be useful.
A test may pass.
A test may show a strong build signal.
A test may show a moderate build signal.
None of these automatically authorise downstream content, Supabase, plugin UI, automation, workers, M handoff, or build work.
Relationship To Content Brain Site Intelligence Test Log
The Site Intelligence Test Log should remain a short WordPress summary page.
It should record:
test number
test name
result
build readiness signal
key finding
friction found
recommended next action
status
The future Supabase table should hold structured repeatable records.
The log should not become the database.
Relationship To Content Brain Page Registry
The Content Brain Page Registry should track this page once created.
The Registry should not list every future field.
The Registry should only identify this page as a Draft Future Supabase Planning Specification under Content Brain.
A Registry update may be needed if this page is created.
Relationship To Existing Site Intelligence Test Pages
Existing Tests 1 to 5 may remain temporarily in WordPress.
When Supabase storage exists, each record can be reviewed.
Possible migration actions:
migrate into Supabase
keep as historical WordPress page
archive later
retire later
leave untouched
No automatic deletion.
No automatic retirement.
No automatic migration without review.
Drift Protection
This structure prevents:
repeatable test records becoming endless WordPress pages
test records being confused with build approval
build readiness signals being treated as build approval
future fields being treated as approved technical fields
planning pages being handed to M as implementation instructions
Supabase table creation before approval
SQL creation before approval
plugin UI planning before approval
dashboard creation before approval
worker setup before approval
automation triggers before approval
Brain Room routing before approval
Content Brain approving its own downstream actions
approval scope becoming vague
WordPress becoming the long term test database
migration deleting useful history too early
Recommended Next Step
Create this page under Content Brain only if HeadOffice chooses to preserve the reusable future Supabase structure.
Recommended choice:
Create this page.
Reason:
This is not another test record.
This is a reusable future storage planning specification that prevents future WordPress page bloat.
After creating this page:
Do not create SQL.
Do not create a Supabase table.
Do not create plugin UI.
Do not create dashboard work.
Do not create worker setup.
Do not create automation.
Do not create M handoff.
Next useful future step after this page is created:
Update the Content Brain Page Registry only if needed to record this new planning page and corrected Test 5 parent status.
Change Impact Declaration
Pages Created:
Content Brain Site Intelligence Test Record Supabase Structure
Pages Updated:
None inside this action unless Registry is updated later
Pages Replaced:
None
Pages Deleted:
None
Pages Renamed:
None
Registry Update Required:
Yes, if this page is created
Recommended Registry Timing:
After this page is saved and visible under Parent: Content Brain
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:
Planning only
No Supabase build started
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 Research Brain Impact:
None
Page Count Impact:
Increase by 1 if created as a new WordPress page
Change Log
Version: v1.0
Date: 2026-06-10
Author: HeadOffice
Change:
Created Content Brain Site Intelligence Test Record Supabase Structure as a Draft Future Supabase Planning Specification.
Defined the recommended future Supabase table name content_brain_site_intelligence_tests.
Defined table purpose, core record fields, approval and build control fields, record status fields, linkage and migration fields, human controlled fields, system generated fields, non automation boundaries, future UI relationship, future dashboard relationship, future worker relationship, relationships to MWMS Supabase Naming Standard, MWMS Supabase Task Schema Standard, Content Brain Future Fields To Define Later Framework, Content Brain Human Approval Points Framework, Content Brain Site Intelligence Test Log, Content Brain Page Registry, and existing Site Intelligence test pages.
Confirmed that future repeatable Site Intelligence test records should move to Supabase after approval instead of continuing to become WordPress pages.
Confirmed this page is planning only and does not authorise SQL, Supabase build, plugin UI, dashboard, automation, workers, Brain Room routing, AI Employees, cross brain task wiring, or M handoff.
End Of Day Save Point Template
Page list checked:
Yes / No
Content Brain Site Intelligence Test Log v1.6 confirmed:
Yes / No
Test Records 1 to 5 confirmed:
Yes / No
Test 5 parent corrected to Content Brain:
Yes / No
Content Brain Site Intelligence Test Record Supabase Structure created:
Yes / No
Parent set to Content Brain:
Yes / No
Status set to Draft Future Supabase Planning Specification:
Yes / No
Supabase table created:
Yes / No
Recommended answer should be No
SQL created:
Yes / No
Recommended answer should be No
Plugin UI started:
Yes / No
Recommended answer should be No
Dashboard started:
Yes / No
Recommended answer should be No
Worker setup started:
Yes / No
Recommended answer should be No
Automation started:
Yes / No
Recommended answer should be No
Brain Room routing started:
Yes / No
Recommended answer should be No
M handoff authorised:
Yes / No
Recommended answer should be No
Registry updated:
Yes / No
New pages created today:
Yes / No
Pages created today:
Content Brain Site Intelligence Test Record Supabase Structure if created
Pages updated today:
Content Brain Site Intelligence Test Log
Content Brain Site Intelligence Test 5 The Blog Starter Refresh Before New Content Review parent corrected to Content Brain
Content Brain Page Registry if updated later
Pages deleted today:
None / other
No plugin UI started:
Yes / No
No Supabase build 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 task wiring started:
Yes / No
M’s Research Brain work untouched:
Yes / No
Target Save Point
Content Brain — Site Intelligence WordPress Test Page Bloat Contained / Test Log v1.6 Stable / Test Records 1 To 5 Confirmed / Test 5 Parent Corrected / Site Intelligence Test Record Supabase Structure Created As Planning Only / Supabase Build Not Started / Manual Workflow Only / Plugin UI Not Started
Final Rule
This page is a planning specification only.
Do not create SQL from this page.
Do not create Supabase tables from this page.
Do not create plugin UI from this page.
Do not create dashboards from this page.
Do not create workers from this page.
Do not create automation from this page.
Do not create Brain Room routing from this page.
Do not create AI Employees from this page.
Do not create cross brain task wiring from this page.
Do not hand this page to M as build instructions.
Tests 1 to 5 may remain temporarily as WordPress records.
Future repeatable Site Intelligence test records should move to Supabase only after structure approval and build authorisation.
A test result is not build approval.
A build readiness signal is not build approval.
A future Supabase planning page is not build approval.
Content Brain remains Manual Workflow Only / Plugin UI Not Started.
END CONTENT BRAIN SITE INTELLIGENCE TEST RECORD SUPABASE STRUCTURE v1.0