MWMS Advanced AI Capability Activation Registry

System: MWMS
Document Type: Registry
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Version: v1.2
Primary Location: MCR
Future Operational Destination: HeadOffice Brain, AIBS Brain, Automation Brain, Product Brain, Research Brain, Prompt Vault, AI Operating Systems
Parent Page: HeadOffice
Owner: Martyn
Developer Boundary: Do Not Touch M’s Active Build Areas Unless Specifically Assigned
Source Of Truth: MCR
Last Reviewed: 2026-06-01
Source / Origin: MWMS Advanced AI Capability Activation Registry v1.1 + AI Automations by Jack — AI Agents / n8n Client Automation Block
MWMS Classification: Advanced AI Capability Registry / Deferred Capability Activation System / AIOS Future Capability Control Layer / Client Automation Capability Registry
Primary Brain: HeadOffice Brain
Supporting Brains: AIBS Brain, Automation Brain, Product Brain, Research Brain, Content Brain, Sales Brain, Customer Brain, Risk Brain, Compliance Brain, Data Brain, SIT Brain
Related Pages: MWMS Advanced AI Capability Stack Framework, MWMS Client AI Interface Selection Framework, MWMS AI Dashboard Capability Framework, MWMS Supabase RAG And Vector Memory Framework, MWMS n8n Operating And Deployment Standard, MWMS Client Intelligence Report Automation Framework, MWMS Lead Intake Qualification And Follow-Up Automation Framework, MWMS Client Communication Automation Framework, MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework, MWMS Market Driven Social Content Production Framework, MWMS AI Agent Operations Core, MWMS AI Agent Memory And Context Framework, MWMS AI Tool Permission And Access Framework, MWMS Automation Build Planning Framework, MWMS Automation Client Demo And Handover Framework, MWMS AI Operating System Architecture Framework, MWMS Context Engineering Framework, MWMS AI Automation Security And Risk Checklist, HeadOffice Kaizen Continuous Improvement Loop

Purpose

The purpose of the MWMS Advanced AI Capability Activation Registry is to prevent valuable advanced AI ideas from being forgotten, scattered, or loosely parked without a future activation path.

MWMS frequently absorbs course material, newsletters, frameworks, tool signals, automation concepts, commercial product ideas, and future capability opportunities.

Some ideas are immediately useful.

Some deserve full MCR pages straight away.

Some are valuable but not ready for implementation yet.

This registry gives every valuable advanced capability a structured home.

The registry records:

what the capability is
why it matters
which Brain owns it
which Brains support it
current status
future activation trigger
likely MWMS use case
likely AIBS use case
required governance before use
risk level
whether a full framework exists
whether a future framework is needed
what should happen next when the trigger appears

This is not a random idea list.

This is a governed activation system.

v1.2 Update Summary

The v1.2 update adds the major commercial automation capabilities extracted from the latest AI Automations by Jack — AI Agents / n8n Client Automation Block.

This block strengthened MWMS around:

n8n operating and deployment
Make↔n8n hybrid orchestration
self-hosted n8n
WhatsApp automation
VAPI voice agents
client communication automation
GoHighLevel lead intake
lead magnet reports
cold outbound enrichment
Apollo / Appify / Anymailfinder workflows
market-driven social content engines
competitor intelligence reports
WhatsApp group reports
Fireflies transcript-to-proposal automation
YouTube multilingual dubbing
client-facing PDF/report automation
Lovable front end + n8n backend patterns

Several of those capabilities have now moved from vague future ideas into governed strategic capability areas because full MCR pages have been created.

Core Doctrine

The MWMS doctrine is:

Useful ideas should not be forgotten, but they should not all be built immediately.

This registry exists to balance two risks.

The first risk is forgetting.

If MWMS parks useful ideas loosely, they may never be revisited.

The second risk is overbuilding.

If MWMS creates full systems too early, it wastes time, creates clutter, distracts M, and bloats the Blueprint.

The correct middle path is:

Register the capability now.
Give it an owner.
Give it a trigger.
Give it a risk level.
Create a framework when the capability becomes strategically important.
Build only when the constraint appears.

Registry Status Types

Each capability should be classified as one of the following:

Active: currently being used or implemented.
Active Strategic Capability: recognised as strategically important and supported by formal governance.
Framework Created: a full MCR framework exists.
Deferred: valuable but not currently needed.
Backlog Priority: should be revisited soon when related work begins.
Infrastructure Watch: monitor for future technical use.
Commercial Opportunity: likely useful for future AIBS offer design.
Prototype Candidate: useful for demos, proof-of-concepts, or M handoff mockups.
Governance Required: valuable but too risky without a dedicated framework.
Rejected: not suitable for MWMS at this time.

Registry Entry Template

