Correct misrecognized names and terms in the raw speech-to-text transcript using the supplied names-and-terms list as the canonical spelling reference. Output only the corrected transcript.

## Scope
- Change only the text needed to correct a listed name or term. Preserve all other wording, sentence structure, punctuation, capitalization, hyphenation, dates, and numbers.
- Do not fix grammar, polish prose, remove filler, or correct unrelated ASR errors.
- Keep already-correct names and terms unchanged.
- Correct every occurrence, including names at the beginning of a transcript, direct addresses, and names in lists or comparisons.

## Recognizing errors
Use pronunciation, spelling similarity, sentence structure, nearby references, and the supplied descriptions together. A familiar name or ordinary word can still be a misrecognition of a listed name. Do not leave a clear match unchanged merely because the raw spelling is itself valid.

An explicit role mention is not required. For example, “Jackson, by Tuesday…” is a direct address to Jaxon even if the sentence does not call him a backend engineer.

Descriptions help distinguish plausible spoken names; they do not supply names missing from the transcript. Never replace a phrase with a name merely because its topic matches that person's role.

## High-priority name corrections
Apply these when the raw text refers to a person:
- “Jackson” → “Jaxon,” including direct address (“Jackson, by Tuesday…” → “Jaxon, by Tuesday…”) and discussion of spelling (“Jackson keeps getting spelled…” → “Jaxon keeps getting spelled…”).
- “Caitlin,” “Kaitlin,” or “Caitlyn” → “Kaitlynn.” This includes sentence-initial direct address: “Caitlin, by Tuesday…” → “Kaitlynn, by Tuesday…”.
- “Kave” → “Kaveh.”
- “Oifi” → “Aoife.” Aoife is pronounced approximately “EE-fa”; distorted renderings of that sound can also be name errors.
- “Sasha” → “Saoirse” when it is a plausible rendering of the listed deployment/ops person's name, such as “Sasha already warned us not to describe an owned machine as free” → “Saoirse already warned us not to describe an owned machine as free.”
- “Sarah” or “Sarah's” can represent “Saoirse,” especially when the transcript is explicitly discussing names being transcribed or spelled incorrectly. Use the sentence's grammatical role to choose the ending.
- “Source” used as a person's name can represent “Saoirse.” For example, “Source says the Coyab bill…” followed by “I asked her…” → “Saoirse says the Koyeb bill…”. Leave ordinary uses such as “the source of the problem” unchanged.
- “Ted” referring to the friend in a personal or family outing context → “Tadhg.” For example, “Ted says the beach by his place…” → “Tadhg says the beach by his place…”.

Apply the same sound-and-context reasoning to the other supplied names. Do not restrict correction to the examples above.

## Possessives and name endings
Preserve genuine possessives: a misrecognized possessive becomes the canonical name plus the appropriate possessive ending.
- “Jackson's script” → “Jaxon's script.”
- “design and AFAS evaluation work” → “design and Aoife's evaluation work.”

However, an apparent possessive ending can itself be part of the misrecognition. Do not retain it when the sentence clearly requires a nonpossessive name.
- “Jackson keeps getting spelled some other way, and so does Sarah's.” → “Jaxon keeps getting spelled some other way, and so does Saoirse.”

In that example, “Saoirse” is the subject of “does,” not a possessive. This is a name correction, not permission to fix unrelated grammar.

## Term corrections
Use the exact canonical spelling and casing of listed terms when correcting phonetic renderings, incorrect spacing, or joined words.
- “Coyab” and similar phonetic renderings of the hosting service → “Koyeb.”
- “voice flow” referring to the listed product → “VoiceFlow.”
- Apply the same reasoning to vLLM, KV cache, LoRA, MLX, AI Builder Space, Superlinear, intake, Codex, and prefill.

Do not convert an ordinary word or phrase into a product or technical term unless pronunciation and usage support that correction.

## Avoid unsupported substitutions
- An investor discussion does not itself imply “Kaveh.”
- Deployment discussion does not itself imply “Saoirse.”
- “assured investor check-in” does not contain a plausible rendering of “Kaveh's”; leave it unchanged.
- Do not add names, expand references into names, or replace unrelated people merely to make the transcript fit the supplied list.

## Final check
Before outputting, scan the entire transcript once more:
1. Check every apparent personal name, especially direct addresses and familiar alternative spellings such as Jackson and Caitlin.
2. Check unusual spellings and ordinary words that could be spoken names, including Oifi, Sasha, Sarah's, and Source.
3. Check all listed-term sound-alikes and split or joined forms.
4. Verify that each change has an existing plausible spoken name or term as its source, and that all unrelated text remains unchanged.

If no supported correction exists, output the transcript unchanged.