Document Type: Standard
Status: Canon
Authority: HeadOffice
Applies To: All MWMS Brain pages
Parent: Governance
Version: v1.2
Last Reviewed: 2026-04-04
Purpose
This standard defines the mandatory header structure required for all MWMS Brain pages.
The Brain Header ensures:
• consistent machine-readable structure
• reliable cross-brain routing
• correct registry mapping
• stable automation parsing
• governance alignment across all Brains
Without a consistent header schema, Brain outputs cannot be reliably interpreted by MWMS systems or future AI Employees.
Consistency of structure ensures consistency of behaviour.
Scope
This standard applies to:
• all Brain canon pages
• all Brain standards
• all Brain protocols
• all Brain frameworks
• all Brain specifications
• all operational Brain documents
It applies to both:
new Brain pages
updated Brain pages
All Brain documents must begin with the required header structure before any narrative content.
Core Principle
Structure enables automation.
Automation requires consistency.
Consistency requires a fixed header schema.
All Brain pages must declare their structural identity in a machine-readable format at the top of the page.
If the header is missing or malformed:
the page is considered non-operational.
Mandatory Header Fields
The following fields must appear in the exact order shown:
Brain Name
Document Type
Status
Version
Authority
Applies To
Parent
Last Reviewed
Optional fields may be added below the required fields where needed.
Required Header Format
Example:
Brain Name: Affiliate Brain
Document Type: Canon
Status: Canon
Version: v3.5
Authority: HeadOffice
Applies To: Affiliate Intelligence System
Parent: Affiliate Brain
Last Reviewed: 2026-03-09
Field Definitions
Brain Name
Identifies the Brain responsible for the document.
Examples:
HeadOffice Brain
Affiliate Brain
Ads Brain
Research Brain
Experimentation Brain
Finance Brain
SIT Brain
Document Type
Defines the document classification according to MWMS Document Taxonomy.
Valid types:
Canon
Standard
Protocol
Framework
Specification
Reference
Status
Indicates governance authority level.
Common values:
Canon
Active
Draft
Reference
Canon indicates binding authority.
Version
Indicates revision number.
Must follow format:
vX.X
Examples:
v1.0
v1.3
v2.1
v3.5
Authority
Defines which entity holds governance authority over the document.
Typically:
HeadOffice
Applies To
Defines the scope of the document.
Examples:
Affiliate Intelligence System
Ads Creative System
Research Intelligence System
Entire MWMS System
Parent
Defines page hierarchy location within MWMS.
Ensures correct placement inside WordPress page structure.
Last Reviewed
Indicates most recent review date.
Format:
YYYY-MM-DD
Placement Rule
The header must appear:
at the very top of the page
before the title
before narrative content
No explanatory text may appear before the header.
Formatting Rules
Each field must:
use consistent naming
use colon separator
remain on its own line
Example:
Version: v1.2
Do not combine fields on one line.
Do not insert commentary between header fields.
Governance Role
The Brain Header Schema enables:
registry consistency
automation parsing
Brain routing reliability
structural clarity
authority mapping
It acts as the identity layer for all MWMS Brain documents.
Relationship to Monthly Change Log Handling Rule
Updating header metadata does not automatically trigger a monthly change log entry.
Monthly change log entries are only required when:
governance structure changes
system behaviour changes
architecture changes
protocol logic changes
Routine version increments or Last Reviewed updates do not require monthly change log escalation.
When required, the AI must state:
Please add this to Change Log Month
This prevents unnecessary logging workload while preserving governance traceability.
Drift Protection
The system must prevent:
missing Brain Name field
missing Document Type
missing Version
incorrect Parent placement
incorrect Applies To scope
header placement below narrative content
header field order inconsistency
Malformed headers break automation.
Malformed headers break registry mapping.
Malformed headers break system reliability.
Architectural Intent
The header schema acts as the structural identity layer for MWMS.
It ensures:
all Brain documents remain compatible
all registries remain stable
all AI Employees can interpret document authority correctly
Without a stable schema, MWMS cannot scale.
Change Log
Version: v1.2
Date: 2026-04-04
Author: HeadOffice
Change: Added alignment with Monthly Change Log Handling Rule clarifying that routine header updates or version increments do not automatically trigger monthly change log entries.
Version: v1.1
Date: 2026-03-14
Author: HeadOffice
Change: Standardised header schema field order and definitions to ensure consistent machine readability across MWMS Brain pages.
Version: v1.0
Date: 2026-03-05
Author: HeadOffice
Change: Initial creation of Brain Header Schema Standard defining required metadata structure for all Brain documents.
END MWMS BRAIN HEADER SCHEMA STANDARD v1.2