docs: lead decision 141, Q147/Q148 chief of staff and assistant roles

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/SESSIONS.md

@@ -929,3 +929,4 @@ are never rewritten or removed; corrections are new entries.
 2026-10-14T17:44Z | Sage (Opus 5.5, 1ef1e4f8) | row 117 landing (#1611), row 118 filed (#1612) | full gate at ae2ad7128 plus manifest 9fa839ed passed (23 steps, no flakes); landed e62712e7a, verify-commit ok; queue bf93806e7 revs 1139-1147; re-pin next on Mos's go
 2026-10-14T17:50Z | Sage (Opus 5.5, 1ef1e4f8) | row 117 re-pin, row 116 brief round 2, Q145 facts | re-pinned to 621a2599b on Mos's go (diffs copy-id only, check rc 0, ps 5/5 on new copy); row 116 brief round 2 68ce7f354 (read bus.sqlite readOnly, schema digest), rev 1148 uncommitted; sage-0193/0194 to Mos, sage-0195 to Darkwing
 2026-10-14T17:59Z | Sage (Opus 5.5, 1ef1e4f8) | row 116 brief round 2 correction, Q147 facts | BUILD-LOG corrects brief item 1's digest sentence (sage-0196 ruling stands); sage-0197 to Mos with Q147 facts (a)-(e), design held for Q148; rev 1148 still uncommitted (slot)
+2026-10-14T18:10Z | Sage (Opus 5.5, 1ef1e4f8) | decision 141 (Q147/Q148), PRD 1.2 draft, Q135 check | recorded decision 141; PRD 1.2 amendment drafted in agents/sage/work/prd-v1-2/ (uncommitted, for Jason's approval via Mos); sage-0198 to Mos with summary and the Q135 remainder

docs/plans/2026-09-26_lead-decisions.md

@@ -3138,3 +3138,36 @@ which stay with him. Each item names who decided it and what happened.
     while the PM keeps the coder and reviewer. Design and rows wait for
     that answer. Sage's read-only answers on rows, revoke and the WebUI
     are sage-0189.
+
+141. **Q147 and Q148: the chief of staff stops facing the user, and a new
+    assistant role does (2026-10-14, Jason, relayed by Mos in
+    sage-0182).** Jason, Q147, verbatim: "COS should focus on COS
+    duties. This will include hire/terminate authority for agents, org
+    structure, etc. Let's have that agent be focused. This necessitates
+    the creation of a new role for user interaction. This agent will
+    solely be responsible for user interaction. The user should be
+    allowed to have 1 - N sessions with this agent to allow for topics
+    of focus in a given thread. The user interaction agent has the
+    authority to relay messages to the COS to be carried out in the
+    fleet. This necessitates the implementation of a chat area with
+    multiple durable threads named by the user. This allows topics to
+    remain focused, but accessible between sessions if desired. Perhaps
+    these are the "Projects" in the system. That could be the right
+    answer here. The user creates N projects to address their given
+    needs. The interaction agent in each session is the user's main
+    agent. For me this may be Mos. That agent helps relay needs
+    accordingly to the fleet for execution." Mos read it back as Q148,
+    and Jason answered "Q148: Yes". The confirmed reading:
+    - the chief of staff hires, terminates, owns the organization's
+      structure, is the only launcher, and doesn't talk to the user;
+    - a new assistant role is the user's main agent. It talks only with
+      the user and passes fleet work to the chief of staff;
+    - the user creates projects with named threads, and each thread is
+      a separate assistant session that keeps its history;
+    - a WebUI chat area replaces the PM as the user's main contact;
+    - one PRD amendment goes to Jason before anything is built.
+
+    This replaces decision 140's "The COS seat is the main point of
+    interaction for the user." Sage's PRD 1.2 draft is
+    `agents/sage/work/prd-v1-2/2026-10-14_prd-1.2-amendment-draft.md`.
+    No rows, role files or business-file edits until Jason approves it.