Trust Veracity

The authority layer in action

FROM AI OUTPUT TO AUTHORIZED ACTION

Trust Veracity creates a release boundary around consequential AI-generated work. It checks one specific output against authoritative evidence and organizational requirements before recording whether that work has earned permission to move.

The question changes

A reliable model can produce an answer. It cannot authorize the answer.

EvidenceWhat source records support the claims and calculations?

RequirementsWhat rules must be true for this workflow?

AuthorityShould this work Release, Hold, or Block before action?

A verification record, not a confidence score

See what earns a release decision.

One claim. One source relationship. One bounded result. When the required proof is not established, Hold or Block is the correct outcome.

Verification record RUN 02A7

Q2 finance memo

Claim under review Q2 operating margin increased by 14%. Extracted from the AI-generated artifact
Source
finance_q1.csv + finance_q2.csv
Check
Relative change recomputed
Scope
Q1 2026 → Q2 2026
Result
23.7% — mismatch found

Inspect the evidence relationship

finance_q1.csv records a 27.9% margin; finance_q2.csv records a 34.5% margin.

BLOCK The work stops before the unsupported figure reaches the next system.

Static sample · no customer data is processed here.

The release flow

Four steps, one attached decision.

  1. 01AI-generated work entersAn AI-generated artifact or analysis enters the workflow.
  2. 02Veracity checksSupported claims are tested against source-of-record evidence and workflow-specific business rules.
  3. 03Release / Hold / BlockRelease when requirements pass. Hold when evidence or a rule is unresolved. Block when a required check fails.
  4. 04Evidence remainsThe evidence, checks and decision remain attached to a verification record reviewers can inspect.

Where Veracity fits

Before downstream use.

Teams can keep using their existing generation tools. Veracity checks AI-generated artifacts before they are shared or exported.

A source workbook shows a margin value of 23.7 percent. An AI-generated output file says 14 percent. Veracity checks the AI-generated output file against connected source evidence, fails the accuracy check and blocks the release before it can be shared.

Source workbook Generated output file Accuracy check Release blocked
Q3 Operating Model.xlsx
fx =(34.5% - 27.9%) / 27.9% 23.7%
1 Line itemQ3 valueSourceFormulaStatus
2 Revenue$13.1MGL-102ImportedReviewed
3 Claims reserve$3.1MCL-441ImportedReviewed
4 Prior operating margin27.9%WorkbookImportedReviewed
5 Operating margin34.5%Workbook=margin()Reviewed
6 Relative increase23.7%Workbook=change()Reviewed
7 Evidence refSR-1042SnapshotLockedReady
8 Workbook statusSourceScope definedEvidenceFinal
Generated output file Q3 finance review AI-generated artifact under review
Report contents

Revenue increased to $13.1M.

Operating margin improved to 14%.

Awaiting export.

Verification in progress
Output file Claim contradicted
Configured check
Generated claim 14%
Source re-calculation 23.7%
Accuracy check Failed
Release decision Block
Verification record Attached
Veracity decision Block Source mismatch
Export destinations Block
Slack #finance-review
Block
Teams Quarterly reporting
Block

Veracity blocks release at the accuracy check.

Release checks & verification

An evidence record for every release decision.

Workflow owners define what must be true. Veracity turns those requirements into repeatable release checks, records the evidence and preserves the final decision. Release / Hold / Block | the verification record stays with the AI-generated artifact for review.

The generated finance review says 14 percent. Source evidence re-calculates 23.7 percent. The selected finance check fails and blocks release. The verification record documents the configured checks and decision.

Generated output file Q3 finance review
14%
Source evidence 23.7% Re-calculated value
Finance release profile v0
Selected release checks Required checks
  • Accuracy check Failed
  • Completeness check Pending
  • Freshness check Pending
  • Traceability check Pending
Verification record · sample Block
Q3 finance review
Overall status Accuracy check failed
Verification record Evidence attached · decision recorded

See the release boundary in the context of your workflow.

Request access