Retain English defaults and plan broader prompt examples

This commit is contained in:
2026-11-11 15:58:32 +00:00
parent 6e30054c36
commit 2712a3887f

View File

@@ -3,9 +3,9 @@
**Updated:** 2026-11-11 **Updated:** 2026-11-11
**Status:** Topic 1 resolved in ADR 0003; topics 2–4 decided, with implementation **Status:** Topic 1 resolved in ADR 0003; topics 2–4 decided, with implementation
pending; topic 5 deferred; grammar naming/scope and glossary/homophone overlap pending; topic 5 deferred; grammar naming/scope, glossary/homophone overlap,
in topic 6 decided, with description updates pending; language/examples and and language/examples in topic 6 decided, with description and example updates
meaning-reversal policy await discussion. pending; meaning-reversal policy awaits discussion.
Work through the remaining topics in order. Their recommendations are starting Work through the remaining topics in order. Their recommendations are starting
points for discussion, not newly adopted restrictions or guarantees. points for discussion, not newly adopted restrictions or guarantees.
@@ -192,12 +192,14 @@ without waiting for the deferred evaluation work:
merely because it targets a glossary term. No module consolidation is planned merely because it targets a glossary term. No module consolidation is planned
in this pass. Reevaluating defaults does not depend on the deferred formal in this pass. Reevaluating defaults does not depend on the deferred formal
evaluation work in topic 5. evaluation work in topic 5.
3. **Language and examples:** decide whether spoken English and campaign-specific 3. **Language and examples — Decided:** retain English as the bundled default.
examples are the right bundled defaults, and how broadly those defaults Keep useful existing campaign examples and add a few more general examples
should apply. during the prompt editing pass. Use broadly applicable wording for names,
terminology, and glossary entries, without asserting D&D specificity or
adding a disclaimer about it. Broader language support is outside this pass.
4. **Meaning-reversal policy:** the guard can also exclude a genuine correction 4. **Meaning-reversal policy:** the guard can also exclude a genuine correction
of a mistranscription. Initially retain the conservative default while of a mistranscription. Initially retain the conservative default while
explicitly evaluating that tradeoff. explicitly evaluating that tradeoff.
The remaining items are product discussions, not selected changes to language The remaining meaning-reversal item is a product discussion, not a selected
support or validation policy. change to validation policy.