Capability Name:
Capability Type:
Current Status:
Owning Brain:
Supporting Brains:
MWMS Use Case:
AIBS / Client Use Case:
Why It Matters:
Current Reason For Deferral Or Controlled Activation:
Future Activation Trigger:
Required Governance Before Use:
Risk Level:
Possible Future MCR Page / Current Framework:
Related Existing Pages:
Next Review Condition:
Notes:

Capability 1: Local Hosting / Local Models

Capability Type: Infrastructure / Private AI Model Layer
Current Status: Deferred / Infrastructure Watch
Owning Brain: Infrastructure Brain / HeadOffice Brain
Supporting Brains: AIBS Brain, Automation Brain, Data Brain, Risk Brain, Compliance Brain, Research Brain
Risk Level: Medium
Possible Future MCR Page: MWMS Local AI Hosting Decision Framework

Use Case

Local hosting may eventually support:

private document processing
offline AI workflows
high-volume low-risk summarization
lower API dependency
privacy-sensitive client systems
private AIOS positioning
local model experimentation

Activation Trigger

Activate when:

API costs become a serious constraint
client privacy requires private processing
local model quality becomes strong enough
MWMS needs bulk internal processing
AIBS needs private AI as a client offer

Registry Rule

Monitor as future infrastructure.

Do not build until a real constraint appears.

Capability 2: Chrome Extensions / Browser Copilots

Capability Type: Browser Interface / Data Capture / Workflow Trigger Layer
Current Status: Deferred / Backlog Priority
Owning Brain: Product Brain / Research Brain
Supporting Brains: Prompt Vault, Affiliate Brain, Content Brain, Research Brain, Automation Brain, Data Brain, Risk Brain, Compliance Brain
Risk Level: Medium to High
Possible Future MCR Page: MWMS Browser Copilot And Chrome Extension Framework

Use Case

Chrome extensions may support:

Prompt Vault rebuild
Prompt Saver upgrade
webpage-to-Research-Brain capture
sales page capture for Affiliate Brain
YouTube transcript capture
competitor page analysis
browser-to-MWMS workflow triggers
one-click “send to MWMS” intake

Activation Trigger

Activate when:

Prompt Vault rebuild begins
Research Brain needs browser intake
Affiliate Brain needs sales page capture
Content Brain needs web/video capture
M is ready for extension work
secure webhook/Supabase destination exists

Registry Rule

Start with a narrow MVP.

Do not build broad browser capture without privacy and permission rules.

Capability 3: Voice AI Systems

Capability Type: Voice Interface / Customer Interaction / Client Service Layer
Current Status: Commercial Opportunity / Governance Required / Strengthened By VAPI Block
Owning Brain: AIBS Brain
Supporting Brains: Customer Brain, Sales Brain, Automation Brain, Risk Brain, Compliance Brain, Operations Brain, Product Brain
Risk Level: High
Possible Future MCR Page: MWMS Voice AI Governance Framework
Related Framework: MWMS Client Communication Automation Framework

Use Case

Voice AI may support:

AI receptionist
appointment confirmation
missed-call recovery
inbound FAQ voice assistant
lead qualification
customer support triage
post-call intelligence reports

v1.2 Upgrade

The VAPI + n8n lesson strengthened this capability by showing that voice agents can connect to backend tools, retrieve product/business information, and produce end-of-call intelligence.

The important MWMS insight is:

Voice AI should not only answer calls. It should create business intelligence after the call.

Activation Trigger

Activate when:

AIBS designs AI receptionist packages
a client needs call handling
a safe internal prototype is needed
Customer Brain requires voice interface planning
post-call intelligence becomes a client product

Registry Rule

Voice AI remains high-risk.

No customer-facing voice agent should launch without script boundaries, approved knowledge, consent/disclosure rules, handoff, logging, and review.

Capability 4: AI App Builders / Build Any App In One Prompt

Capability Type: Prototype Builder / Web App Generation / Product Validation Layer
Current Status: Deferred / Prototype System / Strengthened By Lovable+n8n Pattern
Owning Brain: Product Brain
Supporting Brains: AIBS Brain, Automation Brain, UX Brain, Research Brain, Risk Brain, SIT Brain, M Development
Risk Level: Medium to High
Possible Future MCR Page: MWMS AI App Prototype Governance Standard

Use Case

AI app builders may support:

internal tool prototypes
mock dashboards
client demo interfaces
AIBS proof-of-concepts
intake apps
report generators
M handoff visuals
micro-app validation

v1.2 Upgrade

The Lovable + n8n lesson strengthened the correct architecture:

AI app builder for front-end experience → n8n for backend workflow logic → database/PDF/storage for outputs.

This is a strong future MWMS prototype pattern.

Activation Trigger

Activate when:

