HeadOffice Page Registry

Document Type: Registry
Status: Canon
Version: v1.8
Authority: HeadOffice
Applies To: HeadOffice Brain
Parent: HeadOffice Brain
Last Reviewed: 2026-05-12


Purpose

The HeadOffice Page Registry provides a central inventory of pages governed by HeadOffice.

This registry ensures:

  • HeadOffice maintains visibility of governance-layer documentation
  • HeadOffice structural pages remain traceable
  • UI surfaces remain aligned with system architecture
  • operational dashboards remain visible within governance scope
  • structural documentation does not drift outside oversight
  • decision and messaging control layers remain visible
  • AI Employee governance remains controlled
  • Newsletter Intelligence systems remain visible and governed
  • External Change Intelligence remains visible and governed
  • Opportunity System build-control pages remain visible and governed
  • MCR to Brain Site operational wiring remains visible and governed
  • Martyn and M build-lane coordination remains structurally controlled
  • Phase-based Opportunity System build packs and acceptance checklists remain registered
  • Architecture Registry update logs remain visible and governed

The registry acts as the authoritative index of HeadOffice pages.

This version updates the registry from v1.7, which registered the Phase 3 Opportunity System Developer Build Pack and Phase 3 Acceptance Checklist.


Scope

This registry applies to:

  • HeadOffice governance pages
  • HeadOffice architecture pages
  • HeadOffice UI specification pages
  • HeadOffice operational dashboards
  • structural coordination surfaces
  • cross-Brain visibility surfaces
  • decision intelligence systems
  • messaging intelligence governance visibility
  • AI employee control systems
  • Newsletter Intelligence systems
  • External Change Intelligence systems
  • Opportunity System build-control systems
  • MCR to Brain Site operational wiring pages
  • mwmsbrain.site implementation coordination pages
  • mwmsheadofficebrain.site visibility coordination pages
  • developer build packs
  • acceptance checklists
  • implementation control briefs
  • phase-gated build documentation
  • Architecture Registry update logs

This document governs how HeadOffice pages are tracked and classified.


Registry Structure

Each page is recorded with:

  • Page Name
  • Page Type
  • Authority Level
  • Status

HEAD OFFICE PAGE REGISTRY


Core Governance

Page NamePage TypeAuthority LevelStatus
HeadOffice BrainCanonConstitutionalActive
HeadOffice Brain Employee RegistryRegistryOperationalActive
HeadOffice Page RegistryRegistryOperationalActive

Decision Intelligence Systems

Page NamePage TypeAuthority LevelStatus
MWMS Attribution Driven Decision FrameworkFrameworkConstitutionalActive
MWMS Decision Narrative FrameworkFrameworkConstitutionalActive
MWMS Action Definition FrameworkFrameworkConstitutionalActive
MWMS Output Structuring FrameworkFrameworkConstitutionalActive

Messaging Intelligence Visibility

Note: Messaging frameworks live in Affiliate Brain but must remain visible to HeadOffice.

Page NamePage TypeAuthority LevelStatus
Affiliate Brain Messaging Architecture FrameworkFrameworkSupportingActive
Affiliate Brain Strategic Narrative FrameworkFrameworkSupportingActive
Affiliate Brain Message Mapping SystemSystemSupportingActive
Affiliate Brain Messaging Canvas TemplateTemplateSupportingActive

AI Employee Governance

Page NamePage TypeAuthority LevelStatus
MWMS AI Employee Version And Canon Sync FrameworkFrameworkConstitutionalActive

UI Standards

Page NamePage TypeAuthority LevelStatus
HeadOffice UI Brain Page StandardUI StandardSupportingActive
HeadOffice UI Card And Panel Design StandardUI StandardSupportingActive
HeadOffice UI Dashboard Layout StandardUI StandardSupportingActive
HeadOffice UI Navigation And Page ArchitectureUI ArchitectureSupportingActive

UI Dashboard Specifications

Page NamePage TypeAuthority LevelStatus
HeadOffice UI MWMS System Command Center SpecUI Dashboard SpecSupportingActive
HeadOffice UI Signals Dashboard SpecUI Dashboard SpecSupportingActive
HeadOffice UI Ads Command Dashboard SpecUI Dashboard SpecSupportingActive
HeadOffice UI Affiliate And Ads Pipeline Dashboard SpecUI Dashboard SpecSupportingActive

Decision Control Dashboard

Page NamePage TypeAuthority LevelStatus
HeadOffice Attribution Decision Engine Dashboard SpecificationSpecificationConstitutionalActive

Operational Dashboards

