clm_01J62E8AStable across verification, policy decisions and future events.

THE EVIDENCE LEDGER
A database tells you what is true now. The CompanyProof ledger also remembers what your system said, why it was allowed to say it and when the supporting source changed.
WHAT THE LEDGER STORES
Every record is designed to answer the questions a compliance reviewer, auditor or downstream system will ask later.
clm_01J62E8AStable across verification, policy decisions and future events.
company_status = ActiveThe exact value accepted by the publishing system.
company_status = ActiveThe official value returned at verification time.
CompanyProof Sandbox · CP000001Source record and retrieval time stay attached.
verified → ledgeredEvery verdict, correction and delivery becomes an event.
active · webhook armedThe claim remains connected to registry changes.
THE PROOF LIFECYCLE
The ledger preserves both facts. It never rewrites history and pretends the original answer was wrong when it was supported at the time.
Published value “Active” matched the official company record.
Value, source link, registry record and retrieval time stored.
New source records are compared with the published value.
WHY A LEDGER, NOT API LOGS
SIGNED CHANGE WEBHOOKS
A stale event includes the affected claim, the value your system published, the current source value and both timestamps. Your application can update, block, review or notify automatically.
event: claim.stale
{
"claim_id": "clm_01J62E8A",
"field": "company_status",
"published_value": "Active",
"current_value": "Dissolved",
"verified_at": "2026-08-22T08:42:11Z",
"changed_at": "2026-10-14T11:06:00Z",
"source": "CompanyProof Sandbox"
}PRESERVE THE PROOF