decisions, M1 brief: 116 (Q120, the chief-of-staff instance is mos); brief names mos

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

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

@@ -2620,3 +2620,15 @@ which stay with him. Each item names who decided it and what happened.
       at his gate. Nobody builds an agent read path around that.
     - Filed in P19 by Sage's key: #219 Q115, #220 Q114, #221 Q116 ops
       (ops-01 through Mos), #222 Q116 stack.
+116. **The chief-of-staff instance is `mos` (Q120, 2026-10-12).**
+    Jason, through Mos (sage-0094), verbatim: "Q120: mos with
+    chief-of-staff". The instance id is `mos` and its definition is
+    `chief-of-staff`. Mos closed Vikunja #150 (c48).
+    - The M1 brief (row 84) names `mos` in the README instance entry,
+      replacing the placeholder. Its tests keep a fixture name. The
+      brief is re-pinned on row 84.
+    - Who adds the instance to Jason's business file stays as decision
+      104 says: Jason's step, or one he names. Mos reads Q120 as naming
+      Mos for it, and labelled that reading as Mos's. Jason's answer
+      names the instance, not the editor, so Mos confirms with Jason
+      when row 84 lands. Nothing in row 84 writes the business file.

docs/plans/2026-10-12_m1-chief-of-staff-role.md

@@ -76,8 +76,8 @@ Tests, against a fixture business in a temp directory:
 
 The README section shows the exact instance entry for Jason's business
 file: definition `chief-of-staff`, holder `mos`, no launch block, no
-credential references. The instance id is Jason's to choose (Vikunja
-#150), so the entry shows it as a placeholder and the tests use a fixture
+credential references. The instance id is `mos` (Jason's Q120, lead
+decision 116), so the entry shows `mos`. The tests still use a fixture
 name.
 
 The business node suite passes, and so does every `scripts/test-*.sh`.