Correct only mistranscribed occurrences of the supplied names and terms. Output only the corrected transcript, with no explanation.

The supplied list is the authoritative spelling reference. Your task includes correcting plausible-looking alternative names and ordinary words that speech recognition substituted for a listed name—not just correcting obvious nonsense.

Use this procedure silently:

1. Scan the entire transcript for listed names and terms, alternative spellings, sound-alikes, split words, acronyms, and fused possessives.
2. Identify supported matches using sound similarity and the local sentence context. Direct address, attribution (“___ says”), and possessive constructions are evidence that a name was spoken. Do not require the person's job title or role to appear.
3. Replace each supported span with the exact listed spelling and capitalization. Preserve a possessive ending when present. Leave already-correct occurrences unchanged.
4. Check again for missed name variants and unsupported additions. Preserve everything outside the matched spans exactly.

## Name corrections to apply

Treat the following as supported correction patterns, not merely possibilities to notice:

- **Caitlin / Kaitlyn → Kaitlynn** when used as a person's name in the work discussion. This includes sentence-initial direct address such as “Caitlin, by Tuesday, …”. A familiar, valid alternative spelling still needs correction; explicit mention of “product manager” is unnecessary.
- **Jackson → Jaxon** when used as the person's name in the work discussion. This includes “Jackson, by Tuesday, …” and assignments involving backend or intake work. Do not leave “Jackson” unchanged just because it is a real name.
- **Kave → Kaveh** when used as a person's name, such as “Kave asked for honest denominators.”
- **Source → Saoirse** when the word occupies a person's-name slot in an ops or deployment discussion. For example, in “Source says the Coyab bill went up … I asked her to dig into the logs,” correct both “Source” to “Saoirse” and “Coyab” to “Koyeb.” The attribution, infrastructure context, and later “her” together support the name correction. Do not demand a closer spelling match.
- **Ted → Tadhg** in a personal conversation about the friend's beach invitation, visiting his place, bringing the kids, or meeting for lunch afterward. For example, “Ted says the beach by his place is great …” becomes “Tadhg says the beach by his place is great …”. This contextual match is sufficient; the transcript need not explicitly call him a friend.
- A name and possessive ending can be fused into a word or acronym. For example, **“AFAS evaluation work” → “Aoife's evaluation work”** when the context supports the intern's work. Replace the entire corrupted name-and-possessive span.

Use the same sound-and-context reasoning for other supplied names. The patterns above apply only where the text supports the corresponding person; they are not unconditional global substitutions.

## Term corrections

Correct recognizable split, respelled, or miscapitalized forms of listed terms to their exact supplied forms. For example:

- “voice flow” → “VoiceFlow” when referring to the product.
- “Coyab” → “Koyeb” when referring to the service.

Check for all supplied terms, including short technical terms and acronyms. Do not overlook a match merely because its raw transcription consists of ordinary words.

## Avoid unsupported insertions

- The list is a spelling reference, not a requirement to mention every entry.
- Require an existing word or span that plausibly represents the name or term. Context helps identify that span; context alone does not justify adding a name.
- A person's role or a related topic is not evidence that their name was spoken. “Investor check-in” does not justify adding “Kaveh” or “Kaveh's.”
- Do not turn an unrelated phrase such as “assured investor check-in” into a person's name merely to improve the sentence.
- Leave genuinely ordinary uses unchanged: for example, “source code” is not “Saoirse code.”
- If there is no supported match, leave the text unchanged.

## Exact preservation

Change only matched name-or-term spans. Preserve all other wording, punctuation, dates, numbers, grammar, capitalization, whitespace, and formatting exactly as supplied. Do not repair general transcription errors, normalize dates, add hyphens, or rewrite sentences—even when another correction seems obvious.

Before outputting, specifically recheck sentence-initial names and ordinary-word name substitutions. Do not miss a supported “Caitlin,” “Jackson,” “Ted says,” or “Source says” correction because the raw wording already looks grammatical.