Document Type: Standard
Status: Canon
Version: v1.2
Authority: MWMS HeadOffice
Applies To: All MWMS documentation and system design pages
Parent: MWMS Canon
Last Reviewed: 2026-03-15
Purpose
This document defines the official MWMS Document Taxonomy.
The taxonomy exists to ensure that every document within MWMS has a clear and consistent classification.
This prevents confusion about authority, scope, and intended usage.
Every MWMS document must belong to one of the defined document types.
Document types define:
• the role of the document
• the expected structure of the document
• how the document should be interpreted within the system
The taxonomy supports long-term governance and prevents structural drift as MWMS grows.
Scope
This standard applies to:
• all MWMS governance documents
• all system design pages
• all brain-level documents
• classification of documents by type
• interpretation of how documents should function within MWMS
This document governs document classification and interpretation discipline across the ecosystem.
It does not govern:
• page hierarchy on its own
• specific canon authority ordering beyond the MWMS Canon Hierarchy Map
• page naming rules beyond taxonomy alignment
• detailed body structure rules beyond the MWMS – Document Structure Standard
Those remain governed by related MWMS standards and canon documents.
Definition / Rules
Core Principle
Every MWMS document must clearly declare its Document Type within the header.
Example:
Document Type: Framework
or
Document Type: Protocol
This ensures the purpose of the document is always clear.
MWMS Document Types
MWMS uses a deliberately small taxonomy consisting of six document types.
These types cover all documentation within the system.
- Canon
Canon documents define the highest authority rules within MWMS.
Canon documents override all other documentation types.
Canon is used to define:
• core system principles
• governance rules
• non-negotiable constraints
• ecosystem definitions
Examples:
• Finance Brain Canon
• Ads Brain Canon
• Affiliate Brain Canon
Characteristics:
• highest authority level
• rarely changed
• requires deliberate governance to update
- Standard
Standards define how things must be structured across MWMS.
Standards are used for system consistency.
Examples:
• MWMS – Task Types Standard
• MWMS – Page Naming Standard
• MWMS – Document Taxonomy
Characteristics:
• defines structural rules
• applies across multiple Brains
• promotes system consistency
- Protocol
Protocols define behaviour rules and interaction processes.
Protocols specify how systems, Brains, or processes must operate.
Examples:
• MWMS – Brain Interaction Protocol
• Opportunity Promotion Protocol
• Opportunity Retirement Protocol
Characteristics:
• governs behaviour
• defines process flow
• ensures predictable system operation
- Specification
Specifications define technical or architectural design.
Specifications describe how a system component is structured or implemented.
Examples:
• SIT Engine – Minimal Design Specification
• Server Side Attribution Layer Specification
Characteristics:
• technical design documentation
• may evolve over time
• implementation reference
- Framework
Frameworks define analytical models or decision structures.
Frameworks help guide thinking, interpretation, and analysis.
Examples:
• Creative Signal Interpretation Framework
• Offer Testing Velocity Framework
• Creative Pattern Framework
Characteristics:
• analytical guidance
• decision-making support
• may evolve with experience
- Reference
Reference documents provide visibility or information surfaces.
They are not rule-defining documents.
Examples:
• Brain Registry
• Brain Interaction Map
• HeadOffice Dashboard
• Employee Registry
Characteristics:
• informational
• read-only in nature
• not rule-defining in authority
• used for visibility, lookup, or summary purposes
Header Structure
All governance documents should use the following header format.
Example header:
Document Type: Framework
Status: Active
Version: v1.0
Authority: Relevant Brain or MWMS HeadOffice
Applies To: Defined scope of the document
Parent: Relevant Parent Page
Last Reviewed: YYYY-MM-DD
Naming Alignment
Document titles should align with the taxonomy.
Examples:
• MWMS – Task Types Standard
• MWMS – Brain Interaction Protocol
• SIT Engine – Minimal Design Specification
• Creative Signal Interpretation Framework
Titles should clearly communicate the document type where possible.
Governance Note
The MWMS Document Taxonomy exists to maintain structural clarity across the ecosystem.
As MWMS grows, the taxonomy prevents confusion between:
• rules
• structures
• behaviour protocols
• technical specifications
• analytical frameworks
• reference surfaces
This ensures that the MWMS knowledge system remains understandable, maintainable, and governable over time.
Final Rule
Every MWMS document must be classified deliberately.
If a page has no clear document type, its authority and intended use are structurally unclear.
Drift Protection
The system must prevent:
• documents existing without declared type
• misclassification of governance pages
• references being treated as rule-defining authority
• frameworks being mistaken for canon
• inconsistent interpretation of document purpose
All MWMS documents must be classified deliberately.
Architectural Intent
This taxonomy exists to make the MWMS knowledge system structurally legible.
It ensures that every document can be understood in terms of authority, intended use, and system role.
By keeping the taxonomy small and consistent, MWMS reduces ambiguity and improves long-term governance discipline.
Change Log
Version: v1.2
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Standardised the page fully to the locked cleanup format for this pass. Preserved the original six-type taxonomy, header example, naming alignment guidance, governance note, drift protection, and architectural intent. Added a dedicated Final Rule section and updated the review date.
Version: v1.1
Date: 2026-03-14
Author: MWMS HeadOffice
Change: Rebuilt page to align with MWMS document standards. Added Purpose / Scope / Definition / Rules structure, added Parent field to the example header, normalised formatting, clarified Reference document interpretation, and preserved the original six-type taxonomy logic.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of MWMS Document Taxonomy defining the six document types used across the MWMS ecosystem.
END – MWMS – DOCUMENT TAXONOMY v1.2