MWMS Brain

MWMS System Dashboard

MWMS System Dashboard

Document Type: Architecture
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: MWMSBrain.site system navigation, structural orientation, and operating-layer overview
Parent: MWMS
Last Reviewed: 2026-04-03

Purpose

This page exists to serve as the primary operating-system style entry point for MWMSBrain.site.

It gives a clear top-level view of the MWMS layer structure so that humans and future AI systems can quickly understand:

  • where core governance sits
  • where architecture sits
  • where authority sits
  • where data standards sit
  • where routing logic sits
  • how the system is organised at a structural level

This page is not a deep content page.

It is the top-level dashboard and orientation layer for the site.

Scope

This page applies to:

  • MWMSBrain.site root navigation
  • structural orientation for Martyn and M
  • future dashboard and Brain navigation planning
  • future AI-assisted system navigation
  • top-level ecosystem visibility

Definition / Structure

MWMSBrain.site is organised into the following top-level layers under MWMS:

  1. MWMS Home
  2. MWMS Canon Layer
  3. MWMS Architecture Layer
  4. MWMS Authority Layer
  5. MWMS Data Layer
  6. MWMS Routing Layer

Each layer has a distinct role.

MWMS Home

Role:
Front-door overview page for the site.

Purpose:
Provides a simple landing point and immediate orientation for users entering the MWMSBrain environment.

MWMS Canon Layer

Role:
Constitutional and standards layer.

Purpose:
Holds the core documents that define structural rules, document standards, hierarchy logic, and canon discipline.

Typical contents include:

  • Canon Index
  • Canon Hierarchy Map
  • Document Structure Standard
  • Document Taxonomy
  • Brain Header Schema Standard

MWMS Architecture Layer

Role:
System design and structural map layer.

Purpose:
Holds the pages that explain how MWMS is architected as an ecosystem.

Typical contents include:

  • Architecture Registry
  • Brain Registry
  • Brain Interaction Map
  • System Architecture
  • System Layers Map
  • System Data Flow Map
  • Organisation Chart
  • Money Engine Diagram

MWMS Authority Layer

Role:
Decision and control layer.

Purpose:
Defines who has authority, what can make decisions, and where escalation boundaries sit.

Typical contents include:

  • Decision Authority Matrix
  • Brain Authority Matrix
  • authority standards and boundary pages

MWMS Data Layer

Role:
Schema and structural data standards layer.

Purpose:
Defines how tasks, events, Supabase structures, and system data objects should be organised.

Typical contents include:

  • Supabase Event Schema
  • Supabase Task Schema Standard
  • Task Architecture Standard
  • Task Types Standard
  • RLS and Append Only Enforcement
  • Finance Decision Task Schema Standard

MWMS Routing Layer

Role:
Cross-system communication and request-routing layer.

Purpose:
Defines how Brains, requests, connectors, and structured flows move across the ecosystem.

Typical contents include:

  • Brain Routing Rule
  • Brain to Brain Request Protocol
  • Brain Connector Architecture
  • Request Routing Map

Operating Use

This page should be used when:

  • starting work on MWMSBrain.site
  • orienting a new build session
  • showing the site structure to M
  • planning future dashboards
  • checking whether a new page belongs in the correct layer
  • preparing future HeadOffice / Brain interface development

Placement Rule

No loose structural pages should be created directly under MWMS unless they are intended to act as top-level system entry pages.

The preferred top-level structure under MWMS is:

  • MWMS Home
  • MWMS System Dashboard
  • MWMS Canon Layer
  • MWMS Architecture Layer
  • MWMS Authority Layer
  • MWMS Data Layer
  • MWMS Routing Layer

All supporting pages should sit underneath the appropriate layer unless there is a strong structural reason not to.

Navigation Intent

This page should eventually support a cleaner operating interface by making it obvious where each class of page belongs.

Its long-term role is to reduce:

  • structural confusion
  • misplaced pages
  • navigation drift
  • duplicated layer logic
  • wasted build effort

Architectural Intent

MWMSBrain.site must behave like a controlled system environment, not a generic content website.

This dashboard helps establish that behaviour by making the layer model visible and repeatable.

Change Log

Version: v1.0
Date: 2026-04-03
Author: MWMS HeadOffice
Change: Initial creation of MWMS System Dashboard as top-level operating and structural orientation page for MWMSBrain.site.