Detecting AI Deception Intent: not assessed
Practice
Menu

Check whether an AI answer is backed by the evidence.

AI answers can sound certain even when their sources are missing, contradictory or too weak to support them. This site helps anyone reviewing an AI answer compare the claim with the evidence it would need and the record that exists. You will learn to classify the result as Supported, Contradicted or Insufficient evidence without guessing at intent.

Try a practice caseSee the four-step method
Featured synthetic case 03 Does the citation support the answer?
Claim
30 days
Required evidence
30 days
Observed record
7 days
Finding
Choose, then reveal
Open the case and make the narrowest call the evidence supports.

How the method helps you reach a defensible result.

The four steps keep a confident answer from substituting for evidence. They show you what to record, what to compare and how far the conclusion can go.

  1. 01

    Record the claim

    Capture exactly what the answer says before interpreting it.

  2. 02

    Define the evidence

    Write down what the record would need to show for the claim to hold.

  3. 03

    Compare the record

    Look for evidence that matches, conflicts with or fails to reach the claim.

  4. 04

    Report the result

    Classify the relationship and keep intent separate.

Read the complete method

Practice with six synthetic cases.

Each case lets you compare one AI claim with the evidence it would need and the record that is actually available. Choose a case and classify the result as Supported, Contradicted or Insufficient evidence.

  1. 01The missing file
  2. 02The reassuring average
  3. 03Unsupported citation
  4. 04Wrong product identity
  5. 05Lost response
  6. 06Supported claim
Boundary

Know what the evidence can—and cannot—tell you.

This site shows how far the available record supports a claim. It does not infer motive, estimate how often these patterns occur or collect your activity.

  • Six visibly synthetic casesTeaching examples, not a prevalence estimate or allegation about a real incident.
  • One deterministic ruleThe browser and local checker import the same classifier.
  • Exact public revisionsEvery source keeps its revision and reviewed-through date beside the claim.
  • No hidden collectionNo account, analytics, tracker, backend or live model receives your choices.

Challenge a result with evidence.

Run the checker, inspect an exact revision, or supply a public-safe counterexample. The record should change when the evidence does.

Challenge the recordOpen the evidence tools