diff --git a/docs/plans/2026-11-09_prd-1-20-draft.md b/docs/plans/2026-11-09_prd-1-20-draft.md
index 826d9aa59..cf0d75a6e 100644
--- a/docs/plans/2026-11-09_prd-1-20-draft.md
+++ b/docs/plans/2026-11-09_prd-1-20-draft.md
@@ -1,4 +1,4 @@
-# PRD version 1.20, draft 1: unified workspace
+# PRD version 1.20, draft 2: unified workspace
 
 - Status: draft, not approved. Jason approves the exact text before it
   enters `docs/prd/mosaic-stack.md` as version 1.20.
@@ -100,9 +100,13 @@ need no sign-in.
 - **REQ-AGENT-2.** The user can see and change the configuration of agents,
   organizations, projects and sessions, and can override any setting at any
   time, through the write path (REQ-ROLE-3).
-- **REQ-AGENT-3.** The chief of staff hires and fires agents at the
-  organization and project levels under REQ-COS-3. Root-level agents change
-  only by the user.
+- **REQ-AGENT-3.** The chief of staff hires and fires agents to meet the
+  user's needs. At the organization and project levels it acts under
+  REQ-COS-3. At the root level its hire or fire changes the user's root
+  configuration, which every organization of that user sees, so it reaches
+  outside the chief's own organization. A root-level hire or fire is a
+  decision the user approves in the inbox (REQ-DEC-2) before it takes
+  effect. The user can also change root-level agents directly.
 
 ### System types
 
@@ -131,6 +135,10 @@ need no sign-in.
 
 ## Open questions for the approval
 
-1. The final name for the Mosaic Montage module.
-2. REQ-AGENT-3 keeps root-level agents user-only. Should the chief of staff
-   also be able to propose root-level hires for the user to approve?
+1. The final name for the Mosaic Montage module. A council of three agents
+   is producing three suggestions for Jason to choose from.
+2. Answered 2026-11-09: "yes, the COS should be able to hire and fire
+   agents to fulfill the user's needs". REQ-AGENT-3 now lets the chief hire
+   and fire at every level. Draft 2 keeps one approval step at the root
+   level because a root change reaches every organization; Jason can drop
+   that step when he approves the text.
diff --git a/docs/plans/2026-11-09_unified-workspace-owner-direction.md b/docs/plans/2026-11-09_unified-workspace-owner-direction.md
index a7833e506..7ee0dea8e 100644
--- a/docs/plans/2026-11-09_unified-workspace-owner-direction.md
+++ b/docs/plans/2026-11-09_unified-workspace-owner-direction.md
@@ -236,3 +236,18 @@ the start.
 - The final name for the Mosaic Montage module.
 - Which "sign-in (model proxy)" step Jason hit. F3 inventories every manual
   step on the dev instance and reports it.
+
+## Addendum, 2026-11-09 18:13 UTC
+
+Jason's answers to the two open questions in PRD 1.20 draft 1, verbatim:
+
+> 1. I would like you to use a council of agents to decide on 3 name
+>    suggestions for this
+> 2. yes, the COS should be able to hire and fire agents to fulfill the
+>    user's needs
+
+Effect: the chief of staff hires and fires agents at the root,
+organization and project levels (PRD 1.20 draft 2, REQ-AGENT-3). A council
+of three agents proposes three names for the Mosaic Montage module, and
+Jason picks one.
+