Clarify ongoing reevaluation of module defaults

This commit is contained in:
2026-11-11 15:53:46 +00:00
parent 2261a38a6b
commit 6e30054c36

View File

@@ -20,7 +20,10 @@ The maintainer reports that nearly all module behavior was selected through
practical experimentation. Treat that experience as evidence when reviewing the
design: overlapping responsibilities and repeated passes are not inherently
redundant. The deferred evaluation work does not imply an absence of empirical
support for the existing module design.
support for the existing module design. This experience informs ongoing choices;
it does not lock in the current default. Frequently reevaluate the default module
combination and sequence, selecting what has been observed to work best for most
workloads.
Retain the strengths: conservative transcript editing, explicit literal-span and
deletion semantics, distinct glossary context and protection, full before/after
@@ -174,17 +177,21 @@ without waiting for the deferred evaluation work:
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 — Decided:** retain both modules, their useful
overlap, and the existing default sequence documented in
[configuration](../config.md#pipeline-and-glossary-selections). The maintainer's
practical experience establishes that two glossary passes help, and some
workloads benefit from three or more. Preserve operators' ability to configure
2. **Glossary/homophone overlap and defaults — Decided:** retain both modules and
their useful overlap. Keep the existing default sequence documented in
[configuration](../config.md#pipeline-and-glossary-selections) for this pass.
Frequently reevaluate the default and set it to the combination and sequence
of modules observed to work best for most workloads. The maintainer has
observed that two glossary passes help and some workloads benefit from three
or more; these observations inform the current choice without fixing a
permanent number or order of passes. Preserve operators' ability to configure
additional passes. Clarify the complementary requested roles: glossary stages
focus on known terms supported by selected glossaries; homophone stages look
more broadly for plausible spoken-word mistranscriptions and may also use
glossary evidence. Do not exclude an otherwise supported homophone correction
merely because it targets a glossary term. No module consolidation or default
sequence change 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
evaluation work in topic 5.
3. **Language and examples:** decide whether spoken English and campaign-specific
examples are the right bundled defaults, and how broadly those defaults
should apply.