Remove confidence scoring and refine correction prompts

This commit is contained in:
2026-11-11 17:05:52 +00:00
parent bbf89bb4f5
commit d155bf4cb3
92 changed files with 448 additions and 786 deletions

View File

@@ -21,6 +21,20 @@ configuration. Use the [configuration reference](../config.md) and
stderr, including when ordinary reports are disabled. `--debug` also shows
counts unless followed by `--quiet`. See [CLI reporting](../cli.md#processing).
## Confidence removal
Remove root `thresholds` and stage `confidence_threshold` settings, and the
`--glossary-confidence-threshold`, `--homophones-confidence-threshold`,
`--spoken-word-confidence-threshold`, and `--grammar-confidence-threshold` flags.
The `confidence_threshold` validator has been removed from the built-in chains.
Update custom proposal, validation, and repair prompts to omit `confidence` from
response examples and instructions. Audita's response schemas no longer accept
that field. Validator responses still require `approved` and `reason`; approvals
may use an empty reason. Corrections in debug records and other affected
serialized proposal/repair data no longer carry confidence, so consumers must
stop requiring or interpreting it. No replacement score or threshold is provided.
Inspect configuration and resources before processing, then try a controlled
small transcript. Processing preflight checks every glossary correction and
selected role before preparing outputs or invoking a model. See [operations](../operations.md)