MWMS needs a quick demo
AIBS needs a proof-of-concept
M needs visual prototype before building
a client-facing idea needs validation
dashboard or intake app needs testing

Registry Rule

AI app builders are for prototypes and demos.

They are not production systems until hardened, tested, secured, and owned.

Capability 5: Custom GPTs

Capability Type: Lightweight Assistant / Knowledge Tool / Prototype Interface
Current Status: Active For Low-Risk Use / Governed Prototype Layer
Owning Brain: Product Brain / HeadOffice Brain
Supporting Brains: AIBS Brain, Content Brain, Sales Brain, Customer Brain, Training Brain, Risk Brain
Risk Level: Low to Medium
Possible Future MCR Page: MWMS Custom GPT Usage Standard

Use Case

Custom GPTs may support:

internal training helpers
prompt helpers
lightweight SOP assistants
content helpers
quick client demos
brand voice assistants
early Brain assistant prototypes

Activation Trigger

Create a dedicated Custom GPT standard when:

MWMS begins making repeatable GPTs
AIBS needs client demo GPTs
client data is involved
GPT sharing rules become important

Registry Rule

Custom GPTs are useful assistant prototypes.

They should not be mistaken for complete AI Operating Systems.

Capability 6: AI-Powered Dashboards

Capability Type: Reporting Interface / Client Value Proof / Operational Visibility Layer
Current Status: Active Strategic Capability / Framework Created
Owning Brain: HeadOffice Brain / Data Brain
Supporting Brains: AIBS Brain, Product Brain, Operations Brain, Automation Brain, Finance Brain, Experimentation Brain, Customer Brain, Risk Brain, Compliance Brain, SIT Brain
Risk Level: Medium
Current Framework: MWMS AI Dashboard Capability Framework

Use Case

AI dashboards may support:

HeadOffice visibility
Brain reporting
client AIOS dashboards
task monitoring
experiment results
automation health
approval queues
value proof
AI Employee performance
client reporting

Activation Trigger

Implementation expands when:

HeadOffice dashboard needs expansion
AIBS package reporting is designed
client AIOS dashboard template is required
dashboard actions need governance
client value proof becomes required

Registry Rule

AI dashboards are now governed MWMS capability.

They should prove value and support decisions, not become decoration.

Capability 7: Advanced n8n Systems

Capability Type: Automation Orchestration / Agentic Workflow / AIOS Execution Layer
Current Status: Active Strategic Capability / Framework Created
Owning Brain: Automation Brain
Supporting Brains: AIBS Brain, Data Brain, Operations Brain, Risk Brain, Compliance Brain, SIT Brain, HeadOffice Brain
Risk Level: Medium to High
Current Framework: MWMS n8n Operating And Deployment Standard
Possible Future Page: MWMS n8n Advanced Agentic Workflow Standard

Use Case

Advanced n8n may support:

Brain-to-Brain workflow automation
AI agent tool orchestration
sub-workflows
webhook-based intake
chatbot backends
voice agent backends
Supabase RAG workflows
client reporting automation
dashboard action workflows
Make↔n8n hybrid bridges
self-hosted automation infrastructure

v1.2 Upgrade

This capability is now strengthened by the new MWMS n8n Operating And Deployment Standard.

n8n is now recognised as a future MWMS automation operating layer, not just a workflow tool.

Activation Trigger

Activate deeper implementation when:

MWMS needs agentic workflow orchestration
RAG enters technical build
client AIOS backend workflows are needed
Make becomes too limited
self-hosting becomes important
M has implementation bandwidth

Registry Rule

n8n should be used when workflow depth, AIOS infrastructure, RAG, database-backed logic, or advanced orchestration is genuinely needed.

Capability 8: Chatbots

Capability Type: Conversational Interface / Support Layer / AIOS Interaction Layer
Current Status: Partially Activated Through Frameworks / Future Dedicated Governance Possible
Owning Brain: Customer Brain / AIBS Brain
Supporting Brains: Automation Brain, Data Brain, Risk Brain, Compliance Brain, Product Brain, Sales Brain, HeadOffice Brain
Risk Level: Medium to High
Possible Future MCR Page: MWMS Chatbot Memory And Handoff Standard
Related Frameworks: MWMS Client Communication Automation Framework, MWMS AI Agent Memory And Context Framework, MWMS Supabase RAG And Vector Memory Framework

Use Case

Chatbots may support:

Brain Room assistant
internal knowledge assistant
website FAQ bot
lead qualification bot
customer support triage
onboarding assistant
RAG-powered support assistant

Activation Trigger

Create dedicated chatbot standard when:

MWMS builds a chatbot
AIBS designs a client chatbot offer
customer-facing chatbot deployment becomes real
chatbot memory/database design is needed
RAG-backed chatbot implementation begins

Registry Rule

Chatbots should be treated as governed client or internal interfaces, not casual AI widgets.

