Terminology consistency control

Add this component when a draft, answer, or review needs stable terminology based only on supplied text, provided sources, or an explicit glossary.

Outcome
Consistent terminology
Keeps repeated terms aligned to one supplied or evidence-supported meaning.
Component type
Terminology-control component
A reusable instruction block for terminology consistency, not a claim-verification or source-retrieval workflow.
Best for
Technical, policy, and research text
Use when inconsistent terms could change meaning, weaken precision, or confuse readers.

Scope and best-fit use

Use this component when terminology must stay consistent. It does not verify factual claims, retrieve sources, classify claims, or reduce overclaims by itself.

Use when
Terms must keep one meaning
Use when the same term appears multiple times and must not shift meaning across the text.
Source boundary
Definitions must be supplied
Definitions must come from the supplied text, provided sources, or an explicit glossary. Missing definitions are marked, not invented.
Boundary
Not a factual-accuracy gate
Use a separate claim, citation, artifact-only, or overclaim control when factual support must also be checked.

Inputs required

Provide the text to review and, when available, an explicit glossary or source material that defines the key terms.

Source text
Paste the draft, answer, or section where terminology consistency must be checked.
Terminology source
Provide an explicit glossary, supplied source material, or state that definitions must be inferred only from the supplied text.

Copy-ready prompt

Copy this component into the instruction layer when key terms must stay consistent without inventing definitions or changing claim meaning. 

TERMINOLOGY CONSISTENCY CONTROL

PURPOSE
Keep key terms consistent across the supplied text without inventing definitions or changing factual meaning.

HARD RULES
- Do not invent definitions for key terms.
- Use definitions only from:
  1. the supplied text,
  2. provided source material, or
  3. an explicit glossary supplied by the user.
- If a key term has no supplied or evidence-supported definition, mark it as: DEFINITION NOT PROVIDED.
- Use each term consistently according to its supplied or evidence-supported meaning.
- Do not silently change the meaning of a claim while improving terminology.
- Do not introduce new factual claims.
- Do not perform source retrieval, citation validation, claim classification, or overclaim reduction unless another instruction explicitly requires it.

OUTPUT FORMAT
Return exactly these sections:

1) TERMINOLOGY SOURCE
- State whether definitions come from supplied text, provided source material, or an explicit glossary.
- If no terminology source is available, write: NOT PROVIDED.

2) GLOSSARY
- Term | Definition | Source / Basis | Status

Status values:
- DEFINED
- DEFINITION NOT PROVIDED
- AMBIGUOUS

3) TERMINOLOGY CONSISTENCY CHECK
- Term | Issue | Why it matters | Recommended fix

4) CLEAN TEXT
- Provide the revised text with terminology made consistent.
- Do not add new factual claims.
- Do not change claim meaning.

FAIL-CLOSED
If the task requires controlled terminology and no terminology source is supplied, ask for the terminology source or glossary before rewriting.

Related controls

Use these only when the task needs controls beyond terminology consistency.

Use provided material only
Use when terminology decisions must rely only on supplied files, excerpts, logs, screenshots, or repository snapshots.
Open prompt →
No simulation / no fabrication
Use when the assistant must not invent facts, sources, citations, files, logs, test results, definitions, or verification steps.
Open prompt →
Return copy/paste-ready structure
Use when the output must be reusable as headings, tables, checklists, or replacement blocks.
Open prompt →