AI Governance // Truth Forensics 03

When AI Cannot Determine the Truth

Desmond Otieno Odhiambo · ClearGlass Intelligence · Burlington, Ontario · 30 September 2026

An analyzer can find a two-second gap in a video's frame timing. It cannot tell you whether those frames were dropped by an overloaded encoder or cut by a person. Any system that pretends otherwise is not being careful. It is being confident.

What automated analysis is good at

Machines are excellent at the tedious, exact parts of media examination:

None of that is intelligence in the interesting sense. It is measurement. It is also the part people do badly.

What it cannot know

SignalWhat it showsWhat it cannot determine
Frame-timing gapIntervals are missing from the timelineEncoder drop, pause, or deletion
Exact digital silenceSamples were zeroedNoise gate, codec, mute button, or edit
Abrupt waveform stepA sharp discontinuityKnock, plosive, cable click, or splice
Cloned regionTwo areas are identicalWhich is the original; whether the pattern is genuinely repetitive
Editor in the software tagA program wrote the fileWhat, if anything, it changed
No indicators at allThe available tests found nothingThat the content is authentic

The last row is the one vendors skip. The absence of indicators is a statement about the tests, not about the event. The honest sentence is: no manipulation indicators detected by the available analyzers; authenticity cannot be established solely from this analysis.

Language is a control

“This video is fake” is a conclusion about the world. “Manipulation indicators detected; human review required” is a statement about analysis. Reports should be written so that the second is the only thing the machine is allowed to say.

The ClearGlass report generator enforces it. Engine-authored text passes a guard that refuses certainty phrasing (“is fake”, “proves authentic”, “100% accurate”, “guaranteed”). Quoted user text, such as the claim under test or a reviewer's note, is exempt, because a report must be able to quote a claim it does not endorse. Every line of the report is typed as an observation, an interpretation or a conclusion.

Governance that holds up

  1. Record every analyzer run: which analyzer and version, the input hash, the output hash, when, and for whom. If a model provider is involved, record the model and prompt version too.
  2. Keep external models opt-in. Evidence is often sensitive. The ClearGlass console calls no AI service at all; an adapter would have to be switched on deliberately, and every call would be logged the same way.
  3. Separate duties. The analyst who produced a finding cannot accept or reject it. A reviewer can request a second opinion, and the requester cannot then decide alone.
  4. Append decisions; never edit findings. A reviewer rejecting an item excludes it from the claim assessment, and the report says who did so, when, and why.
  5. Keep demonstrations labelled. Synthetic data stays SIMULATED whatever a reviewer does, so a demo can never be mistaken for a case.

A buyer's checklist

Before relying on any media-authenticity tool, ask:

See how each of these is handled in the Truth Forensics console, on synthetic data or on your own files, without uploading anything. Companion pieces: Truth Is an Evidence Graph and Why Deepfake Detection Needs Chain of Custody.

Claim boundary. The ClearGlass Truth Forensics system provides analytical indicators and provenance analysis. It does not independently establish the truth of real-world events and should not replace qualified forensic, legal, investigative, or evidentiary review. No detection-accuracy figures are claimed.