Page NamePage TypeAuthority LevelStatus
HeadOffice Active Command DashboardUI DashboardOperationalActive
HeadOffice Cross Brain Status BoardUI DashboardOperationalActive
HeadOffice Escalation And Blockers OverviewUI DashboardOperationalActive
HeadOffice Weekly System Movement DashboardUI DashboardOperationalActive
HeadOffice Cross Brain Performance And Control Dashboard SpecificationSpecificationConstitutionalActive

Architecture Registry Update Logs

Page NamePage TypeAuthority LevelStatus
MWMS Architecture Registry Operational Infrastructure Update 2026 05 11 To 2026 05 12Architecture Update LogConstitutionalActive

Registry Notes

Architecture Registry update logs are used when a detailed architecture update is too large to keep adding directly into the main MWMS Architecture Registry.

These pages preserve detailed update history while keeping the main Architecture Registry usable as the master structural index.

The MWMS Architecture Registry Operational Infrastructure Update 2026 05 11 To 2026 05 12 records:

  • MCR to Brain Site operational wiring
  • Opportunity System Phase 1–3 build-control structure
  • mwmsbrain.site operating role
  • mwmsheadofficebrain.site visibility role
  • Supabase lineage role
  • plugin/UI execution boundaries
  • Brain Room input-surface role
  • no direct Brain site to MCR update rule
  • Architecture Registry bloat-control rule

MCR To Brain Site Operational Wiring

Page NamePage TypeAuthority LevelStatus
MWMS MCR To Brain Copy RuleStandardConstitutionalActive
MWMS MCR Brain Wiring MapReferenceConstitutionalActive
MWMS Brain Connector ArchitectureSpecificationConstitutionalActive
MWMS Brain To Brain Request ProtocolProtocolCanonActive
MWMS Standard Cross Brain FlowStandardConstitutionalActive

Registry Notes

This section governs the controlled movement between:

MCR → Brain Sites → Plugin/UI/Supabase Execution → Operational Feedback → HeadOffice Review → MCR Decision

These pages ensure:

  • MCR remains Source of Truth
  • mwmsbrain.site is treated as an operational execution site
  • mwmsheadofficebrain.site is treated as the HeadOffice visibility and reporting site
  • Brain sites cannot directly update MCR
  • plugin/UI systems cannot become hidden authority layers
  • Supabase records preserve lineage without replacing canon
  • Brain Requests remain the formal cross-Brain communication structure
  • HeadOffice controls whether operational feedback becomes MCR change

System Build And Implementation Control

Page NamePage TypeAuthority LevelStatus
MWMS Opportunity System Build OrderProtocolConstitutionalActive
MWMS Opportunity System Operating ProtocolProtocolConstitutionalActive
MWMS Opportunity System Implementation Control BriefImplementation BriefConstitutionalActive
MWMS Opportunity System Implementation Brief For MProtocolOperationalActive
MWMS Opportunity Intake Phase One Developer Build PackProtocolOperationalActive
MWMS Opportunity Intake Phase One Acceptance ChecklistProtocolOperationalActive
MWMS Opportunity System Phase Two Developer Build PackProtocolOperationalActive
MWMS Opportunity System Phase Two Acceptance ChecklistProtocolOperationalActive
MWMS Opportunity System Phase Three Developer Build PackProtocolOperationalActive
MWMS Opportunity System Phase Three Acceptance ChecklistProtocolOperationalActive

Registry Notes

The Opportunity System implementation chain now covers:

Implementation Control Brief → Implementation Brief For M → Phase One Developer Build Pack → Phase One Acceptance Checklist → Phase Two Developer Build Pack → Phase Two Acceptance Checklist → Phase Three Developer Build Pack → Phase Three Acceptance Checklist → Build Order

This chain ensures:

  • Martyn and M have clear build lanes
  • MCR remains the Source of Truth
  • M builds only approved operational surfaces
  • mwmsbrain.site receives usable operating instructions
  • Phase 1 intake must be accepted before Phase 2 evaluation begins
  • Phase 2 evaluation must be accepted before Phase 3 measurement and forecasting begins
  • Phase 3 measurement and forecasting must be accepted before Phase 4 testing begins
  • no testing, Ads execution, Finance, dashboard, automation, AI, or MCR update logic is built early
  • safe save points are required
  • acceptance checklists prevent false completion
  • HeadOffice remains the review authority

Newsletter Intelligence System

