2.5 KiB
Migrating to application configuration v3
Audita v4.0.0 adopts application configuration schema v3. Audita v3.1.x uses
schema v2. Set version: 3 in the application file and move glossary entries into
configuration. Use the configuration reference and
maintained examples for the new formats.
- Replace
pipeline.moduleswith orderedpipeline.stagesrecords containingmoduleand any per-entry overrides. An explicit empty list runs normalization. - Define named
glossary_collectionsin configuration or its companion imports; select them usingglossariesandprotected_terms. Rename each legacy entry'ssummarytodescriptionto preserve its prompt context. Remove--glossaryand--modulesfrom invocations. - Move profiles and backends out of the application configuration and retired
profiles_dirlayout into PromptKit resources. Use its current list records, IDs, credential sources, and backend admission settings. Select proposal and validation profiles in applicationllmsettings. - Use the shared
--debugflag for capture;diagnostics.work_dirremains the parent directory. Review report and output destinations before running. - Completion counts are hidden by default. Use
--verboseto see them on stderr, including when ordinary reports are disabled.--debugalso shows counts unless followed by--quiet. See CLI reporting.
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 for lifecycle and recovery.