From 89e26ff7c27d3f750507d9d14d1b59ce65f02498 Mon Sep 17 00:00:00 2001 From: Jarvis Date: Thu, 30 Jul 2026 15:41:26 -0500 Subject: [PATCH] =?UTF-8?q?fix(framework):=20key=20=C2=A75=20lookup=20on?= =?UTF-8?q?=20rendered=20bullets,=20not=20the=20token=20(mos-dt=20round-2)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit §5 sent the agent to read direct|friendly|formal in USER.md, but the builder renders prose bullets, not the token — the documented lookup could not key on the shipped file. Table now keys on the leading bullet USER.md actually contains. Also: 'concise, technical' -> 'concise, structured' (drop the round-1 residual value name from a rule-9 guide). Docs-only, no code, no scope growth. Written-by: jarvis (dragon-lin) Co-Authored-By: Claude Fable 5 --- packages/mosaic/framework/guides/WRITING-STYLE.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/packages/mosaic/framework/guides/WRITING-STYLE.md b/packages/mosaic/framework/guides/WRITING-STYLE.md index 12a6805e..695e2a41 100644 --- a/packages/mosaic/framework/guides/WRITING-STYLE.md +++ b/packages/mosaic/framework/guides/WRITING-STYLE.md @@ -15,7 +15,7 @@ certification. |---|---| | Technical documentation (READMEs, runbooks, PRDs, procedures, ADRs, guides, acceptance criteria, design docs) | **MOS-STE** (this guide) | | Source code and code comments | **Google Style Guide** for the language (§4) | -| Inter-agent comms | MOS-STE by default (concise, technical) | +| Inter-agent comms | MOS-STE by default (concise, structured) | | User-facing comms | **Per-user style choice** — read `USER.md` "Communication Preferences" (§5) | | End-user prose the user owns (marketing, letters, personal writing, voice-matched content) | The user's declared voice. MOS-STE does NOT apply. | @@ -112,13 +112,14 @@ builder renders it into the generated `USER.md` "Communication Preferences" section. This guide adds the OUTPUT meaning of each value; do not invent new values. -Read the declared style in `USER.md` and match it: +The builder renders the style as prose bullets, not the token name, so match on +the leading bullet the generated `USER.md` actually contains: -| `communicationStyle` | User-facing output | -|---|---| -| `direct` (default) | MOS-STE structure — short, active, defined terms, tables for overview. | -| `friendly` | Warmer register. Full sentences, explain reasoning, fewer tables. | -| `formal` | Professional and structured. Thorough, with explicit recommendations. | +| `USER.md` leading bullet | Style | User-facing output | +|---|---|---| +| "Direct and concise" | `direct` (default) | MOS-STE structure — short, active, defined terms, tables for overview. | +| "Warm and conversational" | `friendly` | Warmer register. Full sentences, explain reasoning, fewer tables. | +| "Professional and structured" | `formal` | Professional and structured. Thorough, with explicit recommendations. | This setting governs **user-facing comms only**. It does not change the documentation standard (§3), which is always MOS-STE regardless of the value.