Document Type: Protocol
Status: Active
Version: v2.0
Authority: Research Brain
Parent: Research Brain Architecture
Applies To: Central research logging, intelligence preservation, evidence tracking, hypothesis linkage, experiment-linked learning, and cross-brain research continuity across MWMS
Enforcement: SIT Monitored
Last Reviewed: 2026-03-21
Purpose
This protocol defines the mandatory structure for logging, preserving, linking, and governing research intelligence inside MWMS.
Research Intelligence Database functions as the central cumulative intelligence layer owned by Research Brain.
Its purpose is to ensure that research findings, evidence, hypotheses, experiments, and learning are preserved in a structured, reviewable, and reusable form across the ecosystem.
No research finding may be treated as durable intelligence unless it is logged.
No experiment-linked learning may be treated as reliable unless it is linked.
No Brain may rely on disconnected research notes as a substitute for structured intelligence records.
Scope
This protocol applies to:
- central research insight logging inside Research Brain
- evidence-source recording and evidence-density declaration
- confidence-level declaration
- request-to-output intelligence preservation
- hypothesis linkage to downstream experiment systems
- experiment-linked learning capture where Research Brain intelligence informs operational testing
- archival discipline for historical intelligence records
- cross-brain research continuity and reviewability
This document governs the minimum structural standard for preserving research intelligence inside MWMS.
It does not govern:
- capital allocation by itself
- experiment methodology by itself
- scaling approval by itself
- campaign execution by itself
- destination-brain operating decisions by themselves
- canon mutation by itself
Those remain governed by Finance Brain, Experimentation Brain, Affiliate Brain, Ads Brain, SIT Brain, HeadOffice, and related MWMS documents.
Core Position
Research Brain is the central intelligence authority for research preservation inside MWMS.
Research Intelligence Database is the canonical database layer for durable research memory.
Destination Brains may maintain operational logs, working notes, and downstream testing records, but those do not replace Research Brain ownership of cumulative research intelligence.
Where research originates inside another Brain, linkage discipline must be preserved back to the central Research Intelligence Database.
Definition / Rules
Canonical Ownership Rule
Research Intelligence Database is owned by Research Brain.
It exists as the central source of truth for preserved research intelligence across MWMS.
Affiliate Brain, Ads Brain, PPL Brain, AIBS Brain, Strategy Brain, and other Brains may consume, reference, extend, or operationalize this intelligence, but they do not own the primary database layer.
Entry Requirements
Before any research item is treated as preserved intelligence:
- Insight_ID must exist
- Theme_Tag must be assigned
- Evidence_Source(s) must be recorded
- Evidence_Density must be calculated
- Confidence_Level must be declared
- Source_Origin must be captured
- Destination_Brain or Intended_Use must be declared where applicable
Single-source insight = Exploratory.
High-confidence insight requires 2 or more independent sources unless explicitly classified as provisional signal only.
Request Linkage Requirements
Where research originates from a Brain request or intake item:
- Request_ID must be linked
- Originating_Brain must be recorded
- Research_Type must be declared
- Output_Status must be assigned
- Routing_Status must be preserved if the intelligence is promoted outward
No research output should become detached from the originating request chain where that chain exists.
Hypothesis / Experiment Linkage Requirements
Where research informs downstream experimentation:
- Hypothesis_Statement must be linked
- Experiment_ID must be created before launch
- Learning_Objective must be defined
- Destination_Brain must be identifiable
- Funnel_Stage or Operating_Stage must be declared where relevant
After test conclusion, within 48 hours where applicable:
- Outcome must be recorded
- Stage_Reached must be updated
- Statistical_Confidence must be entered where relevant
- Revenue_Impact or Business_Impact should be estimated where possible
- Learning_Notes must be completed
- Research linkage must remain intact
This protocol does not require Research Brain to own all experiment execution.
It requires Research Brain intelligence to remain linked where it informed the experiment.
Archive-Only Rule
No historical intelligence record may be deleted.
Archive only.
Corrections may be appended.
Status may change.
Confidence may change.
Interpretation may change.
But the historical chain must remain reviewable.
Governance Enforcement
Failure to log or link correctly:
- weakens research reliability
- prevents durable intelligence classification
- may block experiment progression where structured linkage is mandatory
- may block scaling support where evidence chain is incomplete
- triggers SIT drift concern where structural integrity is broken
Quarterly meta-analysis of preserved intelligence is mandatory.
Database Discipline Principle
This database exists to preserve cumulative intelligence, not casual notes.
Every research entry must be structured enough to support:
- future review
- cross-brain reuse
- cross-test comparison
- evidence tracking
- learning preservation
- governance enforcement
- historical traceability
If a finding cannot be traced to sources, structure, and intended use, it is not durable MWMS intelligence.
Cross-Brain Usage Rule
Research Brain owns the preserved intelligence layer.
Destination Brains may:
- request research
- consume validated intelligence
- create linked operational records
- create downstream experiments
- attach outcomes and learnings
- return updated findings back into the central intelligence chain
Destination Brains may not treat isolated local notes as a substitute for canonical research preservation.
Affiliate Brain Linkage Note
Affiliate Brain may continue logging operational research, hypotheses, experiment records, and learning needed for offer testing and execution discipline.
However, Affiliate Brain logging now operates as a linked operational layer rather than an isolated research authority.
Where Affiliate Brain creates or consumes intelligence that should persist across MWMS, linkage back to Research Brain must be preserved.
This protects the chain from:
insight → hypothesis → experiment → learning → reusable intelligence
Transition Note
This page replaces the earlier Affiliate Brain-owned posture for Research Intelligence Database.
The former model treated this database primarily as an Affiliate Brain research and experiment memory layer.
The current model repositions it under Research Brain as the central intelligence authority for MWMS, while preserving the right of operational Brains to maintain linked execution-side logging.
This change is architectural, not cosmetic.
It reflects the shift to Research Brain as the ecosystem-wide research owner.
Drift Protection
The system must prevent:
- research being stored without Insight_ID
- evidence claims without recorded sources
- high-confidence claims based on weak source density
- experiments launching without linked intelligence where linkage is required
- tests finishing without learning capture where research-informed testing occurred
- historical intelligence being deleted
- operational Brains becoming isolated intelligence silos
- scaling support being justified by disconnected notes rather than preserved evidence chains
Research intelligence must remain cumulative, reviewable, linked, and archive-only.
Architectural Intent
Research Intelligence Database exists to ensure that MWMS does not rely on memory, assumption, fragmented notes, or Brain-isolated research silos.
Its role is to preserve the chain from source to insight to hypothesis to experiment to learning so future decisions can be informed by structured historical intelligence rather than repeated guesswork.
It is the preservation layer beneath cross-brain learning.
It allows Research Brain to serve as the intelligence department for the entire ecosystem while still supporting operational Brains that need local working discipline.
Final Rule
If it is not logged, it is not learned.
If it is not linked, it is not reliable enough to support MWMS progression.
If it is preserved only inside one Brain, it is not yet ecosystem intelligence.
Change Log
Version: v2.0
Date: 2026-03-21
Author: MWMS HeadOffice / Research Brain
Change: Rebuilt page to reflect Research Brain as the central intelligence authority and moved the protocol from an Affiliate Brain-owned posture to a Research Brain-owned canonical posture. Preserved the core logging discipline, evidence-density rules, confidence requirements, archive-only rule, experiment linkage logic, and quarterly meta-analysis requirement. Added Canonical Ownership Rule, Request Linkage Requirements, Cross-Brain Usage Rule, Affiliate Brain Linkage Note, stronger Transition Note, and clarified the central-source-of-truth role of the Research Intelligence Database inside MWMS.
Version: v1.1
Date: 2026-03-15
Author: MWMS HeadOffice / Affiliate Brain
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original purpose, entry requirements, experiment logging requirements, governance enforcement, archive-only rule, and quarterly meta-analysis requirement. Added Document Type, Applies To, Purpose / Scope / Definition / Rules structure, Database Discipline Principle, Transition Note, Drift Protection, Architectural Intent, Final Rule, and updated review metadata.
Version: v1.0
Date: 2026-02-23
Author: Affiliate Brain
Change: Initial creation of Research Intelligence Database defining mandatory structure for logging research, hypotheses, experiments, and learning inside Affiliate Brain.
END – RESEARCH INTELLIGENCE DATABASE v2.0