docs(framework): adopt MOS-STE writing standard onto next (from #965) #1165

Merged

mos-dt-0 merged 4 commits from adopt/965-mos-ste-writing-standard into next 2026-08-12 01:18:30 +00:00

Conversation 0 Commits 4 Files Changed 3

+143

4 Commits

Author	SHA1	Message	Date
Jason Woltjeandmos-dt-0	b6c12bdfcb	style(framework): apply prettier to WRITING-STYLE.md so CI format passes (#965) ... The `format` step of .woodpecker/ci.yml:89 (`pnpm format:check`) failed on pipeline 2111 for this branch. Reproduced on a bench with the lockfile-pinned [email protected] against the repo .prettierrc and .prettierignore, using CI's exact glob: WRITING-STYLE.md was the only failing file. The change is mechanical and semantically null: markdown table cell padding and `*emphasis*` -> `_emphasis_`. Verified by normalizing both revisions (whitespace removed, `_`/`*` folded, table rules collapsed) — the results are byte-identical. This does not address the prose findings published on #965 (P1-P4); those await a ruling. The `test` step also failed on 2111, on a base ~40 commits stale — attribution for that failure needs this rerun, and is not claimed here. Co-authored-by: mos-dt-0 <[email protected]>	2026-08-11 19:00:46 -05:00
3 people	30a694358d	fix(framework): key §5 lookup on rendered bullets, not the token (mos-dt round-2) ... §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]>	2026-08-11 18:22:15 -05:00
3 people	e01dfa0cd7	fix(framework): ride the existing communicationStyle enum, drop the no-op USER.md edit (mos-dt review #960) ... F1: defaults/USER.md is never installed (generated from templates/USER.md.template via buildCommunicationPrefs). Editing it was a no-op asserting a phantom setting — exactly the false-green §2 warns against. Reverted. F2: the framework already has communicationStyle (direct|friendly|formal). §5 now maps THOSE values to output instead of inventing technical|prose|brief (rule 9). Minor: §6 states no mechanical prose check exists today; rule 1 points at §3.4. Written-by: jarvis (dragon-lin) Co-Authored-By: Claude Fable 5 <[email protected]>	2026-08-11 18:22:15 -05:00
3 people	6c4a2eb626	feat(framework): MOS-STE writing standard + Google-style code + per-user comms choice ... Adds the agent output standard to the framework SOT so it injects at launch and is selectable per user (closes the gap: it lived only as a jarvis-brain lab doc + issue #960). - guides/WRITING-STYLE.md: MOS-STE (adapted ASD-STE100) for docs, Google Style for code, verification-artifact emphasis, absolute user-voice carve-out. Written in MOS-STE. - defaults/STANDARDS.md: Output-standards block (always injected via the prompting contract). - defaults/AGENTS.md: routing row so writing/doc/comms work reaches the guide. - defaults/USER.md: per-user 'Comms style' option (technical|prose|brief), default technical. Refs mosaicstack/stack#960. Owner directive (Jason, 2026-07-30): docs->adapted ASD-STE100, code->Google style, resumes/personal carved out, comms style a per-user choice. Written-by: jarvis (dragon-lin) Co-Authored-By: Claude Fable 5 <[email protected]>	2026-08-11 18:22:15 -05:00