Capability 9: Supabase RAG / Vector Memory Systems

Capability Type: Knowledge Retrieval Infrastructure / Vector Memory / AIOS Context Layer
Current Status: Active Strategic Capability / Framework Created
Owning Brain: Data Brain
Supporting Brains: HeadOffice Brain, AIBS Brain, Automation Brain, Research Brain, Product Brain, Operations Brain, Risk Brain, Compliance Brain, SIT Brain, Content Brain, Customer Brain
Risk Level: Medium to High
Current Framework: MWMS Supabase RAG And Vector Memory Framework

Use Case

Supabase RAG may support:

MCR knowledge retrieval
Brain page retrieval
Brain Room AI replies
AI Manager context retrieval
course absorption anti-duplication
Research Brain knowledge base
Prompt Vault search
chatbot knowledge
dashboard Q&A
client AIOS knowledge bases

Activation Trigger

Implementation activates when:

Brain Room needs source-aware replies
AI Manager needs context retrieval
MCR retrieval becomes a bottleneck
AIBS client knowledge assistant is designed
chatbot/voice agent needs approved knowledge
Prompt Vault search is rebuilt

Registry Rule

Supabase RAG is AIOS backbone infrastructure, not casual chatbot memory.

Capability 10: Client Intelligence Report Automation

Capability Type: Recurring Client Reporting / Competitive Intelligence / Business Insight Automation
Current Status: Active Strategic Capability / Framework Created
Owning Brain: AIBS Brain
Supporting Brains: Automation Brain, Research Brain, Data Brain, Sales Brain, Customer Brain, Content Brain, Risk Brain, Compliance Brain, SIT Brain
Risk Level: Medium to High
Current Framework: MWMS Client Intelligence Report Automation Framework

Use Case

Client intelligence report automation may support:

competitor monitoring
review sentiment reports
WhatsApp/community digest reports
sales call intelligence
proposal generation
AIOS monthly value reports
recurring PDF/email reports
dashboard report systems

Why It Matters

This is one of the strongest commercial capabilities from the block.

It turns automation into visible recurring value.

Activation Trigger

Implement when:

AIBS begins productizing client reporting
competitor monitoring offer is tested
client AIOS value reporting is required
Research Brain needs automated reporting
client dashboards need recurring report layers

Registry Rule

Client intelligence reports should be source-aware, fresh, client-specific, validated where needed, and connected to action.

Capability 11: Lead Intake Qualification And Follow-Up Automation

Capability Type: Lead Intake / AI Qualification / Follow-Up / Sales AIOS Layer
Current Status: Active Strategic Capability / Framework Created
Owning Brain: AIBS Brain
Supporting Brains: Sales Brain, Automation Brain, Customer Brain, Data Brain, Content Brain, Risk Brain, Compliance Brain, SIT Brain
Risk Level: Medium
Current Framework: MWMS Lead Intake Qualification And Follow-Up Automation Framework

Use Case

Lead intake automation may support:

GoHighLevel intake
form-to-CRM workflows
AI lead qualification
personalized lead magnet reports
PDF generation
follow-up email sequences
sales task creation
onboarding intake

Activation Trigger

Implement when:

AIBS needs a lead magnet system
client needs better lead qualification
GHL/form workflow becomes active
sales process needs structured intake
personalized report funnel is tested

Registry Rule

A lead intake should become a structured lead record, qualification decision, personalized response, follow-up path, and sales action.

Capability 12: Client Communication Automation

Capability Type: Customer Communication / Messaging / Voice / Chatbot / Handoff Layer
Current Status: Active Strategic Capability / Framework Created
Owning Brain: AIBS Brain
Supporting Brains: Customer Brain, Sales Brain, Automation Brain, Data Brain, Risk Brain, Compliance Brain, SIT Brain, Product Brain
Risk Level: High
Current Framework: MWMS Client Communication Automation Framework

Use Case

Client communication automation may support:

WhatsApp customer assistant
AI voice receptionist
support router
sales inquiry assistant
appointment confirmation agent
chatbot support
customer intelligence digest
FAQ improvement loops

Activation Trigger

Implement when:

AIBS designs communication packages
client support workflow needs automation
WhatsApp/voice/chatbot use case is approved
approved knowledge source exists
human handoff and logging are ready

Registry Rule

Start with routing and assisted responses before full autonomous customer communication.

Capability 13: Outbound Lead Enrichment And Cold Outreach

Capability Type: Prospect Research / Lead Enrichment / Cold Outreach Governance / Sales Intelligence
Current Status: Active Strategic Capability / Framework Created / Compliance Sensitive
Owning Brain: AIBS Brain
Supporting Brains: Sales Brain, Automation Brain, Research Brain, Data Brain, Content Brain, Compliance Brain, Risk Brain, SIT Brain
Risk Level: High
Current Framework: MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework

