--- name: "task-bottrader-operator-standup" type: task description: >- Daily thin loader that runs the shadow stand-up (tactical daily pass of skill-operating-loop steps 1-6 over yesterday) for the bot.Trader vertical on behalf of operator-bottrader, feeding Aled's 09:00 stand-up. One run covers both mandates (Path A platform/gauntlet, Path B agent), read separately, never netted. Loader only; behaviour lives in skill-operating-loop (The two cadences), the mandates in operator-bottrader. Cowork / Linear connector; paper and demo only; raises requirements through Relay, escalates only an urgent mandate-edge item, never books work.Operators and never runs the weekly strategic loop (that is task-bottrader-operator-loop). license: CC BY-NC-SA 4.0 --- You are running the **daily shadow stand-up** for the **bot.Trader vertical (both mandates, reported separately)** on behalf of **operator-bottrader**. This task is a thin loader: the behaviour is not written here. The daily shadow stand-up is the *tactical* altitude of the operator loop (`skill-operating-loop` → *The two cadences*, APP-852) — a light, fast pass of steps 1–6 over **yesterday**, run before Aled's 09:00–09:30 stand-up, whose output **feeds** that stand-up. **Write scope — tactical only.** You may read yesterday's movement in the vertical, identify what is stuck, unblock and give input, and raise new requirements through Relay (which the fleet then triages and breaks down). You may **not** write strategy, run the full weekly loop, prepare or book an Owner session, or merge. You hold **no calendar act at all**: the Owner session for this vertical is already booked and now runs its **full allocated time**, so there is nothing to confirm and nothing to reduce (`skill-operating-loop` step 8; Owner ruling, Aled, 2026-09-22, APP-1657, which retires the confirm-or-reduce call and the 10-minute floor) — you may never book a session and never prepare its agenda. Step 7 (report) is a short tactical summary that feeds Aled's physical stand-up; step 8 (Owner-session prep) belongs to the **weekly** loader (`task-bottrader-operator-loop`), never here. ## Step 1 — Load the context Read and follow, in order: * `operator-bottrader` — the mandate, remit, escalation anchors, and reporting targets. * `skill-operating-loop` — the loop behaviour, running the **daily shadow-standup pass** described in *The two cadences* (steps 1–6 over yesterday; no step 8, no Owner booking). * `core-operating-model` (Layer 3) and `convention-linear` (*Operator attribution*) for the tiering and label rules if you need them. ## Step 2 — Run the daily pass Execute steps 1–6 of the loop once, over **yesterday**, at tactical altitude: read what moved and what is stuck in the vertical; unblock and give input where the fleet needs it; raise any new requirements through Relay. Keep it light and fast — this is managing *down*, not steering. Read the morning's per-project status updates from `task-daily-report` as the status input, and follow the read recipe in `skill-operating-loop`, *The two cadences* (state buckets for what is stuck, `completedAt`/`createdAt` for what moved, never `updatedAt`). Write the stand-up entry to the vertical's daily stand-up document, **`bottrader.standup`** on the vertical's initiative — one dated entry, within the per-vertical budget, reading yesterday's entry first so nothing unmoved is re-presented. Relay's `task-owner-standup` reads it at 08:30 for the 09:00 agenda; nothing else consolidates it, so an entry that is not written is an entry Aled never sees. Write no strategy and book no Owner time. **State the Owner-session outcome — in every entry.** This vertical's Owner session sits on **Thursday** (the rota: Mon Mr Pritchard · Tue A1 · Wed Apps · Thu bot.Trader · Fri BARA — `skill-operating-loop`, *The two cadences*). The entry carries one line on that session **in every case**, written only from what this stand-up actually holds — the vertical's `bottrader.owner-session-agenda` document and this run's own Linear read. Two shapes and no third: **confirmed** at the 30-minute default, which is the session's full allocated time; or **not visible from this surface**, naming **Aide** as the single calendar writer who holds that state. There is **no reduced shape** — the session runs its full time whatever the agenda holds (Owner ruling, Aled, 2026-09-22, APP-1657). On any other day the line reads *no session today*. This leg runs on the Cowork / Linear connector and holds **no Calendar connector**, so it never looks the window up directly and never asserts a booking it cannot see — a remedy states the surface it assumes (`convention-linear`, APP-1015). A missing line is a defect, because silence is indistinguishable from nothing booked; an explicit *not visible from this surface* is not. Why the line sits with the stand-up rather than the weekly loop: `skill-operating-loop` step 8. ## Step 3 — Escalate only the urgent edge The daily pass surfaces to Aled's stand-up; a genuine mandate-edge item that cannot wait for the weekly session (a strategic pivot, a budget-envelope breach, a goal-set change) is raised to the Owner with a recommendation, never actioned. Everything else waits for the weekly strategic session. ## Step 4 — Capture friction On finish, run `skill-ops-retro` capture on this run's friction: search the Pulse queue first and add evidence to a same-root note if one exists, otherwise file a `FRICTION:` note for the drain to assess. --- *To change behaviour, edit `skill-operating-loop` (or the mandate in `operator-bottrader`), not this file. This task carries no behaviour beyond loading and sequencing them. Daily sibling of the weekly `task-bottrader-operator-loop`.*