Retain grammar naming and clarify its planned description

This commit is contained in:
2026-11-11 15:43:26 +00:00
parent 03d1884bfb
commit 2b5b0d6051

View File

@@ -3,7 +3,8 @@
**Updated:** 2026-11-11
**Status:** Topic 1 resolved in ADR 0003; topics 2–4 decided, with implementation
pending; topic 5 deferred; topic 6 remains for discussion.
pending; topic 5 deferred; grammar naming and scope in topic 6 decided, with
description updates pending; the remaining topic 6 choices await discussion.
Work through the remaining topics in order. Their recommendations are starting
points for discussion, not newly adopted restrictions or guarantees.
@@ -159,9 +160,13 @@ test suite; no numerical quality gate is selected here.
Use the preceding decisions and any available evidence to discuss these in order,
without waiting for the deferred evaluation work:
1. **Grammar naming and scope:** the current module is close to copy editing,
with an isolated article exception. Decide whether its name and scope convey
the intended requested work, preserving the accepted editorial allowance.
1. **Grammar naming and scope — Decided:** retain the `grammar` name, module key,
and corresponding prompt IDs. Clarify its description as conservative
punctuation, capitalization, spacing, and whole-word `a`/`an` article cleanup.
Preserve its current requested scope and the accepted cross-module minor
editorial allowance. Update the relevant module descriptions and canonical
documentation during implementation; no rename or broader grammar-correction
remit is planned.
2. **Glossary/homophone overlap:** assess the benefit of their overlapping remit
and repeated glossary passes before changing the default sequence.
3. **Language and examples:** decide whether spoken English and campaign-specific
@@ -171,5 +176,5 @@ without waiting for the deferred evaluation work:
of a mistranscription. Initially retain the conservative default while
explicitly evaluating that tradeoff.
These are product discussions, not selected renames, broader editing permissions,
language-support promises, or changes to validation policy.
The remaining items are product discussions, not selected changes to module
sequencing, language support, or validation policy.