Foundation 01 · Evidence boundaries

Inspect the claim
before the signal.

A badge, signature, log, citation, or credential is never the first question. Start by naming the claim, the evidence that could bear on it, the scope of that evidence, and what remains unknown.

Learning boundary. This lesson provides an inspection framework. It does not determine the truth of any claim, validate a credential, certify a source, assess compliance, or make a reliance decision for a reader.

Learning objective

Separate the statement from the reason to rely on it.

By the end of this lesson, you should be able to distinguish a claim, its issuer, direct evidence, interpretive context, scope, unknowns, and the different decision a particular reader might make.

01 · Claim

What is being said?

Write a bounded statement about a named subject. Avoid folding the claim, the conclusion, and a marketing adjective into the same sentence.

02 · Evidence

What observation, record, or method bears on it?

Link the claim to a source that can be inspected. Label whether it is direct evidence, an interpretation, a framework, or an unresolved assertion.

03 · Scope

What does the evidence not establish?

Name the time range, audience, conditions, and missing facts. A source can be authentic and still be too narrow or old for the proposed decision.

04 · Reliance

Who decides whether it is enough?

A verifier or reader applies their own rule, context, and threshold. Technical verification and business, safety, legal, or editorial judgment are separate steps.

Practice lab

Unpack a product statement before sharing it.

A public page says a workflow is “verified, secure, and reliable.” It links to a screenshot of a green status panel and a dated engineering note, but does not name the system boundary, test method, owner, or conditions under which the statement applies.

  1. Rewrite the claim as three separable, testable statements.
  2. List the evidence a reader could inspect for each statement.
  3. Write the scope and unknowns that the screenshot and note leave open.
  4. Name the decision a reader must still make rather than treating the display as a conclusion.

Source shelf

Inspect how standards separate verification and reliance.

  1. W3C Verifiable Credentials Data Model v2.0Read the distinction between cryptographically verifying a credential and evaluating the truth or suitability of its encoded claims before relying on it.
  2. NIST AI Risk Management FrameworkUse this voluntary guidance to structure questions about context, measurement, management, and governance; it is not a certification program.

Continue the pathway

Next: preserve the
provenance.