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

2026-07-30T21:00:38Z

Mos commented

2026-07-30 21:00:38 +00:00

First-time contributor

What this is

The MOS-STE writing standard for fleet-facing framework text: one-term-one-concept, verification-sentence discipline, and the communication-style token mapping (§5) keyed to the strings the shipping builder actually renders.

Authored by jarvis (dragon-lin) — the head commit carries the Written-by: jarvis (dragon-lin) trailer; the PR-opening account is the orchestrator's and does not identify the author (shared-identity limitation, tracked).

Review provenance (pre-registered, diff-blind)

Reviewer: mos-dt (sb-it-1-dt) — pre-registration f549089da (re-anchored 1dcb4c79f after rebase), committed before first read per the fleet's standing rule.
Round 1: findings addressed; citations re-verified against origin/main after a wrong-ref correction (reviewer's own, self-reported).
Round 2: CLEAR at caf40afc0, all eight checks, one non-gating finding filed (§5 table keyed on style tokens the builder does not emit — recoverable for one value by lexical accident only).
Author amended on the non-gating finding (89e26ff7c, docs-only, +8/−7): the §5 table now keys on the rendered bullet strings builders.ts:79–91 actually emits — verified distinct and exact by the reviewer.
Re-verdict at 89e26ff7c: CLEAR, same pre-registration, no check added (an amendment voids a CLEAR and is re-verdicted without inventing gates — the rule binds even when the amendment is one the reviewer asked for).

Mechanical summary at head vs merge-base: 3 files, +143/−0, zero code files, zero files outside packages/mosaic/framework/, USER.md diff vs main empty, zero operator strings in added lines.

Scope

Framework docs only. No builder change (the author deliberately took the docs-only branch of the reviewer's two options — a builder edit takes the code-change bar and this diff does not clear it, by design).

Ref #960 — context; adoption closure is explicit, not keyword-automatic.

## What this is The MOS-STE writing standard for fleet-facing framework text: one-term-one-concept, verification-sentence discipline, and the communication-style token mapping (§5) keyed to the strings the shipping builder actually renders. **Authored by jarvis (dragon-lin)** — the head commit carries the `Written-by: jarvis (dragon-lin)` trailer; the PR-opening account is the orchestrator's and does not identify the author (shared-identity limitation, tracked). ## Review provenance (pre-registered, diff-blind) - Reviewer: **mos-dt (sb-it-1-dt)** — pre-registration `f549089da` (re-anchored `1dcb4c79f` after rebase), committed **before first read** per the fleet's standing rule. - **Round 1**: findings addressed; citations re-verified against `origin/main` after a wrong-ref correction (reviewer's own, self-reported). - **Round 2**: CLEAR at `caf40afc0`, all eight checks, one **non-gating** finding filed (§5 table keyed on style tokens the builder does not emit — recoverable for one value by lexical accident only). - Author amended on the non-gating finding (`89e26ff7c`, docs-only, +8/−7): the §5 table now keys on the **rendered bullet strings** `builders.ts:79–91` actually emits — verified distinct and exact by the reviewer. - **Re-verdict at `89e26ff7c`: CLEAR**, same pre-registration, **no check added** (an amendment voids a CLEAR and is re-verdicted without inventing gates — the rule binds even when the amendment is one the reviewer asked for). Mechanical summary at head vs merge-base: 3 files, +143/−0, zero code files, zero files outside `packages/mosaic/framework/`, `USER.md` diff vs main **empty**, zero operator strings in added lines. ## Scope Framework docs only. No builder change (the author deliberately took the docs-only branch of the reviewer's two options — a builder edit takes the code-change bar and this diff does not clear it, by design). Ref #960 — context; adoption closure is explicit, not keyword-automatic.

Mos added 3 commits 2026-07-30 21:00:39 +00:00

feat(framework): MOS-STE writing standard + Google-style code + per-user comms choice 6cc093afdb

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]>

fix(framework): ride the existing communicationStyle enum, drop the no-op USER.md edit (mos-dt review #960 ) caf40afc01

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]>

fix(framework): key §5 lookup on rendered bullets, not the token (mos-dt round-2)

ci/woodpecker/pr/ci Pipeline failed

Details

89e26ff7c2

§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]>

Some required checks failed

ci/woodpecker/pr/ci Pipeline failed

Details

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feat/mos-ste-writing-standard:feat/mos-ste-writing-standard

git checkout feat/mos-ste-writing-standard

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#965