Document Type: Standard
Status: Governance Standard
Authority: MWMS HeadOffice
Applies To: All MWMS AI-assisted development (WordPress, Supabase, VPS, APIs, executors)
Version: v1.1
Last Reviewed: 2026-03-15
Parent: MWMS Canon
Purpose
This command set provides a fast, disciplined way to run MWMS development sessions with minimal confusion and maximum safety.
It ensures that when Martyn or M work with AI inside MWMS, the AI:
• locks the correct context
• confirms environment and target
• produces copy-paste-safe outputs
• avoids screen jumps and assumptions
• declares savepoints correctly
• reduces WordPress / Supabase implementation errors
This command set is designed to be used by:
• Martyn (Plus sessions)
• M (Pro sessions)
• future MWMS developers
Scope
This standard applies to:
• all MWMS AI-assisted development sessions
• WordPress, Supabase, VPS, API, and executor build work
• command-based development control during build and debug tasks
• context-locking and safe navigation during technical work
• full-file output discipline for development sessions
• savepoint declaration during structural changes
This document governs the development command language used to control AI behaviour during MWMS technical sessions.
It does not govern:
• general non-development chat behaviour
• canon editing rules by themselves
• production deployment approval by itself
• Brain authority design by itself
• capital approval
• operational marketing execution
Those remain governed by HeadOffice, the relevant canon documents, and the applicable system-specific rules.
Definition / Rules
Core Rule
When a command is used, the AI must respond using the command’s required response format.
No analysis or instruction may begin until the required confirmations are complete.
Command Index
• MWMS DEV START
• MWMS DEV CONTEXT
• MWMS DEBUG START
• MWMS FILE REPLACE
• MWMS SQL SNIPPET
• MWMS API CHECK
• MWMS WP ADMIN PATH
• MWMS SUPABASE PATH
• MWMS SAFE SAVEPOINT
• MWMS DEV STOP
- MWMS DEV START
Use When
Starting any development session.
User Command
MWMS DEV START
Required AI Response
The AI must confirm:
• Session Type: Brain-Scoped
• Active Brain: Website / DevOps Brain (or declared Brain)
• Operating Layer: Schema / Runtime / Execution
• Build Guardrails: ON
• Full Output Rule: ON
Then ask only the minimum required next question:
• What system are we working on (WordPress / Supabase / VPS / API)?
• What is the target (file name / table / endpoint)?
- MWMS DEV CONTEXT
Use When
You want to lock context mid-session.
User Command
MWMS DEV CONTEXT
<Brain>
<Layer>
<System>
<Target>
Example
MWMS DEV CONTEXT
Affiliate Brain
Execution
WordPress Plugin
mwms-admin-affiliate-intel-view.php
Required AI Response
The AI must echo the locked context in this structure:
• Active Brain: <Brain>
• Operating Layer: <Layer>
• System: <System>
• Target: <Target>
• Build Guardrails: ON
• Full Output Rule: ON
Then proceed with the task.
- MWMS DEBUG START
Use When
You are debugging something broken.
User Command
MWMS DEBUG START
Required AI Response
The AI must ask for only these:
• exact error text (copy/paste)
• exact screen (include screenshot if available)
• what changed immediately before it broke
• target file / table / endpoint involved
The AI must then provide:
• one likely cause
• one safe diagnostic step
• one safe fix step (only after diagnostic confirms)
No multi-path branching.
- MWMS FILE REPLACE
Use When
You need a full file output.
User Command
MWMS FILE REPLACE
<filename>
Required AI Response
The AI must respond with:
• full file content (complete replacement)
• no fragments
• no patch instructions
• include unchanged sections
• include header comments if present
• must be copy-paste-ready
If the AI does not have the current file content, it must request:
Paste the current file first.
- MWMS SQL SNIPPET
Use When
You need SQL for Supabase.
User Command
MWMS SQL SNIPPET
<purpose>
Required AI Response
The AI must provide:
• one SQL snippet only
• safe defaults
• no destructive statements unless requested
• include a rollback note if the SQL changes schema
If schema-altering, the AI must also state:
Savepoint required: YES
- MWMS API CHECK
Use When
You need to verify API routes, keys, or connection logic.
User Command
MWMS API CHECK
<System>
<Endpoint>
Required AI Response
The AI must confirm:
• which API (OpenAI / Supabase / WP REST)
• which credential is used (key location, not the key)
• which environment (dev / prod)
• one verification step
• one safe corrective step
- MWMS WP ADMIN PATH
Use When
You need exact click-path instructions in WordPress admin.
User Command
MWMS WP ADMIN PATH
<goal>
Required AI Response
The AI must provide:
• one navigation path only
• left-menu names exactly
• the final screen name
• what to click next
The AI must not provide alternative paths unless requested.
- MWMS SUPABASE PATH
Use When
You need exact click-path instructions in Supabase UI.
User Command
MWMS SUPABASE PATH
<goal>
Required AI Response
The AI must provide:
• one navigation path only
• exact sidebar names
• the final tab name
• what to click next
- MWMS SAFE SAVEPOINT
Use When
You changed schema, policies, executors, or Canon.
User Command
MWMS SAFE SAVEPOINT
<identifier>
<what changed>
<where>
Required AI Response
The AI must produce a savepoint record including:
• Identifier
• Date
• Location
• System State
• What Changed
• Rollback Target
• Notes (if needed)
No extra commentary.
- MWMS DEV STOP
Use When
You want the AI to stop and reset.
User Command
MWMS DEV STOP
Required AI Response
The AI must respond with:
Session stopped.
State preserved.
Next required input: <what to provide next>
No further steps until the user restarts with a command.
Operating Guarantees
When these commands are used, the AI must always:
• avoid assumptions
• avoid screen jumps
• provide one path forward
• produce full file replacements when editing
• request current file content if missing
• declare savepoints for structural changes
Final Rule
Development speed never outranks development control.
If a command is invoked, the AI must obey the command format exactly and remain inside the declared build guardrails.
Drift Protection
The system must prevent:
• development sessions starting without context lock
• AI giving multi-path instructions during controlled build work
• partial file edits being treated as acceptable replacements
• debugging sessions branching into uncontrolled speculation
• schema-changing SQL being delivered without savepoint awareness
• WordPress or Supabase navigation guidance becoming vague or inconsistent
• development sessions drifting into assumption-based instruction
The command set must keep technical work precise, narrow, and safe.
Architectural Intent
MWMS – Developer Command Set exists to give MWMS a disciplined operating language for AI-assisted build work.
Its role is to reduce developer friction, prevent avoidable implementation mistakes, and create a repeatable control surface for WordPress, Supabase, VPS, API, and executor sessions so technical work stays governed rather than chaotic.
Change Log
Version: v1.1
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original purpose, core rule, command list, command behaviours, required AI response structures, and operating guarantees. Added Document Type, Parent, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of MWMS – Developer Command Set defining the controlled command language for MWMS AI-assisted development sessions.
END – MWMS – DEVELOPER COMMAND SET v1.1