Document Type: Framework
Status: Structural
Authority: Research Brain
Applies To: Research Brain, Content Brain, HeadOffice, future SEO authority systems, future media intelligence systems
Parent: Research Brain
Version: v1.0
Last Reviewed: 2026-04-19
Purpose
The Research Brain Editorial Authority Acquisition Framework defines how MWMS evaluates, prioritises, and acquires editorial authority signals through safe, relevant, and risk-managed off-site visibility.
The framework exists to ensure MWMS grows authority through:
• relevant editorial placement
• topic-aligned coverage
• natural citation patterns
• risk-managed link acquisition
• publication relationship building
• sustained off-site visibility
This framework prevents authority growth from being treated as a volume game.
It ensures editorial authority is earned through relevance, consistency, and ecosystem fit.
Scope
This framework applies to:
• editorial link acquisition
• media outreach strategy
• publication prioritisation
• trade media strategy
• national media strategy
• regional media strategy
• off-site authority growth
• citation and mention strategy
• digital PR support research
• publication targeting logic
• authority-building campaign planning
This framework governs how editorial authority is interpreted and pursued.
It does not govern:
• paid media campaigns
• advertorial purchasing
• direct ad placement strategy
• technical SEO implementation
• on-site content production by itself
• creative production by itself
Those remain governed by Ads Brain, Content Brain, technical systems, and related operational frameworks.
Core Principle
Editorial authority must be built through natural relevance.
Not all links are equal.
Authority depends on:
• source relevance
• source strength
• placement context
• link diversity
• relationship credibility
• consistency over time
Editorial authority growth must remain safe, explainable, and sustainable.
Editorial Authority Model
Editorial authority is built from a mix of source types.
These source types may include:
• national media
• trade media
• regional media
• niche publishers
• industry blogs
• expert contribution environments
• editorial features
• journalist request responses
Authority value is not determined by raw scale alone.
Relevance and consistency often outperform isolated high-profile bursts.
Source Value Layers
Layer 1 — Topical Relevance
Definition:
A source should be strongly related to the topic area, customer problem, market, or industry context of the target being promoted.
Rules:
• relevant trade and niche coverage may outperform broad but weakly related coverage
• relevance must be treated as a core value signal
• unrelated links must not be pursued for volume alone
Topical alignment improves interpretability of authority.
Layer 2 — Source Strength
Definition:
Editorial sources vary in authority strength.
Indicators may include:
• domain authority
• publication reputation
• link equity strength
• audience trust
• citation value
Rules:
• high-strength sources are valuable
• source strength must be evaluated alongside relevance
• source strength alone must not override poor topical fit
Layer 3 — Placement Utility
Definition:
The value of editorial placement also depends on where and how the target is referenced.
Placement utility may include:
• early link placement
• contextual editorial mention
• homepage reference
• biography reference
• about-page reference
• asset reference
• quote attribution
Rules:
• placement context matters
• contextual editorial links are preferred over weak footer or detached mentions
• multiple unique relevant targets may increase total authority value
Layer 4 — Link Diversity
Definition:
A healthy editorial authority profile requires variety.
Diversity may include:
• publication type diversity
• geography diversity
• source format diversity
• link target diversity
• follow and no follow variation
• mention and link mix
Rules:
• diversity strengthens naturalness
• the profile must not become dependent on one source type
• repeated use of one publication tier alone weakens strategic resilience
Layer 5 — Consistency Over Time
Definition:
Authority growth should occur through an ongoing rhythm rather than isolated artificial bursts.
Rules:
• authority should be built consistently
• repeated relevant editorial visibility supports stronger long-term authority
• synthetic burst behaviour should be avoided
• sustained activity is safer than irregular high-pressure pushes
Consistency supports trust and relevance persistence.
Publication Tier Logic
Sources should be grouped according to strategic role.
Tier A — High Influence Publications
Role:
major visibility
brand trust
story ignition
coverage multiplication
Typical use:
launches
exclusive angles
high-visibility narratives
Tier B — Relevant Trade Publications
Role:
topical authority
industry validation
audience precision
high editorial fit
Typical use:
category expertise
technical stories
sector relevance
ongoing authority building
Tier C — Regional and Niche Publications
Role:
coverage extension
relationship development
topic-specific amplification
volume through relevance
Typical use:
follow-on outreach
local angle support
campaign expansion
Tier D — Request and Reactive Opportunities
Role:
quote placement
expert commentary
rapid editorial insertion
relationship seeding
Typical use:
journalist requests
comment opportunities
trend response
Source Prioritisation Rule
Publication targeting should prioritise:
- influence potential
- relevance fit
- story fit
- relationship feasibility
- link and mention utility
The strongest source is not always the first source to approach.
Sometimes the most influential source should lead.
Sometimes the most relevant source should lead.
Decision must depend on story scalability.
Risk Management Rule
Editorial authority strategy must avoid:
• manipulative link acquisition
• paid-link behaviour disguised as editorial work
• source irrelevance
• duplicate mass placements
• synthetic link bursts
• over-reliance on one campaign type
• over-reliance on one publication class
Authority loss risk must be treated as a strategic risk.
Safe growth outranks aggressive short-term gain.
Relationship to Other MWMS Systems
This framework supports:
• Content Brain asset creation
• HeadOffice integrated coordination
• future off-site authority systems
• future digital PR systems
• future SEO intelligence systems
This framework works best when paired with strong on-site support assets.
Drift Protection
The system must prevent:
• treating authority as raw link count
• ignoring trade publication value
• pursuing weak but large publications over relevant smaller ones
• assuming no follow links have zero value
• authority bursts without continuity planning
• source targeting without story fit
Editorial authority must remain relevant, natural, and defensible.
Architectural Intent
The Research Brain Editorial Authority Acquisition Framework exists to give MWMS a safe and structured model for acquiring editorial authority.
Its role is to help MWMS grow through:
• trusted visibility
• relevant publication relationships
• topic-aligned citation
• sustainable authority accumulation
This framework protects MWMS from fragile, manipulative, and low-context authority growth models.
Change Log
Version: v1.0
Date: 2026-04-19
Author: HeadOffice
Change:
Initial creation of framework defining safe, relevant, and risk-managed editorial authority acquisition logic for MWMS.
END Research Brain Editorial Authority Acquisition Framework v1.0
PAGE 2
Content Brain Press Support Asset Framework
Document Type: Framework
Status: Structural
Authority: Content Brain
Applies To: Content Brain, Research Brain, HeadOffice, future media support systems, future authority-building systems
Parent: Content Brain
Version: v1.0
Last Reviewed: 2026-04-19
Purpose
The Content Brain Press Support Asset Framework defines the on-site content and asset structures required to support editorial outreach, journalist usability, and authority-building activity across MWMS.
The framework exists to ensure outreach is supported by usable destination assets rather than weak or missing page infrastructure.
The framework supports:
• stronger editorial conversion
• easier journalist usage
• better link destination quality
• stronger authority signals
• reusable support assets
• more scalable PR and outreach systems
This framework ensures off-site effort is supported by on-site readiness.
Scope
This framework applies to:
• press centres
• biography pages
• about pages
• profile assets
• downloadable media materials
• support landing assets
• anchor content
• quote-support assets
• media image resources
• reference pages used in outreach
This framework governs support asset readiness.
It does not govern:
• core commercial landing pages
• product page merchandising
• general content calendar planning
• creative campaign ideation by itself
• direct journalist outreach by itself
Those remain governed by other Content Brain, Research Brain, and outreach systems.
Core Principle
Editorial outreach performs better when journalists are given usable assets.
A strong story is not enough.
Journalists often need:
• context
• verification
• headshots
• biographies
• images
• company summaries
• supporting pages
• link-worthy destinations
Support assets reduce friction and increase placement probability.
Support Asset Categories
Category 1 — Press Centre Assets
Purpose:
Provide a central information hub for journalists.
Core components may include:
• company summary
• key dates
• contact routes
• downloadable assets
• imagery
• report references
• team references
• social links where relevant
Rules:
• press centre must be easy to navigate
• information must be useful to journalists, not just customers
• high-friction contact pathways should be avoided
• downloadable materials should be easy to access
Category 2 — Biography Assets
Purpose:
Provide expert attribution targets for quotes and commentary.
Core components may include:
• clear name and role
• expertise summary
• career background where relevant
• category expertise
• headshot
• contact pathway where appropriate
Rules:
• biographies must signal why the person is quotable
• biography pages are valid editorial link targets
• biographies should be written for media usefulness, not vanity
Category 3 — About Assets
Purpose:
Provide company context, legitimacy, and organisational background.
Core components may include:
• company origin
• company mission
• key milestones
• company structure context
• leadership references
• major differentiators
• location and background details where relevant
Rules:
• about assets must be link-worthy
• about pages should support journalist verification needs
• company legitimacy should be clear without hype
Category 4 — Headshot and Imagery Assets
Purpose:
Provide usable visual materials for stories.
Core asset types may include:
• formal headshots
• relaxed headshots
• environmental images
• team images
• product or service images
• clean-background cutout-capable shots
Rules:
• images should be available in formats suitable for web and print
• imagery should be easy to download and clearly usable
• weak or low-quality visuals reduce editorial usability
Category 5 — Anchor Content Assets
Purpose:
Provide evergreen pages that can be linked repeatedly from outreach and media activity.
Examples may include:
• research reports
• data pages
• reference resources
• category explainers
• expert commentary pages
• campaign support pages
• insight hubs
Rules:
• anchor content should be durable
• anchor assets should remain relevant beyond one launch
• anchor content must support repeated outreach use
Category 6 — Press Material Bundles
Purpose:
Provide structured outreach-ready support packs for media use.
A press material bundle may include:
• key story summary
• downloadable images
• spokesperson details
• company summary
• relevant links
• supporting facts
• contact pathway
Rules:
• bundles should reduce journalist effort
• attachments should not create avoidable friction
• bundles should be hosted or delivered in easy-access formats where possible
Asset Readiness Rule
Before major outreach or editorial promotion, Content Brain should assess whether the following are ready:
• link destination quality
• spokesperson bio quality
• image quality
• about page sufficiency
• support page relevance
• downloadable material availability
If asset readiness is weak, outreach efficiency declines.
Anchor Content Principle
Anchor content is content that can be linked repeatedly over time.
Anchor content should be:
• relevant
• durable
• non-fragile
• support-oriented
• easy to cite
• easy to understand
Anchor content improves the long-term value of outreach systems.
Relationship to Other MWMS Systems
This framework supports:
• Research Brain outreach and publication targeting
• HeadOffice integrated coordination
• future authority-building systems
• future media-response systems
• future digital PR processes
This framework provides the on-site support layer for off-site activity.
Drift Protection
The system must prevent:
• outreach without destination readiness
• weak biography infrastructure
• weak or missing headshot assets
• about pages that do not support legitimacy
• link building toward low-value destinations
• support assets being built only after outreach failure
Support assets must be prepared before scale outreach.
Architectural Intent
The Content Brain Press Support Asset Framework exists to ensure MWMS has the asset infrastructure required to support trusted editorial growth.
Its role is to make outreach more effective by ensuring the website provides:
• usable context
• usable media assets
• usable expert references
• reusable anchor content
This framework turns content infrastructure into authority support infrastructure.
Change Log
Version: v1.0
Date: 2026-04-19
Author: HeadOffice
Change:
Initial creation of framework defining press support assets, biography structures, about assets, headshots, anchor content, and support bundles for MWMS outreach readiness.
END Content Brain Press Support Asset Framework v1.0
PAGE 3
HeadOffice Integrated Media and Search Coordination Framework
Document Type: Framework
Status: Structural
Authority: HeadOffice
Applies To: HeadOffice, Research Brain, Content Brain, future authority systems, future integrated media systems
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-19
Purpose
The HeadOffice Integrated Media and Search Coordination Framework defines how MWMS coordinates teams, workflows, and reporting across editorial outreach, content support, and authority growth activity.
The framework exists to prevent siloed execution across media, content, and search-facing systems.
The framework supports:
• lower duplication
• lower coordination friction
• stronger swim lane clarity
• safer authority growth
• better reporting visibility
• reduced team conflict
• integrated planning discipline
This framework ensures teams work together without collapsing into role confusion.
Scope
This framework applies to:
• media and search coordination
• integrated editorial planning
• cross-team outreach support
• swim lane definition
• shared reporting structures
• support asset sequencing
• launch coordination
• authority-building workflow management
This framework governs coordination logic.
It does not govern:
• final media strategy by itself
• final content production by itself
• technical SEO implementation by itself
• organisational HR structures
• budget sign-off by itself
Those remain with the relevant operational owners.
Core Principle
Integrated strategy fails when teams collide without coordination.
The main causes of failure are often human rather than technical.
Typical causes include:
• jargon conflict
• territorial behaviour
• metric conflict
• duplicate work
• unclear ownership
• weak handoff timing
• support assets not ready when needed
Coordination must be designed deliberately.
Swim Lane Rule
Each integrated initiative must define clear swim lanes.
Possible swim lane questions include:
• who owns initial story development
• who owns support asset readiness
• who owns first-tier outreach
• who owns follow-on outreach
• who owns reporting consolidation
• who owns link target selection
• who owns update timing
Swim lanes reduce duplication and protect working relationships.
Ask Not Demand Rule
Integration should be introduced through cooperation rather than forced takeover.
Rules:
• ask questions before changing another team’s process
• seek compatibility before asserting control
• use explanation before criticism
• prioritise long-term trust over short-term dominance
Integrated systems fail when one team feels invaded.
Shared Language Rule
Teams must reduce jargon isolation.
Rules:
• unfamiliar terms should be explained
• cross-team meetings should encourage clarification
• repeated key concepts should be standardised
• shared language improves adoption speed
Lack of shared language creates avoidable friction.
Staged Integration Principle
Integration should mature in stages.
Typical progression:
Stage 1 — awareness
teams understand each other’s work
Stage 2 — visibility
teams share calendars, outputs, and priorities
Stage 3 — support
teams create assets that help each other
Stage 4 — sequencing
teams coordinate timing and handoffs
Stage 5 — true integration
teams jointly build higher-value systems
Slow stable integration is preferable to forced integration.
Handoff Timing Rule
Integrated initiatives should follow a clear sequence.
Typical sequence may include:
- build support assets
- identify priority publications
- pre-brief or soft-sell key opportunities
- launch with clear timing
- expand to wider targets
- continue follow-on support
- report results across all affected teams
Poor timing reduces total value.
Reporting Consolidation Rule
Integrated initiatives should not be reported through isolated victory claims.
Rules:
• create shared reporting where possible
• separate warm leads, confirmed leads, and live outcomes
• show both direct and indirect value
• include authority, coverage, support asset, and signal impacts where relevant
Consolidated reporting improves trust between teams.
Conflict Prevention Rule
The system must protect against:
• duplicate outreach to the same source
• argument over who owns a story after it succeeds
• content built without outreach utility
• outreach run without support assets
• reporting that erases another team’s contribution
Inte