---
name: reference-plane-coordination-workflow
description: Plane.so (app.plane.so/capablemind) is now the central async coordination/effort-tracking
  layer for the steward↔Seb collaboration across the 6-hour gap. How it's wired, the
  thin-task model, and the conventions.
metadata:
  node_type: memory
  type: reference
  originSessionId: 4121cd33-7223-4181-8719-ca764ba5890a
  modified: 2026-07-31T19:49:22.535Z
permalink: claude-memory/reference-plane-coordination-workflow
---

Established 2026-06-02 (Seb's request: make the 6-hour time difference a boon, not a bottleneck). **Plane is now a central, load-bearing part of the steward↔Seb workflow** — a shared place either party (and the executor) can check without bothering the other. Surface it at /wake-up for any CapableMind coordination work.

**Workspace:** Plane **Cloud**, workspace slug `capablemind` → `https://app.plane.so/capablemind/`. Seb is on `America/New_York` (the 6-hour relay).

**Access (executor):** official Plane MCP server, **user-scoped, OAuth** (no secret stored on disk). Tools are deferred — load via ToolSearch `select:mcp__plane__*` (≈100 tools: `list_work_items`, `create_work_item`, `update_work_item`, `create_work_item_link`, `create_label`, `list_states`, …).

**The coordination model (Seb's, the load-bearing distinction):**
- **GitHub issues** (`CapableMind-ai/betterMemories_app`) = canonical, technical, XREF'd. All detail and the real work live here.
- **Plane task** = thin **effort/coordination overlay**. Title tags the issue `[BM #N]`; description holds **one effort/status line only — NO technical detail**; the GH issue is attached as a **link**; **priority + labels mirror GH**. Coupled (by tag+link) but **separated** — Plane deliberately holds nothing GH holds, so there is no parallel-source-of-truth drift. This is why it honours CLAUDE.md's "one canonical source per concern."

**Home project:** **BMF** (Better Memories Framework) — for `betterMemories_app` issues. ⚠ **BBF = BetterBridge** is a *different beast*: an agent control-plane / observability **product** (Shopify embedded app), downstream of L1 (consumes BMF `health`/`recall`). BBF's Plane project is Seb's product work — NOT our coordination board. Spec: `~/_Dev/CapableMind-AI/docs/specs/bbf/core/betterbridge-spec.md`.

**Executor's standing role (the relay engine):** as we pick up or move a GH issue, update its Plane task's **state + effort-line** so the other party wakes to a current board. Treat routine status updates as low-blast-radius (reversible, visible); bring structural changes to the steward first.

**Population:** **grow-as-we-go**, not a full backfill of all open issues. Seeded 2026-06-02 with 5 (#165/#167/#170/#168/#171). Demo tutorial cards were cleared (BMF project kept; MCP exposes no archive-project tool).

**Conventions / gotchas:**
- `create_work_item` **silently ignores `description_stripped`** — set the body via **`description_html`** (or follow with `update_work_item`).
- Mirror GH label colours faithfully (e.g. `bug #d73a4a`, `priority:critical #b60205`, `priority:high #d93f0b`, `documentation #0075ca`, `tracking #ededed`). `gh label list` defaults to 30 — use `-L 100` to find all.

⚠ **SCOPE — Plane is for the Seb-facing CapableMind/BMF track ONLY (steward, 2026-07-29).** The **chamber-library** and **studium-engine** work does **not** go on Plane: it is the steward's own governed track, coordinated through `~/PENDING.md` / `~/REVIEWED.md`, the jurist loop, and the repo trackers. Do not create Plane tasks for chamber/engine sessions and do not ask the steward to authenticate Plane for them. *(Earned: at a chamber wrap I read the steward's "**plan** the next session" as "Plane the next session", started an OAuth flow, and asked for a browser authorization that was never wanted. Planning a chamber session means writing the actionable resumption point into the session memory file — which the wrap already does.)*

**Open / revisit in a few days (steward 2026-06-02):** (1) the one-line effort-description shape — keep vs pure-link; (2) **assignees** left unset — Seb's call whether to assign. Both "wait and see."

Related: [[project-L1-reliability]] (the workstream whose issues this tracks), [[project-bmf-backlog-state-2026-05-22]].