What you will be able to do
- Spot inconsistency in three places: against supplied context, inside a response's reasoning, and across repeated runs
- Recognise unsupported confidence, sycophancy and disproportionate hedging as trained-in fingerprints
- Identify bias in a response, including skewed defaults, missing perspectives and problematic framing
- Name which properties are colliding in a failure so you can choose the right fix
1.Inconsistency: against your documents, within the reasoning, across runs
An inconsistency is a response that disagrees with something it should agree with. There are three places to look.
Against the context you supplied. Anthropic's developer documentation defines hallucination to include text that is "inconsistent with the given context." If you upload a contract and Claude's summary gets a clause wrong, that is a hallucination, even if every other line is accurate and nothing was invented about the outside world. Compare the claims against the material you gave Claude, not just against your own sense of what sounds right.
Within the response's reasoning. The same developer guidance suggests asking Claude to explain its reasoning step by step before giving a final answer, because doing so can reveal faulty logic or assumptions. Once the steps are written out, you can see where a conclusion does not follow from the step before it, or where an unstated assumption carried the argument.
Across runs. Claude does not produce exactly the same text every time. The Academy course suggests running the same request for specific facts in a fresh conversation and comparing the results. It calls the variation Next Token Prediction's sampling at work. The developer guide turns this into a check: inconsistencies across outputs could indicate hallucinations. When two chats give two different dates for the same deadline, and neither had a document to work from, don't treat the newer answer as a correction. Treat the disagreement as evidence that neither answer is grounded.
The Academy also names long-conversation drift as a common failure pattern. Over a long exchange, responses can move away from what was set up earlier, so check late answers against early instructions too.
Checkpoint 1 of 6· Exam question
In a single multi-turn conversation, Claude tells a user early on that a product ships in 3 business days, then later in the same conversation states the same product ships in 7 business days without any new information being provided. How should a QA reviewer classify this behavior?
Correct answer: B — An inconsistency, since the two statements about the same fact conflict within one chat
- A. Incorrect. A shipping estimate is plausible and was actually stated twice; the problem is that the two values contradict each other, not that one is fabricated from nothing.
- B. Correct. An inconsistency is when a model gives conflicting answers to the same question without any change in input, which is exactly what happened here.
- C. Incorrect. Bias refers to skewed treatment of a topic or group, not a reviewer question about which of two conflicting numeric answers is favored.
- D. Incorrect. Response timing does not cause a model to contradict earlier output; the two turns are evaluated on content, not on elapsed time.
Checkpoint 2 of 6· Check yourself
You upload a supplier agreement and ask Claude for a summary. The summary says the notice period is 60 days. The agreement says 30. Everything else in the summary is accurate. How should you classify the error?
Anthropic's definition covers text that contradicts the given context, not only invented facts about the world.
“Even the most advanced language models, like Claude, can sometimes generate text that is factually incorrect or inconsistent with the given context.”Source: platform.claude.com
2.Unsupported confidence, agreeable answers and reflexive hedging
Some patterns in how a response sounds are trained in. The Academy explains that Claude's assistant behaviour comes from fine-tuning, which uses human judgments about what makes a good response. Those judgments leave fingerprints: a pull toward sycophancy, a default toward verbosity, occasional over-caution, and loose calibration between stated confidence and actual reliability.
Loose calibration means the tone of a response tells you little about how reliable it is. One Academy exercise asks you to compare a mainstream topic with a niche one. It asks you to notice whether the AI signals uncertainty differently between the two, or whether both answers come with the same confident tone. Another exercise asks you to check specific facts and, where something was fabricated, to note how confident it sounded. When a niche, precise claim sounds just as sure as a textbook explanation, that confidence is not backed by anything.
Sycophancy is agreement you have not earned. The Academy's test is to start a request with a wrong assumption, such as calling a strategy bulletproof, and see whether the AI validates your framing or pushes back. A response that accepts a flawed premise and builds on it can be accurate sentence by sentence and still be wrong overall. The Academy lists agreeable bad premises among the common failure patterns.
Over-caution goes the other way. The Academy suggests noting whether the hedging feels proportionate to the actual risk, or reflexive. Hedging on a claim does not tell you how uncertain that claim really is.
Checkpoint 3 of 6· Check yourself
A user writes: "I'm certain this pricing plan is solid. Write up its strengths." Claude lists only strengths and raises none of the plan's obvious gaps. Which fingerprint is this most clearly?
Fine-tuning leaves a pull toward sycophancy. The Academy's test for it is whether the AI validates your framing or pushes back.
“See whether the AI validates your framing or pushes back.”Source: academy.claude.com
3.Bias: skewed defaults, missing perspectives, uneven framing
Bias is easy to miss because it usually doesn't appear as a false statement. The Academy's knowledge lesson lists inherited bias as one of the typical knowledge failures, and describes it as bias in what counts as "default" or "normal". The model learned its sense of normal from its training data, so its picture of a typical customer, case or user may be an outsider's picture, not the one used in your field.
The Academy's probe for this does not name the assumption. You ask a question that would reveal whether the AI defaults to the outsider's view, such as describing the typical customer, and you note what it treats as normal. You can apply the same reading to any response: what did it assume without being told?
The Academy's role-specific courses add more checks to the Discernment habit. The nonprofit research exercise asks you to note any missing perspectives relevant to your communities. The writing exercise asks you to identify deficit-based framing or problematic language about beneficiaries. The educators' course includes checking for unintended bias. These checks are about what a response leaves out and how it frames people and positions. Every sentence can be accurate while the response as a whole still leans one way. For example, a response might state one group's view plainly and wrap another's in qualifications. Classify that as a framing problem, not a factual error. Fact-checking each claim one at a time won't catch it.
Checkpoint 4 of 6· Exam question
A user asks Claude for a detailed, confident summary of a major news event that occurred after the model's reliable knowledge cutoff. Claude produces specific dates, names, and outcomes that cannot be verified in any source. What is the most likely underlying cause of this response?
Correct answer: C — Claude hallucinated plausible-sounding details to fill a gap past its knowledge cutoff
- A. Incorrect. The scenario states the summary addressed the event in question, so a topic mismatch does not explain the fabricated details.
- B. Incorrect. Systematic favoring of certain groups or viewpoints is bias; inventing unverifiable specifics about a recent event is a knowledge-gap hallucination.
- C. Correct. When a query falls beyond the model's reliable knowledge cutoff and no external grounding is provided, the model can generate confident but fabricated specifics instead of acknowledging the gap.
- D. Incorrect. No tool use or search was described in the scenario, so there are no cached results to attribute the fabricated details to.
Checkpoint 5 of 6· Check yourself
You ask Claude to describe "the typical client" for a specialist trade where clients are mostly small municipal bodies. Claude describes a large private corporation, the stereotype most outsiders would assume. Which failure is this?
The Academy lists inherited bias in what counts as "default" or "normal" as a typical knowledge failure. Here the outsider's view became the default.
“Characteristic failures: staleness, uneven coverage, inherited bias in what counts as "default" or "normal," and inability to attribute where knowledge came from.”Source: academy.claude.com
4.Naming what kind of wrong you are looking at
Recognising a problem is half the job. Naming its type is the other half, because the type tells you what to do next. The Academy's capabilities course describes four model properties: Next Token Prediction, Knowledge, Working Memory and Steerability. It argues that most real failures involve two of them interacting. Hallucinated specifics come from Next Token Prediction combined with Knowledge. Long-conversation drift comes from Working Memory combined with Steerability. The course lists hallucinated citations, long-conversation drift, confidently wrong math and agreeable bad premises as the common patterns.
Naming the properties involved points you to the fix: verify specifics, re-supply context, offload to code execution, or invite pushback. The course calls this diagnostic move Discernment applied, linking it to the AI Fluency competency of evaluating what AI produces. The nonprofit course describes Discernment in practical terms: flag specific claims for verification, notice gaps, and question how recent the information is.
Checkpoint 6 of 6· Match them up
Match each failure pattern to the most targeted fix
Tap a term, then the definition that fits it.
Once you name the properties at play, the Academy pairs each failure with a matching fix.
“Naming the properties at play points you straight to the fix: verify specifics, re-supply context, offload to code execution, or invite pushback.”Source: academy.claude.com
Exam traps
Each one states something that sounds right. Open it to see what is actually true.
1.When two chats give different answers to the same question, the more recent answer is the corrected one.Why is that wrong?
Different outputs from the same prompt are sampling at work. The disagreement is a sign that the answer may be hallucinated, not a sign that it has been corrected.
Covered in Inconsistency: against your documents, within the reasoning, across runs
2.A response that sounds sure of itself is more likely to be reliable than one that hedges.Why is that wrong?
Fine-tuning leaves loose calibration between how confident a response sounds and how reliable it is, so tone is not a reliability signal.
Covered in Unsupported confidence, agreeable answers and reflexive hedging
3.A response is only biased if it contains offensive or factually false statements.Why is that wrong?
Bias often appears as what the model treats as default or normal, or as missing perspectives, even when every individual claim is accurate.
Covered in Bias: skewed defaults, missing perspectives, uneven framing
Sources
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.https://platform.claude.com/docs/en/test-and-evaluate/strengthen-guardrails/reduce-hallucinationsOfficial docs
“Ask Claude to explain its reasoning step-by-step before giving a final answer. This can reveal faulty logic or assumptions.”
↩︎ Inconsistency: against your documents, within the reasoning, across runs“Run Claude through the same prompt multiple times and compare the outputs. Inconsistencies across outputs could indicate hallucinations.”
↩︎ Prediction“Even the most advanced language models, like Claude, can sometimes generate text that is factually incorrect or inconsistent with the given context.”
↩︎ Checkpoint - 2.https://academy.claude.com/courses/ai-capabilities-and-limitations/next-token-predictionOfficial docs
“Run the exact same specific-facts request in a fresh conversation. Compare the two outputs.”
↩︎ Inconsistency: against your documents, within the reasoning, across runs“If it fabricates, note how confident it sounded doing it.”
↩︎ Unsupported confidence, agreeable answers and reflexive hedging“The variation you see is Next Token Prediction's sampling at work.”
↩︎ Exam trap 1 - 3.
“Pay attention to whether the AI signals uncertainty differently between the two, or whether both answers come with the same confident tone.”
↩︎ Unsupported confidence, agreeable answers and reflexive hedging“ask a question that would reveal whether the AI defaults to the outsider's view.”
↩︎ Bias: skewed defaults, missing perspectives, uneven framing“Characteristic failures: staleness, uneven coverage, inherited bias in what counts as "default" or "normal," and inability to attribute where knowledge came from.”
↩︎ Checkpoint - 4.https://academy.claude.com/courses/ai-capabilities-and-limitations/how-ai-gets-its-characterOfficial docs
“Note whether the hedging feels proportionate to the actual risk, or reflexive.”
↩︎ Unsupported confidence, agreeable answers and reflexive hedging“a pull toward sycophancy, a default toward verbosity, occasional over-caution, and loose calibration between stated confidence and actual reliability.”
↩︎ Exam trap 2“See whether the AI validates your framing or pushes back.”
↩︎ Checkpoint - 5.
“Identify any deficit-based framing or problematic language about beneficiaries”
↩︎ Bias: skewed defaults, missing perspectives, uneven framing - 6.https://academy.claude.com/courses/ai-capabilities-and-limitations/when-properties-collideOfficial docs
“Next Token Prediction + Knowledge (hallucinated specifics) Working Memory + Steerability (long-conversation drift)”
↩︎ Naming what kind of wrong you are looking at“This diagnostic move is Discernment applied.”
↩︎ Naming what kind of wrong you are looking at“Naming the properties at play points you straight to the fix: verify specifics, re-supply context, offload to code execution, or invite pushback.”
↩︎ Checkpoint - 7.
“Flag specific claims for verification, notice gaps, and question recency of information”
↩︎ Naming what kind of wrong you are looking at“Note any missing perspectives relevant to your communities”
↩︎ Exam trap 3