Brain Name: Content Brain
Document Type: Draft Future UI Planning Specification
Status: Draft Future UI Planning Specification
Version: v1.0
Authority: HeadOffice
Parent: Content Brain
Last Reviewed: 2026-06-10
Content Brain Site Intelligence Records Screen Specification
Purpose
The purpose of this page is to define the first practical future Content Brain UI screen for managing Site Intelligence test records.
This screen exists because repeatable Site Intelligence test records are useful, but WordPress pages are not the right long term storage method for every test.
The future UI should give Martyn one clean place to create, review, filter, and manage Site Intelligence test records without creating more WordPress page bloat.
This page is planning only.
It is not plugin UI approval.
It is not Supabase build approval.
It is not dashboard approval.
It is not worker approval.
It is not automation approval.
It is not Brain Room routing approval.
It is not AI Employee approval.
It is not cross brain task wiring approval.
It 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 UI Planning Stage
Current page role:
Draft Future UI Planning Specification
Current maturity status:
Site Intelligence workflow useful
Tests 1 to 5 recorded
WordPress test record bloat identified
Future Supabase structure planned
First future UI surface now identified
Future UI build not authorised
Future Supabase build not authorised
Future worker setup not authorised
Future automation not authorised
Future M handoff not authorised
Screen Name
Content Brain Site Intelligence Records
Primary Job Of The Screen
The first future Content Brain UI screen should let Martyn manually record, review, filter, and manage Site Intelligence test records.
The first UI should not try to run all of Content Brain.
It should only solve the proven pain point:
Site Intelligence test records are useful, but WordPress pages are the wrong long term storage method.
Core Principle
The first UI surface should be a record management screen only.
It is not a content generator.
It is not a dashboard.
It is not an automation system.
It is not a cross brain router.
It is not an AI Employee.
It is not a WordPress page builder.
It is not a task creator.
It is not an M handoff tool.
Main Screen Areas
Record List
Purpose:
Show all Site Intelligence test records in one simple table.
Recommended visible columns:
Test Number
Test Name
Source Reviewed
Test Type
Result
Build Readiness Signal
Compliance Risk Level
Offer Evidence Status
Recommended Next Action
Approval Status
Status
Reviewed Date
Value:
Martyn can see test history without opening multiple WordPress pages.
Add New Test Record Button
Button label:
Add Site Intelligence Test Record
Purpose:
Open a simple form for a new structured test record.
Boundary:
This button must create a record only.
It must not create a WordPress page.
It must not create a content brief.
It must not trigger routing.
It must not start automation.
It must not notify M.
Test Record Form
The form should include these sections.
Basic Record Details
Test Number
Test Name
Source Reviewed
Source URL
Source Type
Test Type
Secondary Test Types
Result And Evidence
Result
Build Readiness Signal
Build Readiness Verdict
Key Finding
Evidence Summary
Friction Found
Risk And Routing
Compliance Risk Level
Compliance Risk Notes
Offer Evidence Status
Routing Recommendation
Routing Notes
Recommended Next Action
Approval And Build Control
Downstream Content Authorised
Plugin UI Authorised
Supabase Build Authorised
Automation Authorised
Worker Authorised
M Handoff Authorised
Approval Status
Approval Owner
Record Status
Status
Created By
Reviewed By
Reviewed Date
Links And Migration
WordPress Record Link
Appendix Link
Migration Status
Filters
The first useful filters should be:
Result
Test Type
Build Readiness Signal
Compliance Risk Level
Offer Evidence Status
Approval Status
Migration Status
Status
Useful filter examples:
Show all Strong Build Signal tests
Show all High Compliance Risk tests
Show all Refresh Before New Content Review tests
Show all WordPress records not migrated
Show all records needing review
Search
Search should cover:
Test Name
Source Reviewed
Source URL
Key Finding
Evidence Summary
Routing Notes
Recommended Next Action
Record Detail View
Clicking a record should open a clean detail view.
The detail view should show:
Basic details
Test outcome
Friction found
Risk notes
Routing recommendation
Recommended next action
Approval controls
WordPress record link if one exists
Migration status
The detail view should be readable like a short test record, but stored as data.
Human Approval Controls
These controls must be visible and protected.
Default values should be:
Downstream Content Authorised:
No
Plugin UI Authorised:
No
Supabase Build Authorised:
No
Automation Authorised:
No
Worker Authorised:
No
M Handoff Authorised:
No
Approval Status:
Human Approval Required
Reason:
A useful test is not approval to build, publish, route, automate, or hand work to M.
Migration Support
Because Tests 1 to 5 already exist as WordPress pages, the UI should later support:
WordPress Record Link
Migration Status
Migration Notes
Recommended migration statuses:
Not Started
Ready To Migrate
Migrated
Checked
WordPress Page Can Stay
WordPress Page Can Retire Later
Important rule:
No automatic deletion of WordPress test pages.
Migration must stay human controlled.
Recommended First Buttons
Add Site Intelligence Test Record
Save Draft
Mark Completed
Mark Needs Review
Archive Record
Open WordPress Record
Buttons Not Allowed In Version 1
Do not include buttons for:
Create Brief
Create Article
Create SEO Brief
Create Affiliate Pack
Create Bridge Page
Send To Brain Room
Create Task
Start Worker
Notify M
Build Dashboard
These are future possibilities only.
What Is Editable
Martyn should be able to edit:
Test Number
Test Name
Source Reviewed
Source URL
Source Type
Test Type
Secondary Test Types
Result
Build Readiness Signal
Build Readiness Verdict
Key Finding
Evidence Summary
Friction Found
Compliance Risk Level
Compliance Risk Notes
Offer Evidence Status
Routing Recommendation
Routing Notes
Recommended Next Action
Downstream Content Authorised
Plugin UI Authorised
Supabase Build Authorised
Automation Authorised
Worker Authorised
M Handoff Authorised
Approval Status
Approval Owner
Record Status
Reviewed By
Reviewed Date
WordPress Record Link
Appendix Link
Migration Status
What Should Be Read Only Later
The following fields should probably be system controlled if this is built later:
Record ID
Created Date
Updated Date
Related Request ID
Related Task ID
System Metadata
This is future build logic only.
What Must Stay Blocked
The first UI must not:
Create public content
Create content briefs
Create SEO briefs
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 automation
Start workers
Update the Registry
Delete WordPress test pages
Notify M
Future Supabase Relationship
This UI would eventually read and write to:
content_brain_site_intelligence_tests
WordPress should keep:
Core operating pages
Frameworks
Templates
Protocols
Short logs
Future specifications
Supabase should hold:
Repeatable Site Intelligence test records
Structured evidence
Friction
Signals
Risk levels
Routing recommendations
Migration status
Recommended Version 1 Scope
Version 1 should stay small.
Build only:
Record list
Add record form
Edit record form
Filters
Search
Record detail view
WordPress record link
Migration status
Human approval controls
Do not build dashboards yet.
Do not build workers yet.
Do not build automation yet.
Do not build content generation yet.
Do not build Brain Room routing yet.
Future Version 2 Ideas
Only later, after the record screen works:
Dashboard summary
Friction pattern summary
Build signal trend
Compliance risk overview
Offer evidence gap overview
Migration progress panel
Export records
Manual review queue
Still no automatic content creation.
Future Version 3 Ideas
Only much later:
Controlled handoff into Content Briefs
Controlled handoff into Refresh workflow
Controlled handoff into Compliance review
Controlled handoff into Affiliate Brain
Controlled handoff into Search Intelligence
Only after human approval rules are working.
Relationship To Content Brain Site Intelligence Test Record Supabase Structure
The Supabase Structure page defines the future data storage model.
This UI page defines the first future user screen that would use that storage model.
The UI should not exist without the storage model.
The storage model should not be built from this page alone.
Both remain planning only until build approval exists.
Relationship To Content Brain Human Approval Points Framework
The UI must protect human approval.
Any field that affects publishing, claims, offer evidence, compliance, routing, Supabase build, plugin UI, workers, automation, or M handoff must remain human controlled.
Default approval values should protect against accidental execution.
Relationship To Content Brain Future Fields To Define Later Framework
The UI fields listed in this page are future planning fields.
They are not approved UI fields yet.
They are not approved database fields yet.
They are not approved automation triggers yet.
They are not M build instructions.
They may only become build fields after the proper approval path.
Relationship To WordPress Test Records
Tests 1 to 5 may remain as temporary WordPress test records until Supabase storage exists.
The future UI should help track those records using:
WordPress Record Link
Migration Status
Migration Notes
No automatic deletion should happen.
Relationship To Content Brain Page Registry
The Registry should track this page as a Draft Future UI Planning Specification.
The Registry should not copy this full page.
The Registry should not become a daily change log.
One short registry entry is enough if the Registry is updated.
Drift Protection
This page prevents:
the first UI becoming too big
the first UI becoming a generator
the first UI becoming a dashboard too early
the first UI becoming a task router
the first UI becoming automation
the first UI creating WordPress pages
the first UI approving content
the first UI approving claims
the first UI approving Supabase build
the first UI notifying M
the first UI replacing human approval
WordPress page bloat continuing through test records
Recommended Next Step
Create this page under Content Brain as a short Draft Future UI Planning Specification.
After creating this page:
Do not create plugin UI.
Do not create Supabase tables.
Do not create SQL.
Do not create dashboard work.
Do not create worker setup.
Do not create automation.
Do not create Brain Room routing.
Do not create M handoff.
Change Impact Declaration
Pages Created:
Content Brain Site Intelligence Records Screen Specification
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:
Planning only
No plugin UI started
Supabase Impact:
Planning relationship 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 Records Screen Specification as a Draft Future UI Planning Specification.
Defined the first practical future Content Brain UI screen for managing Site Intelligence test records.
Confirmed the first UI should focus only on Site Intelligence record management, including record list, add and edit form, filters, search, record detail view, WordPress record link, migration status, and human approval controls.
Confirmed this page does not authorise plugin UI, Supabase build, SQL, dashboards, workers, automation, Brain Room routing, AI Employees, cross brain task wiring, or M handoff.
End Of Day Save Point Template
Content Brain Site Intelligence Records Screen Specification created:
Yes / No
Parent set to Content Brain:
Yes / No
Status set to Draft Future UI Planning Specification:
Yes / No
Plugin UI started:
Yes / No
Recommended answer should be No
Supabase build started:
Yes / No
Recommended answer should be No
SQL created:
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
Final Rule
This page is a UI planning specification only.
Do not build plugin UI from this page.
Do not create Supabase tables from this page.
Do not create SQL 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.
The first future Content Brain UI should manage Site Intelligence records only.
It should not generate content.
It should not approve content.
It should not approve claims.
It should not route work.
It should not notify M.
Content Brain remains Manual Workflow Only / Plugin UI Not Started.
END CONTENT BRAIN SITE INTELLIGENCE RECORDS SCREEN SPECIFICATION v1.0