Repository navigation
feat(config): add glossary prompt variable - #31
Merged
Merged
Conversation
Term lists beat mistranscription mappings, which are brittle: one concept arrives in several wrong spellings, and a wrong form often collides with a real word. - Add promptVars.glossaryFile, rendered into the cleanup and summarize prompts - Missing file warns and continues, because the glossary is user data - Prompt rules match on sound and context, and forbid inserting a term - Update example config, README table, and tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A list of mistranscriptions to fix is brittle. One concept arrives in several
wrong spellings, and a wrong form often collides with a real word. Counts from
four months of real transcripts:
katt35,katten19,cut entr14,cuttin5encore70,ankor14bigquery193,bigshare2kattandkattenare ordinary Swedish words, so a mapping would rewrite everygenuine mention. A list of correct terms lets the model decide from context.
What
promptVars.glossaryFile. The recorder reads a user-owned Markdown termlist and renders it into the cleanup and summarize prompts.
not said. A collision example covers the
kattcase.user data that the recorder does not own.
Notes
Glossaryfield feeds both prompts, so summaries also use thecorrected spellings.
Test plan
mise run build(lint, test, tidy, goreleaser check)LoadreadspromptVars.glossaryFilefrom JSONrecorder prompts cleanupandrecorder prompts summarizerender a liveglossary file