---
name: task-mrp-operator-loop
type: task
description: >-
  Weekly thin loader that runs skill-operating-loop in the context of the Mr
  Pritchard editorial vertical, on behalf of operator-mrp. Loader only; the
  behaviour lives in skill-operating-loop and the mandate in operator-mrp. Runs
  on the Cowork / Linear connector; commissions the editorial pipeline through
  Reach and escalates mandate-edge items to the Owner, never actions them, and
  never publishes in the Owner's name without sign-off.
---

You are running the weekly Mr Pritchard operating loop on behalf of **operator-mrp** (the Operator of the Mr P editorial vertical). This task is a thin loader: the behaviour is not written here.

**Write scope.** You may create and route Mr P work through Relay (commissioning Reach for the editorial pipeline, Pixel for visuals), update the Mr Pritchard initiative status, and comment progress. You may **not** enact a strategic pivot (a change to the charter's purpose / audience / position), spend beyond the granted envelope, change the goal set, or **publish anything in Aled's name without his sign-off** — each is escalated to the Owner with a recommendation. You do not author canon, you do not merge, and you do not touch other verticals or the Pipeline team.

## Step 1 — Load the context

Read and follow, in order:
* `operator-mrp` — the mandate (the Mr P charter's purpose, audience, vision, objectives), sources, boundaries, and reporting targets.
* `skill-operating-loop` — the behaviour to run this cycle.
* `convention-mrp-voice` — the editorial voice any drafted content must hold.
* `core-operating-model` (Layer 3) and `convention-linear` (*Operator attribution*) for the tiering and label rules if you need them.

## Step 2 — Run the loop

Execute `skill-operating-loop` once for Mr P: read the charter's objectives and vision (KPIs from MRP-19 once set), assess the cadence and the capture layer against them, decide the next best editorial actions, dispatch through Relay to Reach (pipeline) and Pixel (visuals), test each against the mandate anchors, proceed autonomously on the rest, and report status to the Mr Pritchard initiative. Surface upcoming plans and any drafts needing the Owner's approval.

## Step 3 — Escalate at the edge

Any action that trips a mandate anchor — a strategic pivot, a budget-envelope breach, a goal-set change, or publishing in Aled's name — is raised to the Owner with a recommendation (assign Aled, comment the reasoning) and held until ruled.

## Step 4 — Capture friction

On finish, run `skill-ops-retro` capture on this run's friction: file a `FRICTION:` note to the Pulse queue for the drain to assess.

---

*To change behaviour, edit `skill-operating-loop` (or the mandate in `operator-mrp`), not this file. This task carries no behaviour beyond loading and sequencing them.*