> ## Documentation Index
> Fetch the complete documentation index at: https://www.latentcast.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reviewing flagged terms

> LatentCast marks the rules it is least sure about and explains why — how to work through them quickly and confidently.

When rules are generated for you rather than typed by hand, some are obvious and some are a
judgement call. Rather than presenting them all as equally certain, LatentCast marks the ones worth
a human ear and tells you why.

Working through that list is the fastest quality win available in the whole product.

## What a flag means

A rule marked **needs review** carries a short **analysis** note explaining the doubt: an unusual
spelling, a name that could be read two ways, a term the system's own checks disagreed about. It is
a request for your attention, not a claim that the rule is wrong.

## Working through the list

<Steps>
  <Step title="Filter to what needs you">
    The rules list filters by review state and by issue. Set it to show only what needs review and
    you have your working list.
  </Step>

  <Step title="Read the note, then listen">
    The note tells you what the doubt is. The play buttons tell you whether it matters. Judge with
    your ears, not with the spelling.
  </Step>

  <Step title="Accept or correct">
    If it sounds right, mark it reviewed. If it does not, fix the say-as. **Editing a rule counts as
    reviewing it**, so there is no second step after a correction.
  </Step>
</Steps>

The header counts what is left, so you can see the list shrink.

## Also worth filtering for

Beyond the review state, the list can show you the rules with structural problems:

* **Shadowed** — a rule that will not be heard because another dictionary defines the same term.
  Either delete it or disable the competing dictionary.
* **Duplicates** — the same term defined more than once.
* **Engine default** — rules deliberately not sent to a particular engine, which is useful when
  checking that an override you set is still what you intended.

## How to judge a name

* **Say it out loud yourself first**, then play the rule. Comparing two sounds is easier than
  evaluating one.
* **Prefer the pronunciation the person or company uses**, not the one their spelling suggests.
  If you are unsure, their own website or a video of their team usually settles it.
* **Test in the language it will be spoken in.** A name inside a Dutch sentence and the same name
  inside an English one are two different problems.
* **A term that is only ever written, never spoken, needs no rule.** Skip it.

## Newly generated dictionaries start switched off

A dictionary produced by the [generation run](/docs/guides/names/dictionaries-from-your-list) arrives
disabled. That is on purpose: nothing reaches a customer's video until a person has looked at it and
enabled it.

## Next

<CardGroup cols={2}>
  <Card title="Building a dictionary from your list" href="/docs/guides/names/dictionaries-from-your-list">
    Where flagged rules usually come from.
  </Card>

  <Card title="Pronunciation dictionaries" href="/docs/guides/names/pronunciation-dictionaries">
    Rules, notations and per-engine overrides.
  </Card>
</CardGroup>