Page NamePage TypeAuthority LevelStatus
HeadOffice Newsletter Intelligence Intake FrameworkFrameworkConstitutionalActive
HeadOffice Newsletter Insight Parking SystemFrameworkConstitutionalActive
HeadOffice Newsletter Brain Routing Review FrameworkFrameworkConstitutionalActive
HeadOffice Newsletter Intelligence Operating ProtocolProtocolConstitutionalActive
HeadOffice Newsletter Intelligence Supabase Schema SpecificationSpecificationSupportingActive
HeadOffice Newsletter Intelligence Dashboard SpecificationSpecificationSupportingActive
HeadOffice Newsletter Intelligence Brain Room Integration SpecificationSpecificationSupportingActive
HeadOffice Newsletter Intelligence Daily Signal LogReferenceOperationalActive

External Change Intelligence

Page NamePage TypeAuthority LevelStatus
HeadOffice External Change Intelligence FrameworkFrameworkConstitutionalActive

Registry Integrity Rule

All HeadOffice pages must appear in this registry.

Pages not listed are considered outside governance visibility.

Registry must be updated when:

  • new pages are created
  • page purpose changes
  • dashboards are added
  • structural surfaces expand
  • new intelligence layers are introduced
  • AI systems are introduced or updated
  • Newsletter Intelligence systems are created or updated
  • External Change Intelligence systems are created or updated
  • Opportunity System build-control pages are created or updated
  • MCR to Brain Site operational wiring pages are created or updated
  • mwmsbrain.site implementation control pages are created or updated
  • mwmsheadofficebrain.site visibility pages are created or updated
  • developer build packs are created or updated
  • acceptance checklists are created or updated
  • phase-gated implementation pages are created or updated
  • Architecture Registry update logs are created or updated

Governance Role

This registry ensures HeadOffice maintains visibility over:

  • governance pages
  • decision systems
  • dashboard systems
  • implementation control pages
  • operational build sequencing
  • phase-gated build packs
  • acceptance checklists
  • cross-Brain routing standards
  • MCR to Brain Site wiring
  • Architecture Registry update logs
  • Newsletter Intelligence systems
  • External Change Intelligence systems
  • Opportunity System build-control documentation

It ensures active build systems remain visible to HeadOffice and do not drift into isolated operating areas.

It also ensures large Architecture Registry updates can be tracked in smaller dated update pages without losing governance visibility.


Relationship To Other MWMS Pages

This registry works alongside:

  • MWMS Architecture Registry
  • MWMS Architecture Registry Operational Infrastructure Update 2026 05 11 To 2026 05 12
  • MWMS MCR To Brain Copy Rule
  • MWMS MCR Brain Wiring Map
  • MWMS Brain Connector Architecture
  • MWMS Brain To Brain Request Protocol
  • MWMS Standard Cross Brain Flow
  • MWMS Opportunity System Build Order
  • MWMS Opportunity System Operating Protocol
  • MWMS Opportunity System Implementation Control Brief
  • MWMS Opportunity System Implementation Brief For M
  • MWMS Opportunity Intake Phase One Developer Build Pack
  • MWMS Opportunity Intake Phase One Acceptance Checklist
  • MWMS Opportunity System Phase Two Developer Build Pack
  • MWMS Opportunity System Phase Two Acceptance Checklist
  • MWMS Opportunity System Phase Three Developer Build Pack
  • MWMS Opportunity System Phase Three Acceptance Checklist
  • HeadOffice Newsletter Intelligence Operating Protocol
  • HeadOffice External Change Intelligence Framework

Drift Protection

This registry prevents:

  • HeadOffice pages becoming invisible
  • dashboards drifting outside governance
  • build-control pages being missed
  • MCR to Brain Site wiring being undocumented
  • Opportunity System pages becoming scattered
  • Martyn and M build lanes becoming unclear
  • developer build packs existing outside registry visibility
  • acceptance checklists being forgotten
  • HeadOffice losing oversight of mwmsbrain.site build control
  • mwmsheadofficebrain.site visibility work being disconnected
  • new operational systems bypassing HeadOffice review
  • Brain sites becoming competing authority layers
  • Phase 3 measurement and forecasting pages drifting outside registry visibility
  • testing work starting without accepted measurement and forecast planning
  • dated Architecture Registry update logs being created outside governance visibility
  • the main Architecture Registry becoming too large to maintain without supporting update logs

Architectural Intent

The HeadOffice Page Registry ensures governance-layer visibility of structural documentation and operational surfaces.

It prevents fragmentation of oversight pages and ensures dashboards, implementation briefs, wiring protocols, developer build packs, acceptance checklists, and Architecture Registry update logs remain aligned with system architecture.

