Claim verification is a guardrail workflow. Use it when an application, assistant, or review process has drafted a legal/regulatory claim and needs to check whether the published pack supports it. It is not the first step for most business workflows. Start with packs, obligations, applicability, evidence, and calendars; use claim verification to keep generated text grounded.Documentation Index
Fetch the complete documentation index at: https://docs.esheria.ai/llms.txt
Use this file to discover all available pages before exploring further.
Request
Response
Successful responses include status, publication mode, authority IDs, provision IDs, obligation IDs, citation IDs, quote spans, and any correction labels.Correction Example
If a generated answer changes a deadline or statutory detail, the verifier can returnsupported_with_corrections with issue labels such as deadline_mismatch.
When Verification Is Unsupported
Some packs may not have a promotedclaim_evaluation_profile. In that case, claim verification returns unsupported_capability. The pack can still support obligation, applicability, evidence, filing-calendar, export, and graph workflows.
Failure Modes
| Result | Meaning | Product behavior |
|---|---|---|
likely_supported | Published facts support the claim | Show the answer with citations and trace ID |
supported_with_corrections | Nearby source-backed fact supports a corrected version | Show correction context, not the original claim as final |
unsupported_scope | Claim is outside supported scope | Ask for a narrower claim or route to review |
not_found | No supporting published fact found | Do not present the claim as source-backed |
unsupported_capability | Pack lacks a claim verifier | Use generic pack workflows instead |