Parent: Governance
Status: Active Canon
Version: v1.0
Last Reviewed: 2026-06-11
Purpose
The MWMS Output Format Enforcement Rule exists to stop inconsistent page output, missing tracking records, missing version numbers, wrong formatting, writing block misuse, and broken change-log discipline.
This rule applies to all MWMS, MCR, Brain, Governance, Framework, Protocol, Template, Specification, and operating page outputs created in chat for WordPress or MCR use.
The purpose is simple.
If an output is intended to become a WordPress or MCR page, it must be delivered in the locked full-page format every time.
No exceptions.
Core Rule
Every MWMS / MCR / Brain page output must use the approved full-page copy/paste format.
The output must include:
Title
Parent
Status
Version
Last Reviewed
Full page body
Final Rule
System Change Log Entry
The System Change Log Entry must include:
Date
Change Type
Page Created or Page Updated
Parent
Status
Version
Reason For Change
Operating Impact
Related Pages
Registry Impact
System Change Log Impact
Boundary Confirmation
If any required element is missing, the output is invalid and must be regenerated.
Why This Exists
The MWMS system depends on clean operating records.
A page output is not only content.
A page output is part of the system architecture.
When the format changes without approval, the system becomes harder to maintain.
When version numbers are missing, the system loses traceability.
When the System Change Log Entry is missing or casual, the work becomes harder to track.
When writing blocks or wrappers are used, the output becomes harder to copy into WordPress.
When the assistant changes format from day to day, Martyn has to spend energy policing the system instead of building it.
This rule removes that problem by making the format mandatory.
Approved Output Format
All MWMS / MCR / Brain page outputs must follow this structure:
Title:
Parent:
Status:
Version:
Last Reviewed:
Purpose
Main body sections
Final Rule
System Change Log Entry
Date:
Change Type:
Page Created / Page Updated:
Parent:
Status:
Version:
Reason For Change
Operating Impact
Related Pages
Registry Impact
System Change Log Impact
Boundary Confirmation
This structure is locked unless Martyn explicitly approves a different format.
Format Preflight Requirement
Before giving any MWMS / MCR / Brain page output, the assistant must run a visible preflight check.
The preflight check must appear before the page output.
The preflight check must confirm:
Output type: Full WordPress page output
Format: Plain copy/paste text only
No writing block: Yes
No markdown wrapper: Yes
Header included: Title / Parent / Status / Version / Last Reviewed
System Change Log Entry included: Yes
Version included in System Change Log Entry: Yes
Registry impact included: Yes
Boundary confirmation included: Yes
If the assistant cannot satisfy the preflight, the page must not be output.
Plain Text Rule
MWMS / MCR / Brain page outputs must be plain copy/paste text.
Do not use:
Writing blocks
Markdown containers
Code blocks
Canvas-style wrappers
Draft boxes
Special embedded blocks
Fragmented output
Hidden formatting
The output must be directly usable for WordPress or MCR page creation.
Version Rule
Every page output must include a version number in the page header.
Every System Change Log Entry must also include the same version number.
The version number must not be implied.
The version number must not be left out of the change log.
If the page says Version: v1.0, the System Change Log Entry must also say Version: v1.0.
System Change Log Entry Rule
Every page output must end with a System Change Log Entry.
The System Change Log Entry is not optional.
It is not a casual note.
It is not a short change update.
It is not a summary.
It is the tracking record for the page.
The heading must be:
System Change Log Entry
Do not replace it with:
Change Update
Quick Update
Summary
Note
Save Point
Created Today
The System Change Log Entry must be complete enough to paste into the correct MWMS System Change Log if needed.
Registry Impact Rule
Every System Change Log Entry must include Registry Impact.
Registry Impact must say whether a registry update is required.
Examples:
Registry Impact
Governance page created.
Governance / MWMS page registry update required if the registry is being maintained today.
Registry Impact
No registry update required because no WordPress page was created or changed.
Registry Impact
Content Brain Page Registry update required because page count changed.
The registry impact must never be skipped.
Boundary Confirmation Rule
Every System Change Log Entry must include Boundary Confirmation.
Boundary Confirmation must confirm the operating boundaries that were not crossed.
Examples:
No automation started.
No worker started.
No Brain Room routing started.
No queue work started.
No generator build started.
No AI Employee work started.
No cross-brain task wiring started.
M’s Research Brain work untouched.
No content generation started unless explicitly approved.
No M handoff created unless explicitly approved.
The boundary confirmation must match the current work.
It must not be generic if the work affects a specific Brain.
Invalid Output Conditions
An output is invalid if:
It uses a writing block.
It uses a code block.
It omits the page version.
It omits the System Change Log Entry.
It calls the tracking section Change Update instead of System Change Log Entry.
It omits version from the System Change Log Entry.
It omits Registry Impact.
It omits Boundary Confirmation.
It gives a partial page when full page output was required.
It changes the approved format without Martyn’s approval.
It mixes commentary into the page body.
It creates a page without identifying the parent.
It creates a page without status.
It creates a page without Last Reviewed date.
If output is invalid, the assistant must regenerate the full page in the correct format.
No Memory Reliance Rule
The assistant must not rely on memory alone for this format.
The format must be enforced through the visible preflight check.
The preflight check exists because memory-based promises have failed.
The assistant must not say the format is fixed unless the output itself proves the format is fixed.
Correct operating pattern:
Preflight Check
Full Page Output
System Change Log Entry
Stop or wait for next instruction
Incorrect operating pattern:
Apology
Promise
Wrong format
Missing change log
Missing version
Another apology
The system must use the correct operating pattern.
Application Scope
This rule applies to:
MWMS pages
MCR pages
Brain pages
Governance pages
Framework pages
Protocol pages
Template pages
Specification pages
Registry pages
System control pages
M handoff pages
Build instruction pages
Operating model pages
Workflow pages
Save point pages
This rule does not apply to casual chat answers, quick advice, analysis, or non-page responses unless Martyn explicitly asks for WordPress-ready output.
Assistant Behaviour Rule
When Martyn asks for:
next
full page output
create this page
give me the page
MCR page
MWMS page
WordPress page
page output
the assistant must assume the locked page format is required.
The assistant must not ask whether to use the format again.
The assistant must not use a different format unless Martyn explicitly requests it.
Correction Rule
If Martyn identifies a format failure, the assistant must not give a long explanation first.
The assistant must correct the output.
The correction must include:
Preflight Check
Full corrected page output
System Change Log Entry
The assistant may briefly acknowledge the error, but the priority is correction.
Relationship To Other Governance Pages
This rule works with:
MWMS Brain Identity Gate
MWMS Department Bias Map
MWMS Core Surface Versus Support Layer Rule
The Brain Identity Gate protects against wrong-Brain drift.
The Department Bias Map protects each Brain’s department purpose.
The Core Surface Versus Support Layer Rule protects against support layers becoming the product.
This Output Format Enforcement Rule protects the delivery and tracking format.
Together, these pages prevent:
Wrong Brain bias
Support layer drift
Hidden architecture drift
Bad handoff format
Missing system tracking
Version loss
WordPress copy/paste friction
Final Rule
All MWMS / MCR / Brain page outputs must use the locked full-page format.
Every page output must include a visible preflight check before the page.
Every page output must include Title, Parent, Status, Version, Last Reviewed, full body, Final Rule, and System Change Log Entry.
Every System Change Log Entry must include Date, Change Type, Page Created or Updated, Parent, Status, Version, Reason For Change, Operating Impact, Related Pages, Registry Impact, System Change Log Impact, and Boundary Confirmation.
No writing blocks.
No casual change updates.
No missing version numbers.
No format changes unless Martyn explicitly approves them.
System Change Log Entry
Date: 2026-06-11
Change Type: Governance Control Page Created
Page Created: MWMS Output Format Enforcement Rule
Parent: Governance
Status: Active Canon
Version: v1.0
Reason For Change
Created to enforce the locked MWMS / MCR / Brain page output format after repeated format drift, missing version tracking, and inconsistent change-log handling.
This page exists so future page outputs do not rely on memory or casual promises.
Operating Impact
All future MWMS / MCR / Brain page outputs must begin with a visible Preflight Check and end with a complete System Change Log Entry.
The assistant must use plain copy/paste text only.
Writing blocks, markdown wrappers, casual Change Updates, missing version numbers, missing registry impact, and missing boundary confirmation are invalid.
Related Pages
MWMS Brain Identity Gate v1.0
MWMS Department Bias Map v1.0
MWMS Core Surface Versus Support Layer Rule v1.0
MWMS Output Format Enforcement Rule v1.0
Registry Impact
Governance page created.
Governance / MWMS page registry update required if the registry is being maintained today.
System Change Log Impact
Add this entry to the current MWMS System Change Log.
Boundary Confirmation
No automation started.
No worker started.
No Brain Room routing started.
No queue work started.
No generator build started.
No AI Employee work started.
No cross-brain task wiring started.
No content generation started.
No M handoff created.
M’s Research Brain work untouched.