Document Type: Standard
Status: Canon
Authority: HeadOffice
Applies To: All MWMS documentation
Parent: Governance
Version: v1.2
Last Reviewed: 2026-04-04
PurPurpose
This document defines the classification structure used to organise all MWMS documents.
Clear taxonomy ensures:
• consistent document structure
• reliable governance enforcement
• predictable page placement
• correct authority alignment
• stable system scaling
Without a defined taxonomy, documents drift in purpose, authority, and usage.
MWMS taxonomy ensures that each document type has a defined role within the ecosystem.
Scope
This taxonomy applies to:
• canon pages
• standards
• protocols
• frameworks
• specifications
• reference documents
All MWMS pages must be assigned a Document Type from this taxonomy.
Document Type must be declared in the page header.
Core Principle
Every MWMS document must have:
a defined role
a defined authority level
a defined scope
The taxonomy prevents structural ambiguity between governance documents and operational documents.
Document Types
MWMS uses six document types.
Each type has a defined purpose and authority level.
Canon
Defines binding system authority.
Canon documents define:
rules
governance boundaries
decision authority structures
structural constraints
Canon documents override all other document types.
Examples:
HeadOffice Brain Canon
Affiliate Brain Canon
Finance Brain Canon
Experimentation Brain Canon
SIT Brain Canon
Standard
Defines required structural consistency.
Standards ensure:
format alignment
naming consistency
schema consistency
structural compatibility
Standards enable predictable system scaling.
Examples:
MWMS Page Naming Standard
MWMS Brain Header Schema Standard
AI Output Standard Full File Delivery Rule
Protocol
Defines operational procedures.
Protocols describe:
step-by-step processes
execution sequencing
implementation order
operational discipline
Protocols guide repeatable workflows.
Examples:
Brain Creation Protocol
Structured Testing Protocol
Campaign Review Protocol
Framework
Defines conceptual models used to interpret information.
Frameworks describe:
decision models
evaluation structures
analysis methods
interpretation structures
Frameworks guide thinking structure.
Examples:
Hook Market Fit Model
Creative Angle Matrix
Two Hurdle Diagnostic Framework
Specification
Defines technical structure.
Specifications describe:
data schemas
system architecture
API structure
database structure
technical configuration
Specifications enable reliable implementation.
Examples:
SIT Log Schema
Brain Connector Architecture
Task Event Schema
Reference
Stores supporting knowledge that informs decision making but does not enforce behaviour.
Reference documents:
provide context
store research
capture observations
preserve future insights
Reference documents do not define system rules.
Examples:
Customer Experience Optimization Principles
Future Brain Ecommerce Optimization Brain Concept
Classification Rule
Each MWMS page must declare exactly one Document Type.
The Document Type must match the document’s role.
Misclassification causes:
authority confusion
routing errors
incorrect escalation handling
system drift
If a document performs multiple roles, restructure the content into multiple documents.
Relationship to Governance Structure
Document taxonomy ensures:
HeadOffice maintains structural authority
Brains operate within defined boundaries
standards enforce consistency
protocols guide behaviour
frameworks guide thinking
specifications guide implementation
This separation maintains clarity across the ecosystem.
Relationship to Monthly Change Log Handling Rule
Changing Document Type classification rules requires a monthly change log entry.
Routine classification corrections or formatting updates do not automatically require monthly logging.
Monthly logging is required only when:
taxonomy definitions change
authority relationships change
document role definitions change
When required, the AI must state:
Please add this to Change Log Month
Drift Protection
The system must prevent:
documents without Document Type
documents with multiple conflicting roles
misclassification of Canon documents as Standards
misclassification of Reference documents as Protocols
taxonomy drift across Brains
Taxonomy drift creates governance instability.
Governance instability creates execution risk.
Architectural Intent
Taxonomy ensures MWMS remains:
structured
governable
scalable
understandable
Clear document roles enable clear decision boundaries.
Clear decision boundaries enable stable system growth.
Change Log
Version: v1.2
Date: 2026-04-04
Author: HeadOffice
Change: Added clarification of taxonomy interaction with Monthly Change Log Handling Rule to ensure only structural classification changes trigger monthly log entries.
Version: v1.1
Date: 2026-03-14
Author: HeadOffice
Change: Standardised six-document taxonomy structure and clarified role definitions.
Version: v1.0
Date: 2026-03-05
Author: HeadOffice
Change: Initial creation of MWMS Document Taxonomy defining structural classification system.
END MWMS DOCUMENT TAXONOMY v1.2