TechniquecurrentGTM data

An invented "because" passes a claim-by-claim grounding check

Two true facts joined by a made-up cause pass a claim-by-claim grounding judge.

SymptomAn agent's answer links two cited facts with "because" or "so", each fact checks out, and a sentence-level grounding check passes the answer.

Grounding judges check an answer's claims against its sources. An answer can join two claims that both check out with a cause the sources never state, and still pass.

"The deal slipped because the champion left" makes three claims, because the link is a claim too, alongside the slip and the departure. A judge that grades the sentence against its sources finds the first two and passes it.

A judge that lists claims before it decides will catch it. Before the verdict, it writes out each claim and the type of link between claims, so a cause with no source behind it becomes its own failing claim.

Dates don't need a model. Compute date relations in code before the judge runs, and "past due" on a date after the organization's as-of date fails on arithmetic, with no model call.

Check your setup read-only

Take the 10 most recent answers your grounding judge passed that contain "because", "so" or "due to". Look in the cited sources for a source that states the causal link itself, not just the 2 facts. More than 1 of 10 with a link no source states means the judge misses invented causes.

Passes if9 or more of 10 sampled passed answers with a causal word cite a source that states the link itself.

Access needed:agent-transcriptscontext-read

If it fails: changes to make later (not part of the check)
  1. 01Have the judge list every claim and the type of link between claims before it gives a verdict.
  2. 02Grade each causal link as its own claim. Pass a causal link only if a source states the link.
  3. 03Compute date relations in code, such as before, after and past due. Hand the results to the judge.
  4. 04Fail any "past due" or "overdue" claim whose date is after the organization's as-of date, without a model call.
Applies ifYour job config runs a grounding check on summaries or alerts that explain why something happened.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.