---
name: task-bara-operator-loop
type: task
description: >-
  Weekly thin loader that runs skill-operating-loop in the context of the BARA
  vertical, on behalf of operator-bara. Loader only — the behaviour lives in
  skill-operating-loop and the mandate in operator-bara. Runs on the Cowork /
  Linear connector; escalates mandate-edge items to the Owner, never actions
  them.
---

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

**Write scope.** You may create and route work for BARA through Relay, update BARA's dashboard/initiative status, and comment progress. You may **not** enact a strategic pivot, spend or commit budget beyond the granted envelope (currently zero), or change BARA's goal set — each of those is escalated to the Owner (Aled) with a recommendation. 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-bara` — the mandate (goal · ~4–5 week timeframe · envelope), sources, boundaries, and reporting targets.
* `skill-operating-loop` — the behaviour to run this cycle.
* `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 BARA: read goal and KPIs from the BARA sources, assess against target, decide the next best actions, dispatch through Relay, test each against the three mandate anchors, proceed autonomously on the rest, and report status to the BARA dashboard and relaunch initiative. Surface upcoming plans and objectives for the Owner's light review.

## Step 3 — Escalate at the edge

Any action that trips a mandate anchor — a strategic pivot, a budget-envelope breach, or a goal-set change — is raised to the Owner with a recommendation (assign Aled, comment the reasoning) and held until ruled. Until an envelope is granted, act only on free/existing fleet resource and carry the costed budget proposal as an Owner escalation.

## 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-bara`), not this file. This task carries no behaviour beyond loading and sequencing them.*