# ClaimAnchor™
## Evidence Provenance Infrastructure for Insurance
### The independent chain-of-custody layer for claim documents.

**Product of ICPO X Inc. — Pre-Release Draft · June 2026**

---

## The Problem: Insurance Has No Independent Evidence Layer

Insurance is a document business. Every claims decision depends on records that can be altered, backdated, duplicated, fabricated, or resubmitted in modified form.

Existing systems can prove where a document is stored, who accessed it, and who uploaded it.

They cannot independently prove:

- When the document first entered the process
- Whether it changed after submission
- Whether everyone is looking at the same version
- Whether the record presented in a dispute is identical to the original

**Claims systems were built to manage documents. Not to verify them.**

---

## Why Now

The provenance problem is not new. The urgency is.

| 2018 | 2026 |
|---|---|
| Altering records required expertise | AI tools make document manipulation accessible and inexpensive |
| Fraud investigations were reactive | Real-time authenticity concerns across every claim type |
| Document authenticity assumed | Document authenticity increasingly questioned |
| Provenance optional | Provenance becoming a compliance expectation |

AI has reduced the cost of document manipulation to near zero. Detection tools tell you whether something looks suspicious. Provenance tells you what was submitted and when. Those are different problems, and only one of them has an independent infrastructure answer.

---

## The Industry Has Already Named This Gap

**Guidewire** (January 2026) called for insurers to invest in "provenance-protected workflows" and "real-time verification tools," describing the need to verify "where the digital content came from, whether it's been altered, and how confident they can be in its authenticity."

Guidewire described a requirement. Not a product.

**Verisk** (*State of Insurance Fraud*, March 2026):
- **98%** of insurers say AI editing fuels fraud
- **76%** report increased sophistication in claim submissions
- **45%** anticipate stricter proof-of-loss documentation requirements within 3–5 years
- **36%** of consumers said they would submit digitally manipulated photos to support a claim
- Only **43%** feel very confident detecting authenticity at scale

**NAIC** explicitly identifies fraud prevention and immutable audit trails as blockchain use cases for claims management — stating that blockchain records are permanent, cannot be deleted, and provide a reliable audit trail.

**Deloitte** identifies trusted records, fraud reduction, and transaction validation as blockchain's strongest insurance applications.

**RiskBlock Alliance** (industry consortium): launched specifically to reduce fraud, streamline claims, and create shared records validating customer and claim information across multiple parties.

The insurance industry is not debating whether provenance matters. It is debating who provides it.

---

## Why Existing Systems Are Not Enough

Every buyer will ask: *"Doesn't Guidewire already do this? Doesn't our document management system timestamp uploads?"*

| Capability | Claims System | Document Management | Fraud Platform | **ClaimAnchor** |
|---|---|---|---|---|
| Store records | ✓ | ✓ | — | — |
| Track workflow | ✓ | Limited | — | — |
| Detect suspicious claims | Limited | — | ✓ | — |
| **Independent provenance** | ✗ | ✗ | ✗ | **✓** |
| **Third-party verifiable** | ✗ | ✗ | ✗ | **✓** |
| **Immutable evidence record** | ✗ | ✗ | ✗ | **✓** |
| **Neutral-party timestamp** | ✗ | ✗ | ✗ | **✓** |

Existing systems create timestamps and audit trails within environments controlled by participating parties — even immutable internal logs, WORM storage, and evidentiary controls remain inside that party's architecture. ClaimAnchor adds an independently verifiable timestamp and integrity record that exists outside those environments entirely, on a public network controlled by no one.

**ClaimAnchor does not replace any of these systems. It installs underneath them as the independent evidence layer none of them provide.**

---

## The Solution

**ClaimAnchor provides independently verifiable proof of document integrity and timestamped existence.**

At the moment a claim document leaves your organization, ClaimAnchor:

1. Creates a cryptographic fingerprint (SHA-256 hash) of the document
2. Anchors that hash to the Bitcoin blockchain — a permanent, public record controlled by no single party
3. Stores the full record on Arweave — permanently accessible, decentralized
4. Returns a ClaimAnchor Certificate — the portable proof of provenance

**The result:** An independent record that can be verified without trusting the agency, the carrier, or ClaimAnchor — proving that a specific document existed in a specific form at a specific time.

**The reference frame:** DocuSign proved signing happened. ClaimAnchor proves submission happened — and what was submitted.

**Operationally:** Zero workflow change for producers. Documents pass through a ClaimAnchor endpoint at submission. The Certificate is the only new artifact.

---

## What ClaimAnchor Does Not Do

Buyers benefit from clarity on scope before evaluating fit.

| ClaimAnchor Does Not… | ClaimAnchor Does… |
|---|---|
| Determine whether a document is truthful | Prove a specific document existed in a specific form at a specific time |
| Detect fraud automatically | Preserve independently verifiable evidence for fraud review |
| Replace claims management systems | Add independent provenance beneath them |
| Replace SIU investigations | Reduce uncertainty about document history before investigations begin |
| Replace compliance programs | Strengthen evidentiary controls within existing compliance frameworks |
| Prove who created the original document | Prove what was submitted, by which organization, and when |