Use Case

Outbound systems may support:

Apollo prospect research
Appify extraction
Anymailfinder enrichment
decision-maker discovery
AI-drafted cold emails
reviewed outreach drafts
outbound experimentation dashboards
prospect fit scoring

Activation Trigger

Implement when:

AIBS needs B2B prospect research
outbound test is approved
compliance review is complete
suppression list and opt-out handling exist
outreach is human-reviewed first

Registry Rule

Start with B2B prospect research and reviewed outreach drafts before automated sending.

Capability 14: Market Driven Social Content Production

Capability Type: Content Intelligence / Social Content Automation / Market Signal Extraction
Current Status: Active Strategic Capability / Framework Created
Owning Brain: Content Brain
Supporting Brains: AIBS Brain, Research Brain, Automation Brain, Data Brain, Sales Brain, Customer Brain, Risk Brain, Compliance Brain, SIT Brain
Risk Level: Medium
Current Framework: MWMS Market Driven Social Content Production Framework

Use Case

Market-driven content may support:

source-led content angles
review-mined posts
competitor gap content
sales/support conversation content
social post drafts
platform-specific adaptation
content approval queues
client content systems

Activation Trigger

Implement when:

Content Brain needs production systems
AIBS offers client content systems
Research Brain provides market signals
client intelligence reports feed content
approval workflow exists

Registry Rule

Create content from market signals, not blank prompts.

Capability 15: Make/n8n Hybrid Orchestration

Capability Type: Cross-Platform Automation Bridge / Workflow Preservation / Hybrid Orchestration
Current Status: Active Strategic Capability / Captured Inside n8n Standard
Owning Brain: Automation Brain
Supporting Brains: HeadOffice Brain, AIBS Brain, Data Brain, Risk Brain, SIT Brain
Risk Level: Medium
Current Framework: MWMS n8n Operating And Deployment Standard
Possible Future Page: MWMS Make-n8n Hybrid Orchestration Framework

Use Case

Make/n8n hybrid orchestration may support:

keeping working Make scenarios
calling Make from n8n
calling n8n from Make
data-rich request/response workflow bridges
AI agent tool calls into existing automations
gradual migration from Make to n8n
preserving previous work

Activation Trigger

Create dedicated framework when:

multiple Make↔n8n bridges exist
production workflows depend on both
M needs formal bridge patterns
client systems use hybrid architecture

Registry Rule

Do not rebuild working Make automations just to move platforms.

Bridge first when bridging is safer.

Capability 16: Self-Hosted n8n Infrastructure

Capability Type: Automation Infrastructure / Self-Hosted Workflow Engine / AIOS Backend Layer
Current Status: Infrastructure Watch / Captured Inside n8n Standard
Owning Brain: Automation Brain / Infrastructure Brain
Supporting Brains: HeadOffice Brain, Data Brain, Risk Brain, Compliance Brain, SIT Brain, AIBS Brain
Risk Level: Medium to High
Current Framework: MWMS n8n Operating And Deployment Standard
Possible Future Page: MWMS n8n Self-Hosting Security Checklist

Use Case

Self-hosted n8n may support:

cost control
PostgreSQL-backed automation
client AIOS backend systems
self-hosted workflows
private infrastructure
advanced n8n deployments
Coolify-based service deployment

Activation Trigger

Implement when:

workflow volume justifies self-hosting
client AIOS systems need controlled backend
Make/SaaS costs become a problem
M has infrastructure bandwidth
backup/security/monitoring process exists

Registry Rule

Self-hosted n8n is infrastructure.

Do not treat it like a simple tool account.

Capability 17: Multilingual Video Repurposing

Capability Type: Content Repurposing / Translation / Video Dubbing Automation
Current Status: Deferred / Content Brain Opportunity
Owning Brain: Content Brain
Supporting Brains: AIBS Brain, Automation Brain, Risk Brain, Compliance Brain, Customer Brain
Risk Level: Medium
Possible Future MCR Page: MWMS Multilingual Video Repurposing Framework

Use Case

Multilingual video repurposing may support:

YouTube video dubbing
client content localization
multi-language course content
international content distribution
translated video assets
affiliate campaign expansion
AIBS content packages

Activation Trigger

Activate when:

MWMS needs multilingual content
client asks for video localization
Content Brain begins video repurposing packages
affiliate campaigns require non-English creatives
ElevenLabs or similar workflow becomes active

Registry Rule

Useful, but not central yet.

Keep as deferred Content Brain opportunity.

Capability 18: Transcript-To-Proposal Automation

