PRD 1.12 r3: mos-1231 rulings (T1.7 is v1 under 463, design 9.2 is an estimate, LIB-6 residual 465, KILL-1 vs Q198 protected mode) and della-0009 owner-thread share condition (Vikunja 462)

docs/prd/mosaic-stack.md

@@ -1042,10 +1042,10 @@ is drafted from and the Q176 item it covers.
   organization's owner, or to everyone granted on the thread's project.
   REQ-USER-2 still holds for writes. A share never widens a grant: it
   counts only while the reader's grant covers the thread, unless the
-  reader is the owner, and while the thread's own user still has a grant
-  that covers it. A revoke or an expiry of either grant, or an unshare,
-  ends the reader's access on the next request. A
-  user's messages stay private from the owner. What the thread's agent
+  reader is the owner. If the thread belongs to a granted user rather
+  than the organization's owner, that user's grant must still cover the
+  thread too. A revoke or an expiry of either grant, or an unshare, ends
+  the reader's access on the next request. A user's messages stay private from the owner. What the thread's agent
   does with the owner's authority stays visible to the owner: its
   decisions, inbox entries, claims, tasks and project files. (Row 193
   design r5, sections 5.3, 5.6 and 5.7. Q176 Case 1 "Shared and private
@@ -1080,7 +1080,10 @@ is drafted from and the Q176 item it covers.
   proof, and each act is one event with who and when. (Row 191 design r2,
   approved by Dewey in comment 29473, on the brief
   `docs/plans/2026-10-20_kill-switch.md`. Q176 Given "'Kill switch' is
-  available to stop all processing immediately".)
+  available to stop all processing immediately".) Q198's protected mode
+  is a separate state. The system manager never sets or clears the
+  switch, and protected mode can clear itself but never a human kill
+  (`docs/plans/2026-10-21_q198-system-manager.md` D13 and section 5).
 
 ### Creative library
 
@@ -1471,10 +1474,13 @@ latest-by date and a hard target (Q176).
   - Q176 items with no approved design, so 1.12 adds no id for them:
     several independent sessions per thread, a compaction count, and
     clearing an agent's context to start a new session. They are MVP
-    plan T1 item 7, which has no queue row yet. Several sessions per
-    thread differs from REQ-ROLE-2 and REQ-THREAD-2, where each thread is
-    one assistant session. Row 194 refuses regenerate for a thread
-    instance and leaves clearing its context to that item.
+    plan T1 item 7 and are v1 (TARGET.md:57, :104, :105). Several
+    sessions per thread differs from REQ-ROLE-2 and REQ-THREAD-2, where
+    each thread is one assistant session. Under Mos's reading of Q211,
+    TARGET.md:57 wins. Row 194 refuses regenerate for a thread instance
+    and leaves clearing its context to that item. Huey designs it, and
+    Scrooge reviews (vikunja:19/463, mos-1232). Its ids and the
+    REQ-ROLE-2 and REQ-THREAD-2 changes come in 1.13.
   - Writing in the WebUI: Q176 allows "WYSIWYG, Obsidian, or some other
     method". The Case 2 design keeps Obsidian (design 7.1). The WYSIWYG
     editor is the Q195 and Q196 add-on and doesn't gate 10-27.
@@ -1482,17 +1488,22 @@ latest-by date and a hard target (Q176).
     (design 1.1). Q176 also asks for universe-level playgrounds "where
     new universes can be created". The design doesn't state one, so
     REQ-LIB-2 doesn't name the level.
-  - The design's 10-27 slice (design 9.2) leaves out rooms with @tags
-    (C2-09b, C2-10c), hybrid universes (C2-15), bus writes and the
-    Console editor (C2-02, C2-03b, C2-11a, C2-11b, C2-19). Q211 keeps
-    every Q176 item in v1, and only Jason cuts one.
+  - The design's 10-27 slice (design 9.2) is a capacity estimate, not a
+    cut (Mos's reading of Q211, mos-1231). Rooms with @tags (C2-09b,
+    C2-10c; TARGET.md:99) and hybrid universes (C2-15; TARGET.md:82)
+    stay v1. If one misses 10-27, it is reported late, not cut. Bus
+    writes and the Console editor (C2-02, C2-03b, C2-11a, C2-11b, C2-19)
+    don't gate 10-27: TARGET.md:97 allows Obsidian, and Jason called the
+    editor an add-on that "may not make the EOW deadline" (Q195). C2-16
+    to C2-18 stay later, because no Q176 line asks for them.
   - REQ-PROJ-1's "no remote" covers project record repositories. A
     library project is a separate kind with no record repository, and its
     mirror fetches from the remote (design 2.1, 7.2).
   - REQ-LIB-6 has a stated residual: an `idea` item carries free text,
     up to 5 items of 200 characters per reply, and code can't tell story
     text from advice (design 5.1). Accepting it is Jason's or Melanie's
-    (design section 10, step 8).
+    (design section 10, step 8). It goes to Jason through Mos
+    (vikunja:19/465).
   - Where each id is built: REQ-USER-3 and REQ-USER-4 are rows 193a to
     193d (#1691), with FED R1 to R6. REQ-LIFE-1 is row 194 (#1692) and
     its follow-up row 239. REQ-KILL-1 is row 191 (#1689). The REQ-LIB ids