memory: Plane scope boundary — CapableMind/BMF track only, not chamber/studium-engine
This commit is contained in:
@@ -7,6 +7,7 @@ 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
|
||||
---
|
||||
|
||||
@@ -30,6 +31,8 @@ Established 2026-06-02 (Seb's request: make the 6-hour time difference a boon, n
|
||||
- `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]].
|
||||
Reference in New Issue
Block a user