mosaicstack/stack
1
0
Fork 1
Code Issues 110 Pull Requests 2 Actions Packages Projects Releases 15 Wiki Activity

fix(framework): key §5 lookup on rendered bullets, not the token (mos-dt round-2)
ci/woodpecker/pr/ci Pipeline failed
Details

Browse Source 
§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 <[email protected]>
This commit is contained in:
jarvis
2026-07-30 15:41:26 -05:00
co-authored by Claude Fable 5
parent caf40afc01
commit 89e26ff7c2
1 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/mosaic/framework/guides/WRITING-STYLE.md
+8 -7
View File
@@ -15,7 +15,7 @@ certification.
|---|---| |---|---|
| Technical documentation (READMEs, runbooks, PRDs, procedures, ADRs, guides, acceptance criteria, design docs) | **MOS-STE** (this guide) | | 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) | | 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) | | 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. | | 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 section. This guide adds the OUTPUT meaning of each value; do not invent new
values. 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 | | `USER.md` leading bullet | Style | User-facing output |
|---|---| |---|---|---|
| `direct` (default) | MOS-STE structure — short, active, defined terms, tables for overview. | | "Direct and concise" | `direct` (default) | MOS-STE structure — short, active, defined terms, tables for overview. |
| `friendly` | Warmer register. Full sentences, explain reasoning, fewer tables. | | "Warm and conversational" | `friendly` | Warmer register. Full sentences, explain reasoning, fewer tables. |
| `formal` | Professional and structured. Thorough, with explicit recommendations. | | "Professional and structured" | `formal` | Professional and structured. Thorough, with explicit recommendations. |
This setting governs **user-facing comms only**. It does not change the This setting governs **user-facing comms only**. It does not change the
documentation standard (§3), which is always MOS-STE regardless of the value. documentation standard (§3), which is always MOS-STE regardless of the value.