OPERATIONAL PLAYBOOKS & TEMPLATES

Copy-ready blueprints for your brand system.

Every lesson in MUMRO Academy translates into a concrete operational artifact. Copy these specifications directly into your team repository—or run them natively inside a MUMRO workspace.

PLAYBOOK 01TRACK 01: Living Brand Systems & Content StrategyYAML Specification

Enforceable Brand Voice & Claim Boundaries Specification

Replace vague adjectives with structural syntax rules, domain vocabulary, and hard claim boundaries.

When to use

When onboarding a new brand workspace, configuring AI generators, or aligning editors and reply policies.

Connected in MUMRO

In MUMRO, this profile is stored once per workspace and automatically guides articles, social posts, carousels, comment reply suggestions, and the website assistant.

YAML Specification

# MUMRO Academy — Brand Voice & Claim Boundaries Blueprint
workspace_id: "your-brand-slug"
strategy_version: "v2.0"

cadence_rules:
  opening_hook: "Open with a concrete observation, metric, or physical constraint. No rhetorical questions."
  sentence_rhythm: "Alternate short declarative sentences (4-8 words) with detailed technical explanations."
  formatting: "Use 3 distinct paragraphs per social post: 1) Hook/Voice, 2) Source Fact, 3) Goal/CTA."

domain_lexicon:
  preferred_terms:
    - "verified source"
    - "cohort retention"
    - "confirm gate"
    - "handlebar clearance"
  banned_cliches:
    - "game-changer"
    - "unlock your potential"
    - "in today's fast-paced world"
    - "revolutionary"

hard_claim_boundaries:
  - "Never invent customer testimonials, case-study percentages, or unverified ROI claims."
  - "State exact product tolerances and operating conditions."
  - "Separate raw external research facts from brand opinion."

reply_policy:
  inbox_and_assistant: "Answer product and technical questions directly using ingested workspace knowledge; offer contact capture when custom scoping is required."

Read full lesson

PLAYBOOK 02TRACK 02: Multi-Format Content Engineering & PublishingMarkdown / YAML Matrix

One-Story Multi-Channel Decomposition Matrix

Turn one researched article into a 5-slide carousel and native posts for Instagram, Facebook, X, and LinkedIn.

When to use

At the start of every weekly campaign cycle before drafting individual social captions.

Connected in MUMRO

MUMRO’s Story Studio connects your researched article, 5-slide carousel, and 4 channel drafts in one view—with inspectable Sources, Brand Voice, and Content Goal layers.

Markdown / YAML Matrix

# MUMRO Academy — One Story, Four Channels Matrix
canonical_story:
  title: "Two Days. Four Litres: Packing Physics for Short Gravel Escapes"
  source_provenance: "Field Test Log #14 (1.8 kg handlebar load threshold)"
  strategy_pillar: "packing-physics"
  website_url: "https://example.com/journal/two-days-four-litres/"

carousel_5_slides:
  slide_01_hook: "Two days. Four litres. On your bars, instead of your back."
  slide_02_breakdown: "Rain shell, spare tube, multi-tool, mini pump, 48h nutrition."
  slide_03_mechanism: "Three-point head-tube strap eliminates steering sway and cable rub."
  slide_04_proof: "Stable handling on rough washboard descents."
  slide_05_action: "Save the checklist & read the full geometry guide on our site."

channel_adaptations:
  instagram:
    focus: "Visual carousel + tactile 3-paragraph saveable caption"
    link_strategy: "Link-in-bio hub or first comment"
  facebook:
    focus: "Community question + full story context"
    link_strategy: "Direct canonical article link"
  x:
    focus: "High-density thesis statement on load distribution"
    link_strategy: "Direct link in follow-up / post footer"
  linkedin:
    focus: "Constraint-led product engineering note"
    link_strategy: "Engineering takeaway + canonical article reference"

Read full lesson

PLAYBOOK 03TRACK 04: Agentic AI, Model Context Protocol (MCP) & GovernanceJSON-RPC / MCP Sequence

MCP Agent Campaign Loop & Two-Phase Confirmation Protocol

Step-by-step tool sequence for AI agents (Claude Code, Codex, Antigravity) operating on a MUMRO workspace.

When to use

When instructing an MCP-connected AI agent to audit performance, propose strategy updates, or prepare scheduled posts safely.

Connected in MUMRO

MUMRO’s MCP server enforces this exact sequence natively—requiring `prepare_*` and `confirm_*` tokens for all external mutations.

JSON-RPC / MCP Sequence

// MUMRO Academy — Safe Agentic Content Loop (MCP Runbook)

// 1. Ground in live workspace state & strategy (Read-Only)
1. call get_workspace_context({ "workspace": "fieldwork" })
2. call get_content_strategy({ "workspace": "fieldwork" })
3. call get_analytics_overview({ "workspace": "fieldwork", "windowDays": 30 })
4. call list_content_performance({ "workspace": "fieldwork", "windowDays": 30 })

// 2. Check upcoming queue slots & channel capabilities (Read-Only)
5. call get_publication_capabilities({ "workspace": "fieldwork" })
6. call preview_schedule({ "workspace": "fieldwork", "channel": "instagram" })

// 3. Create visible workspace draft (Safe Workspace Write — Never Publishes Live)
7. call create_publication_draft({
     "workspace": "fieldwork",
     "channel": "instagram",
     "caption": "Two days. Four litres...",
     "mediaIds": ["media_drift4l_carousel"]
   })

// 4. Two-Phase Mutation Gate (Prepare Preview -> Human/Policy Confirm)
8. call prepare_publication_action({
     "draftId": "draft_id_from_step_7",
     "action": "schedule",
     "scheduledAt": "2026-10-11T18:00:00Z"
   })
   // -> Pause and present preview (channel, exact text, slot) to human operator
9. call confirm_publication_action({
     "confirmationToken": "token_from_step_8"
   })

Read full lesson

PLAYBOOK 04TRACK 04: Agentic AI, Model Context Protocol (MCP) & GovernanceJSON Governance Policy

Multi-Workspace AI Autonomy & Governance Checklist

Standard operating policy for autonomy levels, quiet hours, credit budgets, and team roles across brands.

When to use

Before enabling delegated scheduling or onboarding agency team members and clients.

Connected in MUMRO

Configure all four guardrails directly in MUMRO’s Autonomy & Workspaces panels—with instant stop controls per brand.

JSON Governance Policy

{
  "governancePolicyVersion": "1.0",
  "workspaceIsolation": {
    "separateChannelsPerBrand": true,
    "separateBrandVoicePerBrand": true,
    "separateInboxAndAssistantPerBrand": true
  },
  "defaultAutonomySettings": {
    "initialMode": "draft_only",
    "productionMode": "schedule_with_confirmation",
    "delegatedMode": "autonomous_schedule",
    "quietHours": { "enabled": true, "start": "22:00", "end": "07:00" },
    "monthlyCreditBudget": 1000,
    "requireHumanMediaReview": true,
    "emergencyKillSwitchReady": true
  },
  "roleMatrix": {
    "owner": ["strategy_approve", "autonomy_config", "kill_switch", "team_manage"],
    "admin": ["strategy_approve", "publication_confirm", "channel_manage"],
    "member": ["draft_create", "research_curate", "reply_suggest"],
    "viewer": ["calendar_read", "analytics_read"]
  }
}

Read full lesson