---

## The Elevator Pitch

> *"AI has made it easy to manipulate insurance evidence. Insurers are investing heavily in fraud detection — but detection only tells you whether something looks suspicious. ClaimAnchor solves a different problem: provenance. We create an independent chain of custody for every claim document so agencies, MGAs, and carriers can prove exactly what was submitted, when it was submitted, and whether it changed afterward. Think of it as DocuSign for insurance evidence integrity."*

---

## The Documented Evidence of Pain

Document authenticity disputes are not hypothetical. Insurance organizations already devote investigative, legal, regulatory, and forensic resources to resolving them — after they occur. ClaimAnchor proposes a proactive control.

**Finding 1:** A national carrier engaged forensic investigators to analyze HOA loss-assessment letters that appeared modified after submission — comparing original vs. resubmitted documents and tracing edit histories through metadata. Claim coverage decisions and policy-period determinations were affected.

**Finding 2:** In a case involving State Auto, courts upheld a carrier's fraud position after the insured submitted altered invoices. The dispute escalated through federal litigation and appeal. A provenance record at submission would have established what was presented and when — before litigation began.

**Finding 3:** California's SIU regulations mandate preservation of documents obtained during fraud investigations. Regulators already treat evidentiary chain management as a core insurance function — a regulatory foundation for future provenance requirements.

**Finding 4:** Insurance fraud investigators routinely analyze creation dates, revision histories, and file provenance to determine whether submitted evidence was manipulated. Nobody funds metadata forensics unless document authenticity affects claims outcomes.

**Finding 5:** Alteration of insurance certificates and coverage records has repeatedly generated fraud and forgery proceedings because downstream parties relied on document authenticity when making decisions.

**Finding 6:** A recent life-insurance fraud scheme involved false identity records, altered application materials, and fabricated death documentation. The insurer incurred investigation costs to reconstruct the documentary history.

*A structured research project is underway toward "The Insurance Provenance Gap: Twenty Real Cases." See the evidence case tracker.*

---

## The Operational Cost of Provenance Failures

Provenance disputes generate operational cost across multiple categories — before anyone counts legal fees:

| Activity | Cost Driver |
|---|---|
| SIU investigation | Investigator hours, outside expertise, document forensics |
| Outside counsel | Litigation expense, dispute response, regulatory defense |
| Claims delay | Administrative burden; claimant relations; adjuster time |
| Regulatory response | Compliance labor; documentation production; review cycles |
| Audit reconstruction | Operations burden; file retrieval; carrier relationship management |
| Forensic metadata analysis | Specialized investigator cost when standard records are insufficient |

Each of these costs is incurred reactively — after the provenance problem surfaces. ClaimAnchor makes the record before the problem exists.

---

## Pricing

Sold as risk control infrastructure — not by certificate count or blockchain transactions.

| Tier | For | Price |
|---|---|---|
| **Agency Starter** | Independent producers | $99/month |
| **Agency Professional** | Growing agencies | $249/month |
| **Agency Pro** | High-volume agencies | $499/month |
| **MGA Starter** | Small MGAs, 20–100 producers | $9,900/year |
| **MGA Growth** | Mid-market MGAs, 100–500 producers | $24,900/year |
| **Enterprise** | Carriers, large platforms | $50,000+/year |
| **Pilot** | Any | $1,500 – $2,500 (100% credited to first-year contract) |

---

## The Larger Opportunity

Claims are the beachhead.

The same infrastructure can anchor any high-liability record in insurance where the custodian has the ability and motive to alter what they hold: underwriting records, policy changes, beneficiary designations, producer disclosure records, AI-generated recommendations, compliance disclosures, cancellation notices.

A carrier may not purchase "claim anchoring." They may purchase **enterprise evidence integrity infrastructure** — a permanent, independent provenance layer across every record category that touches regulatory and litigation risk.

Insurance is where this starts. Evidentiary infrastructure for regulated industries is where it ends up.

---

## About ICPO X Inc.

ICPO X develops provenance and evidentiary infrastructure for regulated industries.

---

## Sources

- Guidewire, January 2026: called for "provenance-protected workflows" and verification tools for content origin, alteration status, and authenticity confidence
- Verisk, *State of Insurance Fraud*, March 2026: 98% of insurers report AI editing fuels fraud; 45% anticipate stricter proof-of-loss requirements; 43% feel confident in authenticity detection at scale
- NAIC Blockchain Overview: blockchain records provide permanent audit trails; lists claims management and fraud prevention as identified use cases
- Deloitte: identifies trusted records, fraud reduction, and transaction validation as blockchain's strongest insurance applications
- RiskBlock Alliance: industry consortium validating blockchain for fraud reduction, claims streamlining, and shared multi-party records

---

*ClaimAnchor™ is a product of ICPO X Inc. · Pre-release draft · June 2026 · www.icpoxinc.com*
*Nothing herein constitutes legal, financial, insurance, or compliance advice.*
*BTC anchoring currently operates on Bitcoin testnet. Production mainnet deployment prior to commercial launch.*