Capability Type: Sales Enablement / Proposal Automation / Call Intelligence
Current Status: Active Commercial Opportunity / Partially Captured Inside Client Intelligence Framework
Owning Brain: Sales Brain / AIBS Brain
Supporting Brains: Automation Brain, Data Brain, Risk Brain, Compliance Brain, Customer Brain, SIT Brain
Risk Level: Medium to High
Current Framework: MWMS Client Intelligence Report Automation Framework
Possible Future Page: MWMS Sales Call To Proposal Automation Standard

Use Case

Transcript-to-proposal automation may support:

Fireflies transcript retrieval
sales call summaries
proposal drafts
PDF proposals
follow-up emails
onboarding briefs
internal sales documentation

Activation Trigger

Create dedicated page when:

MWMS begins using Fireflies transcript proposals
AIBS proposal workflow becomes active
client-facing proposal generator is designed
pricing/scope approval workflow is needed

Registry Rule

AI may draft proposals, but humans must approve scope, pricing, commitments, and commercial terms.

Current Registry Summary

Capability	Status	Priority	Risk	Framework / Future Page
Local Hosting / Local Models	Deferred / Infrastructure Watch	Later	Medium	MWMS Local AI Hosting Decision Framework
Chrome Extensions / Browser Copilots	Deferred / Backlog Priority	Medium-High	Medium-High	MWMS Browser Copilot And Chrome Extension Framework
Voice AI Systems	Commercial Opportunity / Governance Required	Medium	High	MWMS Voice AI Governance Framework
AI App Builders / One-Prompt Apps	Deferred / Prototype System	Medium	Medium-High	MWMS AI App Prototype Governance Standard
Custom GPTs	Active Low-Risk / Prototype Layer	Medium	Low-Medium	MWMS Custom GPT Usage Standard
AI-Powered Dashboards	Active Strategic / Framework Created	High	Medium	MWMS AI Dashboard Capability Framework
Advanced n8n Systems	Active Strategic / Framework Created	High	Medium-High	MWMS n8n Operating And Deployment Standard
Chatbots	Partially Activated / Future Page Possible	Medium-High	Medium-High	MWMS Chatbot Memory And Handoff Standard
Supabase RAG / Vector Memory	Active Strategic / Framework Created	High	Medium-High	MWMS Supabase RAG And Vector Memory Framework
Client Intelligence Reports	Active Strategic / Framework Created	High	Medium-High	MWMS Client Intelligence Report Automation Framework
Lead Intake + Follow-Up	Active Strategic / Framework Created	High	Medium	MWMS Lead Intake Qualification And Follow-Up Automation Framework
Client Communication Automation	Active Strategic / Framework Created	High	High	MWMS Client Communication Automation Framework
Outbound Lead Enrichment	Active Strategic / Framework Created	Medium	High	MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework
Market Driven Social Content	Active Strategic / Framework Created	High	Medium	MWMS Market Driven Social Content Production Framework
Make/n8n Hybrid Orchestration	Active Strategic / Captured	High	Medium	Future: MWMS Make-n8n Hybrid Orchestration Framework
Self-Hosted n8n	Infrastructure Watch / Captured	Medium	Medium-High	Future: MWMS n8n Self-Hosting Security Checklist
Multilingual Video Repurposing	Deferred / Content Opportunity	Later	Medium	Future: MWMS Multilingual Video Repurposing Framework
Transcript-To-Proposal Automation	Active Commercial Opportunity	Medium-High	Medium-High	Future: MWMS Sales Call To Proposal Automation Standard

Application To Course Absorption

During future course absorption, valuable but not-now capabilities should be added to this registry instead of being loosely parked.

Course absorption should classify:

immediately useful
framework required now
update existing page
registry entry only
future trigger required
rejected / not useful

Course Absorption Rule

If a course idea is useful but not ready, register it with a trigger.

Do not simply say “park it.”

Application To Newsletter Intelligence

Newsletter Intelligence often surfaces new tools, trends, and capabilities.

Useful but not-now newsletter insights should be routed here when they relate to future MWMS capability.

Examples:

new AI browser tools
new voice AI systems
new dashboard platforms
new local model infrastructure
new chatbot memory systems
new automation builders
new app generation tools
new RAG tools
new vector database tools
new prospecting tools
new content automation tools
new client-reporting tools

Newsletter Rule

A newsletter insight that could become future MWMS capability should be registered, not forgotten.

Application To AIBS Brain

AIBS Brain should use this registry as a future package-development source.

The registry helps AIBS identify future offer ingredients, such as:

AI receptionist
client dashboard
internal knowledge assistant
lead qualification chatbot
browser research copilot
private AI system
rapid prototype app
advanced n8n workflow engine
Supabase RAG knowledge assistant
client AIOS dashboard
client support chatbot
competitor intelligence report
lead magnet report system
WhatsApp customer assistant
market-driven content engine

AIBS Rule