The registry allows HeadOffice to maintain clarity over coordination surfaces across MWMS.

It ensures that:

  • decision systems remain visible
  • messaging systems remain governed
  • AI employees remain controlled
  • execution layers remain aligned
  • Newsletter Intelligence remains governed
  • External Change Intelligence remains governed
  • Opportunity System implementation remains governed
  • MCR to Brain Site wiring remains structurally visible
  • Architecture Registry update logs remain traceable
  • Martyn and M build lanes remain coordinated
  • Phase-based Opportunity System build packs and acceptance gates remain visible

Change Log

Version v1.8

Date: 2026-05-12
Author: HeadOffice

Change

Updated HeadOffice Page Registry to register a new Architecture Registry update log.

Registered the following newly created page:

  • MWMS Architecture Registry Operational Infrastructure Update 2026 05 11 To 2026 05 12

Added new section:

  • Architecture Registry Update Logs

Added registry notes explaining that dated Architecture Registry update logs are used to preserve detailed architecture update history while keeping the main MWMS Architecture Registry usable as the master structural index.

Updated Purpose, Scope, Registry Integrity Rule, Governance Role, Relationship To Other MWMS Pages, Drift Protection, and Architectural Intent to include Architecture Registry update logs and Architecture Registry bloat-control.


Version v1.7

Date: 2026-05-12
Author: HeadOffice

Change

Updated HeadOffice Page Registry to register Phase 3 Opportunity System build-control pages.

Registered the following newly created pages:

  • MWMS Opportunity System Phase Three Developer Build Pack
  • MWMS Opportunity System Phase Three Acceptance Checklist

Updated the System Build And Implementation Control section to include Phase 3 measurement and forecasting build documentation.

Updated registry notes to reflect the expanded Opportunity System build-control chain:

Implementation Control Brief → Implementation Brief For M → Phase One Developer Build Pack → Phase One Acceptance Checklist → Phase Two Developer Build Pack → Phase Two Acceptance Checklist → Phase Three Developer Build Pack → Phase Three Acceptance Checklist → Build Order

Updated Scope, Registry Integrity Rule, Governance Role, Relationship To Other MWMS Pages, Drift Protection, and Architectural Intent to include Phase 3 build packs, acceptance checklists, and phase-gated implementation pages.


Version v1.6

Date: 2026-05-12
Author: HeadOffice

Change

Updated HeadOffice Page Registry to reflect the new MCR to Brain Site operational wiring and Opportunity System build-control structure.

Added new sections:

  • MCR To Brain Site Operational Wiring
  • System Build And Implementation Control registry notes

Registered the following newly created pages:

  • MWMS Opportunity System Implementation Control Brief
  • MWMS Opportunity System Phase Two Developer Build Pack
  • MWMS Opportunity System Phase Two Acceptance Checklist

Added or confirmed registry visibility for:

  • MWMS MCR To Brain Copy Rule
  • MWMS MCR Brain Wiring Map
  • MWMS Brain Connector Architecture
  • MWMS Brain To Brain Request Protocol
  • MWMS Standard Cross Brain Flow
  • MWMS Opportunity System Operating Protocol
  • MWMS Opportunity System Build Order
  • MWMS Opportunity System Implementation Brief For M
  • MWMS Opportunity Intake Phase One Developer Build Pack
  • MWMS Opportunity Intake Phase One Acceptance Checklist

Updated Purpose, Scope, Registry Integrity Rule, Governance Role, Relationship To Other MWMS Pages, Drift Protection, and Architectural Intent to include Opportunity System build-control and MCR to Brain Site operational wiring.


Version v1.5

Date: 2026-04-29
Author: HeadOffice

Change

Added External Change Intelligence section and registered HeadOffice External Change Intelligence Framework.

Updated Purpose, Scope, Registry Integrity Rule, and Architectural Intent to include External Change Intelligence as a governed system layer.


Version v1.4

Date: 2026-04-29
Author: HeadOffice

Change

Added Newsletter Intelligence System section to register the full HeadOffice Newsletter Intelligence system.


Version v1.3

Date: 2026-04-26
Author: HeadOffice

Change

Major upgrade aligning registry with MWMS Architecture v4.7.


Change Impact Declaration

Pages Created:
None

Pages Updated:
HeadOffice Page Registry

Pages Deprecated:
None

Registries Requiring Update:
None

Canon Version Update Required:
Yes — updated from v1.7 to v1.8

Change Log Entry Required:
Yes — this update registers a new Architecture Registry update log.


END HEADOFFICE PAGE REGISTRY v1.8