Document Type: Specification
Status: Canon
Authority: HeadOffice
Applies To: HeadOffice
Parent: HeadOffice Brain
Version: v1.1
Last Reviewed: 2026-04-09
Purpose
The HeadOffice Page Registry defines the complete structural inventory of pages that belong to HeadOffice.
It exists to:
prevent duplication
prevent missing oversight components
maintain governance clarity
support structural visibility
ensure command-layer completeness
support system navigation
reduce architectural drift
The registry acts as the reference index for HeadOffice structure.
Any structural change must be reflected in this registry.
Registry Scope
The registry includes:
Canon pages
Specifications
Standards
Reference pages
UI architecture pages
dashboard specification pages
structural oversight pages
This registry tracks HeadOffice structural components only.
It does not replace:
MWMS-wide canon pages
Brain-specific canon pages
plugin implementation logic
dashboard wiring
render-layer code
Those remain governed by their own authoritative pages and implementation layers.
Structural Page List
Core Governance Layer
HeadOffice Brain
HeadOffice Page Registry
HeadOffice Brain Employee Registry
UI Standards Layer
HeadOffice UI Brain Page Standard
HeadOffice UI Card & Panel Design Standard
HeadOffice UI Dashboard Layout Standard
HeadOffice UI Navigation & Page Architecture
Command Visibility Layer
HeadOffice UI MWMS System Command Center (Spec)
HeadOffice UI Signals Dashboard (Spec)
HeadOffice UI Affiliate + Ads Pipeline Dashboard (Spec)
HeadOffice UI Ads Command Dashboard (Spec)
Cross-Brain Structural Visibility References
Affiliate Brain Page Registry
Experimentation Brain Page Registry
Finance Brain Page Registry
MWMS Brain System Map
Registry Integrity Rules
Pages must not be:
duplicated under alternate names
renamed without registry update
removed without HeadOffice review
created outside HeadOffice structural purpose
Registry must remain aligned with system reality.
HeadOffice must remain lean, high-authority, and oversight-focused.
HeadOffice should not absorb operational brain doctrine that belongs inside the Brains themselves.
Registry Change Rule
Any new HeadOffice structural page must:
be added to this registry
follow Brain Header Schema Standard
follow MWMS document structure requirements
receive HeadOffice structural validation
Registry accuracy is mandatory.
Boundary Discipline Rule
HeadOffice pages govern:
oversight
visibility
registry discipline
UI standards
navigation architecture
command-layer specifications
cross-brain structural clarity
HeadOffice does not absorb:
Affiliate Brain opportunity doctrine
Experimentation Brain signal doctrine
Finance Brain capital doctrine
Ads Brain execution doctrine
Research Brain discovery doctrine
Those remain governed by their own Brains.
Governance Alignment
HeadOffice structure operates under:
HeadOffice governance authority
MWMS Constitution
MWMS Canon hierarchy
Brain Routing Rule
MWMS Document Taxonomy
Brain Header Schema Standard
Structural discipline preserves oversight clarity.
Architectural Intent
HeadOffice must remain:
small
governed
visible
high-authority
navigation-safe
system-aware
The registry prevents HeadOffice from becoming fragmented, overloaded, or structurally ambiguous.
Change Log
Version: v1.1
Date: 2026-04-09
Author: HeadOffice
Change:
Updated HeadOffice Page Registry to align with the current live HeadOffice structure.
Confirmed clusters across:
core governance
UI standards
command visibility
Added cross-brain structural visibility references for:
Affiliate Brain Page Registry
Experimentation Brain Page Registry
Finance Brain Page Registry
MWMS Brain System Map
Improved boundary discipline so HeadOffice remains an oversight layer rather than an operational doctrine layer.
END – HEADOFFICE PAGE REGISTRY v1.1