AIBS should activate capabilities only when they can be turned into a clear client outcome.

Technology alone is not enough.

Application To Product Brain

Product Brain should use this registry to manage future MWMS product and interface ideas.

Product Brain should decide:

what deserves prototype
what deserves rejection
what should wait
what needs UX testing
what should become a full feature
what belongs in Prompt Vault
what belongs in HeadOffice
what belongs in client AIOS
what belongs in dashboard systems
what belongs in RAG-enabled interfaces

Product Rule

The registry should reduce product chaos by keeping ideas visible but controlled.

Application To Data Brain

Data Brain should use this registry for advanced data and memory capability planning.

Data Brain should track:

Supabase vector memory
RAG metadata
dashboard data sources
chat memory tables
client isolation
source freshness
retrieval filters
data quality
metric definitions
AIOS knowledge layers
lead schemas
prospect schemas
report history
content signal databases

Data Rule

Capabilities involving vector memory, dashboards, metrics, reports, leads, prospects, or source retrieval must have data governance before implementation.

Application To Automation Brain

Automation Brain should use this registry to identify which advanced capabilities require workflow orchestration.

Automation Brain should track:

n8n RAG workflows
document ingestion
webhook endpoints
dashboard action triggers
chatbot tool calls
Chrome extension workflows
voice AI workflow routing
approval automations
client AIOS execution paths
Make↔n8n bridges
report automations
lead intake automations
content production workflows

Automation Rule

Advanced capability becomes operational only when the workflow path is defined, logged, and governed.

Application To M Development

This registry does not authorize development work.

It creates future readiness.

Before M works on any listed capability, MWMS must create a separate developer brief.

That brief must define:

exact scope
current files/systems
expected outcome
what not to touch
test steps
risk controls
handoff instructions

Developer Boundary Rule

Registry entry does not equal development assignment.

M should only act when a capability has been formally activated and scoped.

Registry Governance Rules

Rule 1: Deferred Does Not Mean Forgotten

A deferred capability remains visible in this registry until activated, rejected, merged, or replaced.

Rule 2: Trigger Before Build

No deferred capability should become active without a trigger.

Rule 3: One Capability Can Feed Multiple Brains

Some capabilities may support several Brains, but one Brain must own activation.

Rule 4: Do Not Send Everything To M

M should not receive development work until the capability has a clear brief, scope, trigger, and priority.

Rule 5: Governance Before Client Use

Any capability that touches clients, customers, public content, data, money, calls, browser capture, RAG, vector memory, dashboards, outreach, messaging, reports, or live systems requires governance before deployment.

Rule 6: Prototype Before Production

Advanced capabilities should usually pass through prototype stage before becoming production systems.

Rule 7: Update This Registry After Decisions

If a capability is activated, rejected, merged, replaced, or has a framework created, this page must be updated.

Rule 8: Avoid Duplicate Pages

Before creating a new framework page, check whether the capability can be absorbed into an existing standard.

Rule 9: Commercial Potential Is Not Enough

A capability may look commercially valuable but still be deferred until MWMS can support delivery, risk, and maintenance.

Rule 10: Capability Must Serve A Constraint

Build only when the capability solves a real MWMS or client constraint.

Common Failure Modes

Failure Mode 1: Parked Means Forgotten

A useful idea is mentioned once and never revisited.

Correction:

Add it to this registry with a trigger.

Failure Mode 2: Everything Becomes A Page

Every idea becomes a full framework page too early.

Correction:

Use this registry to defer without losing the idea.

Failure Mode 3: Everything Goes To M

A capability becomes a development request before scope exists.

Correction:

Create activation brief first.

Failure Mode 4: Commercial Hype Overrides Readiness

A client-facing capability looks profitable but lacks governance.

Correction:

Require risk, compliance, support, and handoff review.

Failure Mode 5: Duplicate Capability Pages

Similar ideas create overlapping MCR pages.

Correction:

Check registry and existing pages before creating new pages.

Failure Mode 6: Trigger Is Too Vague

A capability is activated because it “might be useful.”

Correction:

Require a clear activation trigger.

Failure Mode 7: Registry Becomes Graveyard

Items are added but never reviewed.

Correction:

Review at course closeouts, AIBS planning, and quarterly capability reviews.

Failure Mode 8: Prototype Becomes Production

A quick AI app or workflow is treated as client-ready.

Correction:

Require SIT, security, governance, and ownership review before production.

Failure Mode 9: Framework Created But Registry Not Updated

A capability gets a full page, but the registry still lists it as deferred.

Correction:

Update capability status whenever a framework is created.

Failure Mode 10: Infrastructure Capability Treated As Casual Tool

RAG, vector memory, dashboards, n8n workflows, or communication automations are treated as simple tools instead of system layers.

Correction:

Route to the correct Brain and apply governance before implementation.

