Jewelers & brands
If you make an origin claim, can your customer independently inspect its basis?
See how PV fits →PROVENANCE VERIFIED™Independent gemstone provenance
Provenance claimspeople and machines can verify.
Evidence-backed provenance records that people, platforms, and AI systems can inspect, verify, and monitor over time.
EvidenceTrust StateLifecycleMachine Access
01 / 07IdentifyResolve subject and submitter identity.
{
"record_id": "DET-V1-0CC5D81A36B661A7E9DBE0D2",
"record_state": "RESOLVED",
"lifecycle_state": "ACTIVE",
"trust_state": "TIER_1_SELF_REPORTED",
"actionability": "VERIFY_WITHOUT_ACCOUNT",
"authority_state": "LIMITED"
}PRODUCT MODEL
Verify → Certify → Register → Monitor → Integrate.
Five verbs describe how humans, organizations, and machines use the same governed trust system without creating parallel truth.
01VERIFY
02CERTIFY
03REGISTER
04MONITOR
05INTEGRATE
Marketplaces
If you display a provenance claim, what evidence supports it?
See how PV fits →Institutions
If provenance affects a risk decision, what exactly are you relying on?
See how PV fits →AI systems
If your model repeats a provenance claim, can it explain why?
See how PV fits →WHAT A PV RECORD CONTAINS
The claim, the evidence, the state, and the limits stay together.
A governed record separates record state, lifecycle state, trust state, actionability, and authority state so a human or machine can inspect what is known without inventing what is not.
Evidence scope
Which evidence supports the record, where it came from, and what independence or correspondence limits remain.
Trust state
What the governed determination supports, including tier, claim scope, qualifications, and limitations.
Lifecycle
Whether the record is active, suspended, reactivated, superseded, revoked, or expired.
Authority boundary
Whether separate authority for signing, issuance, marks, or registry publication is actually live.
GOVERNED RECORD REGISTRY
Inspect the record behind the provenance claim.
The public registry resolves governed records and their current lifecycle without calling the registry itself authoritative while registry authority remains separately controlled.
LIFECYCLE
A provenance record is not a static certificate.
PV preserves changes over time instead of replacing history with the newest state.
01ACTIVE
02SUSPENDED
03REACTIVATED
04SUPERSEDED
05REVOKED
06EXPIRED
Suspension, reactivation, supersession, revocation, and expiration remain resolvable so marketplaces, institutions, customers, and AI systems do not rely on stale provenance.
MACHINE ACCESS
The same trust state can be consumed by software and AI.
Use the public machine-trust endpoint for governed record resolution, then API, MCP, SDKs, events, and webhooks for authorized integrations.
Machine trust
Resolve a governed public record without an API key.
AI integration guide →API + MCP + SDK
Build workflow integrations while preserving the distinction between trust, actionability, lifecycle, and authority.
Developer resources →INSTITUTIONAL TRUST
Trust is inspectable before it is marketable.
Security, independence, evidence policy, lifecycle controls, operator identity, and live authority state remain public parts of the product.
PROVENANCE VERIFIED™
Verify it. Certify it. Keep it resolvable.
Start with a public record, request a governed certification workflow, or integrate machine-readable provenance into your own product.