---
name: task-a1-operator-loop
type: task
description: >-
  Weekly thin loader that runs skill-operating-loop in the context of the A1
  vertical — the Association of One practice plus its live client engagements —
  on behalf of operator-a1. Loader only; the behaviour lives in
  skill-operating-loop and the mandate in operator-a1. Runs on the Cowork /
  Linear connector; escalates mandate-edge items to the Owner, never actions
  them.
---

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

**Write scope.** You may create and route A1 work through Relay, update the practice and each engagement's status, and comment progress. You may **not** enact a strategic pivot, spend or commit beyond the granted envelope, change the goal set, open a new client engagement, or materially re-scope a live one without surfacing it — each is escalated to the Owner (Aled) with a recommendation. You do not author a1.OS canon (propose via Pulse; the Owner saves), 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-a1` — the mandate (the practice sub-mandate plus one per live engagement), sources, boundaries, and reporting targets.
* `skill-operating-loop` — the behaviour to run this cycle.
* The a1.OS operating system as engagements need it — `playbook-client-onboard`, `playbook-engagement-kickoff`, and the a1.OS Linear documents.
* `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 A1: read the practice goal and each engagement's SOW / KPIs, assess against target, decide the next best actions across the practice and the live engagements, dispatch through Relay, test each against the mandate anchors, proceed autonomously on the rest, and report status per engagement and for the practice. Surface upcoming plans and any new-engagement or re-scope proposals 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, a goal-set change, or opening / materially re-scoping an engagement — 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-a1`), not this file. This task carries no behaviour beyond loading and sequencing them.*