Claim Lifecycle
A claim moves through four states:draft, approved, expired, or rejected.
- Approval requires a source URL. A claim cannot be approved until it carries a link to what supports it.
- Expiration is explicit. A claim can carry an expiration date; once passed, it reads as expired regardless of its stored status.
- Re-approving an expired claim requires setting a new expiration. Approving it again does not silently extend the old date — you either supply a new one or clear it.
Scope
A claim can be scoped to a vertical (healthcare, legal, fintech, …) and a jurisdiction (US, a state, a region). A claim with a jurisdiction is only offered to generations in that same jurisdiction; a claim with no jurisdiction set stays available everywhere. This keeps a claim that’s only true under one regulatory regime from being retrieved into a generation it doesn’t apply to.Using the Registry
1
Draft a claim
State the exact fact, preserving every qualifier and limitation. Attach a source title and URL, and optionally a vertical, jurisdiction, expiration, and tags.
2
Approve
A claim needs a source URL before it can be approved. Once approved, it becomes eligible evidence for matching future generations.
3
Reuse
Approved, unexpired claims are retrieved automatically when Adaptive Intelligence’s “Use verified claims” control is on and the generation’s vertical and jurisdiction match.
4
Expire or revalidate
Mark a claim expired when it’s no longer current. Re-approving it requires a fresh expiration date rather than reinstating the old one.
Adaptive Intelligence
Control whether generations draw on the claims registry.
Content Governance
See how claim-level evidence fits into the content passport.