docs(framework): MOS-STE writing standard — one term, one concept; verification-sentence discipline (#960 pilot) #965

Open
Mos wants to merge 3 commits from feat/mos-ste-writing-standard into main
Showing only changes of commit 89e26ff7c2 - Show all commits
@@ -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.