What gets attested for insurers?

Operational events each emit an H33-74 proof at the moment they occur: underwriting decisions (bind, decline, refer, exception, conditional), claim approvals, denials, reserve changes and partial payments, reinsurance allocations, subrogation actions, denial appeals, catastrophe response decisions, and policy framework changes.

Is the primitive different for insurance?

No. The primitive is unchanged — the same 74-byte post-quantum-signed proof (a 32-byte on-chain commitment plus a 42-byte compact receipt). Only the application context differs; insurance does not create a separate per-industry primitive.

Which regulations does the evidence support?

H33-74 produces evidence that supports requirements under frameworks such as SOX, DORA, GDPR, the EU AI Act, and the NAIC Model Audit Rule. It supports these requirements but does not by itself make an organization fully compliant.

Can evidence be verified without contacting H33?

Yes. Proofs are independently verifiable offline. A regulator, auditor, or counterparty can verify a proof directly without operator cooperation and without any contact with H33.

Does the evidence survive system, vendor, and chain changes?

Yes. Each proof outlives the system that produced it, the vendor that hosts it, and the chain it was anchored to. Migrating core systems, changing vendors, or re-anchoring to a different chain leaves prior proofs independently verifiable.

H33-74 for Insurance — Chain-Portable Underwriting Evidence

H33-74 for Insurance

Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.

This is H33-74 — the portable 74-byte post-quantum evidence primitive that produces and anchors operational proof — applied to insurance. The primitive is unchanged; only the application context differs. Chief Compliance Officers, Chief Actuaries, Chief Claims Officers, Chief Underwriting Officers at insurers and reinsurers need operational evidence that survives infrastructure change, vendor turnover, and regulatory horizon shifts. H33-74 makes that evidence cryptographically verifiable and chain-portable by construction.

The asset may move. The evidence remains. Every approval, transfer, decision, and policy action your insurance produces gets a 74-byte post-quantum-signed proof at the moment it happens. The proof outlives the system that produced it, the vendor that hosts it, and the chain it was anchored to.

What gets attested in insurance

Each of the following operational events emits an H33-74 proof at the moment it occurs. The collection composes into the operational history that audit, compliance, and regulatory teams reconstruct from.

Underwriting decisions: bind, decline, refer, exception, conditional.
Claim approvals, denials, reserves changes, partial payments.
Reinsurance allocations: facultative, treaty, retrocession.
Subrogation actions: pursuit, settlement, write-off.
Denial appeals: receipt, review, escalation, final disposition.
Catastrophe response decisions: declaration, reserve adjustment, accelerated payment.
Policy framework changes: rate filing, form filing, regulatory approval.

Regulatory pressure that already justifies this

Insurance is regulated under frameworks whose audit horizons now extend past the lifetime of the systems and vendors holding the evidence. H33-74 produces evidence that survives that horizon:

SOX. Publicly listed insurance holding companies. See: SOX crosswalk
DORA. EU insurers under DORA scope. See: DORA crosswalk
GDPR. Personal data processing in underwriting and claims. See: GDPR crosswalk
EU AI Act. High-risk AI in claims and underwriting. See: EU AI Act crosswalk
NAIC Model Audit Rule. Internal controls over financial reporting.

Scenarios this changes

Insurer migrates from one core insurance system to another

Every claim decision, underwriting determination, and reinsurance allocation from the old system remains independently verifiable. The new system inherits zero historical liability and zero audit risk from the change.

A class action requires proof of claim decisions four years ago

The original PQ-signed proofs are produced. The model version, adjuster signature, evidence reviewed, and policy framework in effect are all in the proof. No reconstruction from secondary records.

Regulator inquiry about an AI-flagged claim denial

The proof contains the AI score, the policy applied, the human reviewer, the final disposition, and the appeal chain. The regulator verifies directly without operator cooperation.

What survives versus what gets replaced

Survives

Every approval, decision, transfer, compliance check, and policy action your operation produced — independently verifiable forever.

Gets replaced as normal lifecycle work

The core systems, the vendor SaaS contracts, the cloud, the database product, the chain you anchored to. Each replacement is engineering work, not an existential project.

Insurance operational history compounds in value. Five years of approvals, decisions, and compliance determinations are usually worth more than the systems that produced them. H33-74 keeps that history independent of the infrastructure.

The proof itself is the flagship H33-74 attestation applied here — see the general evidence patterns this vertical reuses: AI attestation and AI decision attestation. Where protection must be shown to stay true over time as claim evidence, HATS records that continuous control history on this same H33-74 substrate.

How to start

Three integration patterns, ordered by how invasive each is.

Pattern 1 — Receipt at the policy engine

The decision system (policy engine, approval workflow, AI scorer) emits an H33-74 proof for every decision at the moment it is made. No change to upstream systems. Auditors verify proofs directly.

Pattern 2 — Receipt at the system of record

Each system of record (treasury, claims, records, EHR) is wrapped so that committed transactions emit H33-74 proofs in addition to the existing audit log. Existing systems remain unchanged. Proofs become a parallel canonical record.

Pattern 3 — Receipt at the integration bus

Service mesh or integration bus intercepts cross-system events and emits H33-74 proofs. Highest reach, requires bus integration. Useful where systems-of-record cannot be modified.

See the architecture

The mechanism that makes insurance evidence chain-portable.

Chain Portability What Gets Preserved