Architecture recipe

Verify an answer claim by claim

Separate supported, unsupported and conflicting claims inside one response instead of assigning a wholesale truth label.

Intermediate35 minUpdated Aug 14, 2026
Outcome

What you will build

A verification report that shows the basis and status of every material claim in an answer.

Before you begin

Inputs and ownership

  • Generated answer
  • Source-bound evidence
  • Claim materiality rules
Conceptual configuration

Blueprint

This illustrates the governed fields to define during onboarding; it is not a public production API contract.

{
  "claim": "The policy applies for 30 days",
  "status": "supported",
  "basis": ["policy.refunds.eu@v4#section-3"],
  "verified_at": "inference"
}
Implementation path

Build it step by step

  1. 01

    Segment material claims

    Separate factual assertions that could change the user’s decision.

  2. 02

    Resolve the source basis

    Attach each claim to the exact knowledge unit that supports or contradicts it.

  3. 03

    Assign a governed status

    Mark claims supported, unsupported, conflicting or out of scope.

  4. 04

    Review the final output

    Remove or qualify unsupported claims before the answer leaves the governed path.

Verification checklist

Prove the governed path

  • The permitted path produces an answer from approved evidence.
  • An unsupported request returns an explicit governed outcome.
  • Every material claim resolves to a known knowledge unit.
  • The decision can be rerun after a source version changes.
Next recipeRe-verify outputs after a source changes→