Strategic Summary

The MWMS Advanced AI Capability Activation Registry v1.2 reflects the completion of a major AI Automations by Jack block.

This update moves several capabilities from vague ideas into governed MWMS capability areas.

The strongest new active capability areas are:

n8n operating and deployment
client intelligence report automation
lead intake qualification and follow-up
client communication automation
outbound lead enrichment and cold outreach governance
market-driven social content production

The registry now gives MWMS a structured view of which capabilities are:

active strategic capabilities
framework-created capabilities
deferred future capabilities
commercial opportunities
infrastructure watch items
high-risk governance-required items

This prevents useful ideas from being forgotten while also preventing MWMS from building everything too early.

Final Standard

The final standard is:

Do not forget useful ideas.
Do not build them too early.
Register them.
Give them an owner.
Give them a trigger.
Give them a risk level.
Create full frameworks when the capability becomes strategically important.
Activate implementation only when the constraint appears.

This registry turns parked ideas into governed future capability.

Change Log

Version: v1.2
Date: 2026-06-01
Author: MWMS HeadOffice

Change:

Updated the MWMS Advanced AI Capability Activation Registry using the latest AI Automations by Jack — AI Agents / n8n Client Automation block.

Added or upgraded capability entries for:

Advanced n8n Systems
Client Intelligence Report Automation
Lead Intake Qualification And Follow-Up Automation
Client Communication Automation
Outbound Lead Enrichment And Cold Outreach
Market Driven Social Content Production
Make/n8n Hybrid Orchestration
Self-Hosted n8n Infrastructure
Multilingual Video Repurposing
Transcript-To-Proposal Automation

Updated Advanced n8n Systems from active learning / future implementation to Active Strategic Capability / Framework Created, linked to MWMS n8n Operating And Deployment Standard.

Added Client Intelligence Report Automation as Active Strategic Capability / Framework Created, linked to MWMS Client Intelligence Report Automation Framework.

Added Lead Intake Qualification And Follow-Up Automation as Active Strategic Capability / Framework Created, linked to MWMS Lead Intake Qualification And Follow-Up Automation Framework.

Added Client Communication Automation as Active Strategic Capability / Framework Created, linked to MWMS Client Communication Automation Framework.

Added Outbound Lead Enrichment And Cold Outreach as Active Strategic Capability / Framework Created / Compliance Sensitive, linked to MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework.

Added Market Driven Social Content Production as Active Strategic Capability / Framework Created, linked to MWMS Market Driven Social Content Production Framework.

Added Make/n8n Hybrid Orchestration as an active strategic capability captured inside the n8n standard.

Added Self-Hosted n8n Infrastructure as infrastructure watch captured inside the n8n standard.

Added Multilingual Video Repurposing as a deferred Content Brain opportunity.

Added Transcript-To-Proposal Automation as an active commercial opportunity captured inside the Client Intelligence Report Automation Framework.

Expanded Current Registry Summary, Application To AIBS Brain, Application To Product Brain, Application To Data Brain, Application To Automation Brain, Registry Governance Rules, Common Failure Modes, Strategic Summary, and Final Standard.

Purpose of update:

To keep the MWMS Advanced AI Capability Activation Registry accurate after creating new governed capability frameworks from the AI Automations by Jack n8n/client automation block, ensuring commercially valuable automation ideas are visible, owned, trigger-based, risk-classified, and ready for future activation without prematurely becoming development tasks.

Version: v1.1
Date: 2026-06-01
Author: MWMS HeadOffice

Change:

Updated the registry using the final Advanced Technology files: AI-Powered Dashboards and RAG & Supabase Masterclass.

Updated AI-Powered Dashboards from Active Concept / Future Expansion to Active Strategic Capability / Framework Created.

Added Supabase RAG / Vector Memory Systems as Active Strategic Capability / Framework Created.

Updated Advanced n8n Systems to include n8n + Supabase vector store + Postgres chat memory + reranking + webhook front-end connection as a major future implementation path.

Purpose of update:

To keep the registry accurate after creating dedicated frameworks for AI-powered dashboards and Supabase RAG/vector memory.

Version: v1.0
Date: 2026-05-31
Author: MWMS HeadOffice

Change:

Created the MWMS Advanced AI Capability Activation Registry from the AI Automations by Jack — Advanced Technology Section.

Added structured registry entries for:

Local Hosting / Local Models
Chrome Extensions / Browser Copilots
Voice AI Systems
AI App Builders / Build Any App In One Prompt
Custom GPTs
AI-Powered Dashboards
Advanced n8n Systems
Chatbots

Purpose of creation:

To create a governed activation system for valuable advanced AI capabilities that are useful to MWMS but not ready for immediate full implementation, ensuring they remain visible, owned, trigger-based, and ready for future activation.