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

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 13:09:39 -05:00
parent 2e2adcf3ef
commit d2ef582811
2 changed files with 34 additions and 0 deletions
@@ -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.