MWMS Course Absorption Operating Rule

Document Type: Standard
Status: Canon
Authority: HeadOffice
Applies To: All MWMS course absorption work, block distillation work, and course-to-system transfer decisions
Parent: Governance
Version: v1.0
Last Reviewed: 2026-04-14

Purpose

This standard defines the operating rule for course absorption work inside MWMS.

Its purpose is to ensure that course-reading sessions remain disciplined, low-noise, and structurally useful to the ecosystem.

This rule exists to prevent course absorption from degrading into:

• premature output
• unstructured note-taking
• canon drift
• duplicate idea capture
• weak or generic lesson storage
• direct structural promotion without comparison
• confusion between course intake and MCR implementation

MWMS course absorption is not a summarization exercise.

It is a selective intelligence intake process used to improve the ecosystem.

Scope

This standard applies to:

• all course absorption threads
• all uploaded course PDFs, notes, transcripts, or lesson text
• all block-based course distillation work
• all “read only until finished” workflows
• all transfer of course insights into MCR or MWMSBrain.site
• all decisions about absorb, merge, park, or ignore outcomes

This standard governs how course absorption sessions must operate.

It does not govern:

• direct canon promotion by itself
• final MCR page creation by itself
• build implementation by itself
• plugin or Supabase changes by themselves
• final Brain authority definitions by themselves

Those remain governed by the wider MWMS governance stack.

Definition / Rules

Core Rule

Course absorption operates as intake and distillation first.

It does not operate as immediate structural creation by default.

The course absorption thread exists to:

• read material
• hold material without premature output
• distill completed blocks
• test value against MWMS needs
• classify structural fit
• prepare explicit handoff outputs

Start of Thread Rule

At the start of a course absorption thread, the operating mode is:

intake only
comparison-aware
block-based
no premature structural drafting unless explicitly requested

This operating mode remains active for the duration of that course thread unless explicitly changed.

Read and Hold Rule

Where the operator instructs:

read and do not output until finished

the AI must:

• read the supplied block
• retain block continuity
• avoid early interpretation dumps
• avoid partial recommendations
• avoid page drafting
• wait until the operator explicitly states the block is finished

Premature output is non-compliant.

Block Completion Rule

A course thread may contain many blocks.

A block is the valid unit of absorption decision.

A block may be:

• a small lesson group
• a coherent section
• a grouped subject cluster
• a larger thematic segment

The end of a block is determined by the operator, not by page count alone.

End of Block Decision Rule

When the operator declares a block finished, the AI must evaluate the block before recommending any transfer into MWMS.

The minimum evaluation sequence is:

Value Test
Novelty Test
Superiority Test
Fit Test

Value Test asks:

Does this block materially improve MWMS?

Novelty Test asks:

Is this meaningfully new relative to existing MWMS knowledge?

Superiority Test asks:

If similar material exists, is this stronger, clearer, more operational, or more scalable?

Fit Test asks:

Can this be cleanly placed into the MWMS system?

Only after these tests may a transfer recommendation be made.

Capability Extraction Rule

Course insights must be extracted at capability level, not lesson level.

Examples of capability-level extraction include:

• opportunity evaluation
• message-market fit
• audience discovery
• experiment methodology
• lead qualification
• landing page validation
• lifecycle coordination
• cross-brain communication discipline
• automation orchestration

This prevents multiple courses from being absorbed as separate duplicates when they are actually teaching the same capability in different language.

Allowed Block Outcomes

Each finished block must end in one or more of the following outcomes:

• Absorb Now
• Merge Into Existing Page
• Park For Later
• Ignore

No block should end in ambiguous state.

Comparison Requirement

Before recommending absorption, the AI must compare the block against:

• known MWMS structures
• existing absorbed concepts where visible
• current Brain authority boundaries
• known page families or frameworks already in use

The AI must explicitly state whether the block represents:

• new capability
• upgrade to existing capability
• duplicate but better replacement
• duplicate and weaker material
• useful but premature material

Environment Decision Rule

Every course absorption recommendation must classify destination as one of:

• MCR
• MWMSBrain.site
• parked for future review
• no action

MCR is used for:

• doctrine
• frameworks
• standards
• protocols
• references
• structural knowledge pages

MWMSBrain.site is used for:

• implementation
• UI
• operational surfaces
• build work
• technical wiring

No environment ambiguity is permitted.

No Direct Canon Promotion Rule

Course absorption does not promote material directly into Canon by convenience.

Where a course insight appears strong enough for higher-level structural use, it must still pass the relevant governance pathway before canon elevation.

Course quality does not bypass MWMS governance.

Governance Role

This standard acts as the session discipline layer for course absorption work.

It ensures that course threads behave as governed intake environments rather than informal idea dumps.

It protects MWMS from:

• duplication
• bloat
• premature page creation
• authority drift
• weak course-derived clutter

Relationship to Other MWMS Standards

This standard operates alongside:

• How to Start a Session MWMS Operating Guide
• AI Session Context Lock Rule
• Brain Routing Rule
• AI Output Standard Full File Delivery Rule
• MWMS Page Naming Standard
• MWMS Document Structure Standard
• MWMS Document Taxonomy
• MWMS Course Absorption Handoff Standard
• MWMS Course Absorption Handoff Queue
• MWMS Course Absorption Decision Registry

Drift Protection

The system must prevent:

• course summarization without system evaluation
• premature output before the operator says finished
• lesson-level clutter being mistaken for capability-level value
• direct structural drafting without comparison
• duplicate absorption of already-known concepts
• build recommendations being mixed into doctrine without environment declaration
• block completion without explicit outcome

Course absorption must remain selective, comparative, and structured.

Architectural Intent

MWMS Course Absorption Operating Rule exists to make course intake usable as a disciplined ecosystem improvement process.

Its role is to transform raw external education into structured MWMS intelligence without allowing hype, duplication, or weak material to pollute the system.

The goal is not to collect more information.

The goal is to extract only what materially strengthens MWMS.

Change Log

Version: v1.0
Date: 2026-04-14
Author: HeadOffice
Change: Initial creation of MWMS Course Absorption Operating Rule defining intake-only course session behaviour, block-based absorption logic, comparison requirements, capability-level extraction, and allowed block outcomes.

Change Impact Declaration

Pages Created:
MWMS Course Absorption Operating Rule

Pages Updated:
None

Pages Deprecated:
None

Registries Requiring Update:
MWMS Architecture Registry

Canon Version Update Required:
No

Change Log Entry Required:
Yes