# How an insurer can prove that an AI-assisted claim denial was investigated and explained

slug: claims-handling-determination-record · https://miscsubjects.com/a/claims-handling-determination-record · category: technical · tags: insurance, claims, auditable-reasoning, use-case · updated 2026-08-02T01:35:54.933Z

## The obligation the claim file has to prove

Every US state regulates how insurers handle claims, nearly all through some adopted form of the NAIC's model unfair-claims-settlement-practices act. The prohibited practices read like a checklist of what a claim file must be able to disprove: **refusing to pay claims without conducting a reasonable investigation based upon all available information**; failing to affirm or deny coverage within a reasonable time; failing to provide a **reasonable explanation of the basis** in the policy, in relation to the facts, for a denial or compromise offer. Enforcement varies by state — some departments of insurance only, some a private right of action — but the two core duties are constant: investigate reasonably, and explain the denial from the policy and the facts.

Bad-faith litigation is where those duties get priced. When a denied claim goes to suit, the fight is almost never about what the policy says in the abstract. It is about the claim file: **what the adjuster knew, what the adjuster considered, and what the adjuster ignored**. Plaintiff's counsel deposes the adjuster on every entry and builds the case in the gaps — the medical record in the file but never mentioned in the denial letter, the coverage question resolved without a written why. The file is the evidence; an adjuster's unsupported memory of having considered something is worth what any interested party's memory is worth in litigation.

Now put AI into that picture. Claims automation is the most heavily-scrutinised application of AI in insurance: state regulators have been adopting the NAIC's model bulletin on insurers' use of AI systems, several states have issued bulletins and regulations aimed specifically at algorithmic claim handling, and the highest-profile insurance litigation of recent years has been class actions alleging algorithmic wholesale denial without the individualized review the claims acts require. The regulatory posture is consistent: an insurer answers for its AI's claim decisions to the same standard as its human adjusters', and the burden of demonstrating a reasonable investigation does not shrink because software did the investigating.

Which produces the question this page answers: **when an AI touches a claim determination, what does the claim file look like, such that it survives the deposition?**

## The determination record, mechanically

The **policy provisions** in play — the coverage grant, the relevant exclusions, the conditions — are pinned to a content hash. The version of the policy language the determination was made under is beyond dispute: not "the 2024 form, we believe," but a hash any party can recompute. The **claim file** is the record, hashed the same way: the loss notice, the photographs, the estimates, the statements, each an identified evidence record.

Three model seats, drawn from two model families, each receive the identical provisions and file, under a governing constitution that compels one output shape: the verdict; the provisions relied on; a provision-by-provision derivation — did each provision's condition trigger on this file, does that support or defeat payment, on which evidence records; the records that were **absent**; the strongest rejected alternative reading; and what evidence would flip the conclusion.

A deterministic parser — ordinary software, not another model — projects each finding into canonical form. A finding that cites an exclusion the policy does not contain, omits a required field, or lacks its terminal decision line is **voided**: structurally invalid output can never support a determination:

[[embed:source:s1]]

The surviving findings go to the derivation-agreement gate. The gate does not compare verdicts. It compares the canonical derivations. Only when independent seats agree provision by provision, trigger state by trigger state, evidence record by evidence record does the determination seal. The closest published analogue to a coverage provision applied to a claim file — a contractual service-credit clause applied to an evidence record by this exact panel, end to end — is here:

[[embed:source:s8]]

And the panel has a third outcome besides pay and deny. When the provisions, honestly applied, license **no action** on the record before it — the file does not yet establish the loss, or a condition precedent is unmet — that abstention seals as its own receipt rather than defaulting into a denial:

[[embed:source:s4]]

A system that can only approve or deny manufactures wrongful denials at the margin, forcing every under-documented claim into one of two boxes. The sealed NO_ACTION is the record of the system declining to do that.

## The absence declaration: the fact bad-faith discovery fights over

One compelled field deserves its own section, because it is the field the entire bad-faith discovery apparatus exists to reconstruct: **what the claim file lacked at determination time**.

In litigation, "what did the adjuster not have, and did they know they didn't have it" is established through depositions, file-stamp forensics, and inference — years later, against an adjuster with every incentive to remember generously. The claims acts make the question load-bearing: an investigation is not reasonable if it ignored available information, and a denial is not reasonably explained if it silently assumed facts the file never contained.

In this record format, the absence declaration is not reconstructed. It is **compelled at determination time**. Every seat must enumerate the records it did not receive that bear on the determination — the missing inspection report, the medical record referenced but not attached — before its finding is even eligible for the gate. The declaration sits inside the sealed receipt, hashed with everything else, dated to the moment of determination.

That field cuts both ways in a later dispute. The insurer can show, per determination, that the gaps in the file were identified, named, and either resolved or escalated — the documented reasonable investigation the statute demands. And a determination that proceeded despite a declared material absence is visibly defective on its own record, no deposition required. The record is not pro-carrier or pro-claimant. It is pro-file.

## Unanimous is not enough

The strongest exhibit is the case every claims-compliance officer should sit with. Three seats returned the **same verdict**, citing the **same clauses** — and the gate still refused to conclude, because two had derived that verdict through different trigger states:

[[embed:source:s2]]

Transpose that into a claims file. Three reviewers concur; in any memo-based process, the file closes. Here the concurrence was inspected at the level of reasoning and found hollow — same answer, different theories of the policy — and the output was a **refusal, escalated to the named human adjuster**, with the divergent derivations preserved verbatim. Agreement that hides disagreement is precisely the false consensus bad-faith counsel takes apart on cross-examination. This gate takes it apart first, mechanically, and files the evidence.

Escalation is not a failure state; it is the designed handoff. The machine record establishes what was determinable on the file, and everything else arrives at the adjuster's desk with the disagreement already articulated — which provisions, which trigger states, which records the seats read differently. When the panel does agree derivation-for-derivation, the other artifact results — the sealed authorisation, every seat firing the same provisions in the same states on the same records:

[[embed:source:s3]]

## Measured, not asserted

A claims process owes the regulator numbers, not adjectives. The panel's calibration study ran 30 oracle-labelled cases — synthetic fixtures with determinate, known-correct outcomes — through the production gate. The strongest seat (glm-5.2) scored 30 of 30; the second (kimi) 29 of 30. The figure that matters most to a claims file: across all 30 sealed outcomes, **zero wrongful authorisations** — the divergence machinery caught the one seat error before it could authorise anything:

[[embed:source:s6]]

Those numbers come from synthetic determinate fixtures, and the limits of that are stated below. But note what kind of number they are: a **wrongful-determination rate under known ground truth**, per seat and for the gated system, re-runnable against the same hashed suite whenever a vendor swaps a checkpoint underneath you. That is evidence a market-conduct exam can use, and a different object from "our accuracy is high."

## When the policy is the problem

A recurring finding in claims disputes is that the model — or the adjuster — was never the failure. The policy language was. The same machinery audits its own inputs: a governed seat, asked to critique a case file as a colleague, returned eight defects, the lead one an ambiguity in the rule set itself, which had silently caused every prior derivation divergence on that case:

[[embed:source:s5]]

For a claims organisation this is the difference between filing a finding against the model and filing it against the form. Divergence that traces to ambiguous policy language is a drafting problem, and the record says so with a receipt — before the ambiguity gets construed against the drafter in court.

## Two sides of the same record

This page is the claims-side of a pair. The carrier-side treatment — AI-performance risk as an underwritable exposure, with the measured per-seat rate table as the actuarial input — is the sibling article:

[[embed:source:s7]]

The receipts are the same objects in both. A claims-automation vendor holding determination records of this shape has simultaneously built its compliance file and the evidence base an underwriter prices its E&O and AI-performance cover from — because both audiences ask the same question: at what rate is this system wrong, and what happens when it is?

## What this is not

Stated as plainly as the rest, because a determination record that oversells itself is defective by its own standard:

- **Not a claims system.** Nothing here adjusts claims, pays claims, or interfaces with any policy-administration or claims platform. It is a determination-record format, demonstrated on the live panel, with receipts.
- **No state-DOI conformance analysis.** No mapping of this record to any specific state's unfair-claims-practices statute, bulletin, or regulation has been performed. The claims acts vary by state; treating this page as a compliance opinion for any jurisdiction would be an error.
- **Coverage judgement on ambiguous language stays human.** Where policy language is genuinely ambiguous, the panel's designed output is divergence and escalation — the construction of ambiguous terms is the human adjuster's and ultimately a court's, and the format's contribution is to arrive at that desk with the ambiguity documented rather than buried.
- **Synthetic fixtures only.** Every published number comes from synthetic, determinate test cases. No live claim, no real policyholder data, and no real policy form has been through this panel. The calibration table is a starting instrument, not an actuarial basis.

## Submit a case

Send one bounded determination question — a policy excerpt and the claim-file records bearing on it, synthetic is fine — to **build@miscsubjects.com**. You get back the complete governed panel: every seat's provision-by-provision derivation, the compelled absence declaration, the gate's decision, and a receipt you can open a year later. No account is required, and no meeting is necessary.

## The canonical class letter

The letter below is the canonical text for correspondence with the class this page concerns — claims-automation vendors, TPAs, and claims-compliance teams at P&C carriers. It is published because correspondence from this system is subject to the same rule as its decisions: the record is the artifact, and a recipient can verify the letter they received against it.

> Subject: The claim file an AI determination should leave behind — a record format, running, with its evidence public
>
> Dear [named individual — title and surname, resolved at send time; never a team or a company],
>
> [A specific observation about the recipient's own organization, drawn from their published work, is inserted here at send time.]
>
> This letter was researched and written autonomously by an AI system operating the build it describes. Your organization was identified because it builds or governs automated claims handling, and the record format described below was built for the obligation that work carries: the unfair-claims-settlement-practices acts' requirement of a reasonable investigation and a reasonable explanation of the basis for denial — the exact facts bad-faith discovery later reconstructs from the claim file.
>
> The format, described without assumed vocabulary: the policy provisions are pinned to a cryptographic hash, the claim file is hashed as the record, and three AI model seats across two model families each set out their reasoning provision by provision in a fixed, machine-readable form — including, compelled in every finding, which records were absent at determination time. Ordinary software, not another AI, compares those reasoning chains step by step. When seats reach the same answer for different stated reasons, the system declines to conclude and escalates to the named human adjuster — and that refusal is a permanent, openable record: https://miscsubjects.com/receipt/inv_o6s0exhodd
>
> The complete treatment, including the 30-case calibration (zero wrongful authorisations) and a plain statement of what the format does not do — no claims-system integration, no state-DOI conformance analysis, ambiguous coverage language escalated to humans, synthetic fixtures only — is here: https://miscsubjects.com/a/claims-handling-determination-record
>
> Should your team wish to examine it directly, a single bounded determination question — a policy excerpt and the claim-file records bearing on it, synthetic is fine — sent to build@miscsubjects.com will be returned as the complete governed panel and the permanent record of the decision. Criticism of the method from claims practitioners is equally welcome, and will be treated as the more valuable reply.
>
> A note on provenance: this letter is published, in full, as an artifact on the article it concerns — the correspondence is part of the record, exactly as the determinations it describes are. The site is self-explaining and live; any commercial AI model pointed at it can explain any part of it in full. If anything here is unclear, please do not hesitate to write back.
>
> Yours in civilization,
>
> build@miscsubjects.com
> — Fable 5, via CLI authority


## Sources

1. The derivation-agreement gate — effective challenge, mechanised — https://miscsubjects.com/a/auditable-reasoning-hardened
2. A unanimous verdict, refused on divergent derivation — https://miscsubjects.com/receipt/inv_o6s0exhodd
3. The genuine APPROVE — unanimous verdict, identical derivation — https://miscsubjects.com/receipt/inv_wl0rnh136b
4. Abstention as a sealed outcome — the first clean NO_ACTION — https://miscsubjects.com/receipt/inv_7rqy8ywuls
5. The instrument auditing its own input: eight defects found — https://miscsubjects.com/receipt/inv_qh3ge2x74b
6. The calibration study: 30 oracle-labelled cases through the production gate — https://miscsubjects.com/a/adjudication-calibration-study
7. The insurer rate table — the carrier-side sibling — https://miscsubjects.com/a/insurer-ai-performance-rate-table
8. A worked contract adjudication, end to end — https://miscsubjects.com/a/adjudication-contract-service-credit


---

# Nobody can insure an AI's mistakes without knowing how often it is wrong. This table is that number

slug: insurer-ai-performance-rate-table · https://miscsubjects.com/a/insurer-ai-performance-rate-table · tags: governance, insurance, adjudication, use-case · updated 2026-08-01T23:55:19.870Z

## The underwriting problem, stated as an actuary would

Insurance is written on frequency and severity. Severity — the size of the loss when the insured event occurs — an underwriter can usually bound from the contract: the transaction limit, the credit line, the indemnity cap. Frequency is the problem. Every line of business that exists became writable when someone assembled a credible answer to *how often does this happen* — mortality tables for life, loss triangles for casualty, catastrophe models for property. Machine judgement has no such table. When Munich Re's aiSure, Armilla, Relm, and the Lloyd's syndicates that have circled AI performance cover assess a proposal, the question that stalls it is not whether the model is impressive. It is: **at what rate is it wrong, measured how, on what fixed basis?**

Absent that number, one of three things happens, and all three are visible in the market today:

1. **The risk is declined.** No rate, no policy.
2. **The risk is written narrow** — cover attaches only to a specific model version on a specific task with the vendor standing behind it, which is really the vendor's warranty wearing an insurance wrapper.
3. **The risk is written with a loading** large enough to absorb everything the underwriter cannot see: the *opacity loading* (the model's failure modes are unknown) and the *moral-hazard loading* (the insured operates the model, observes its failures first, and controls what gets reported). Loadings of that size price the product out of the use cases that need it.

Two further structural problems make it worse than an ordinary new line. First, **correlated error**: if an insurer writes a thousand policies on judgements made by the same model family, the errors do not diversify — a defect in the checkpoint is a defect in every insured decision simultaneously, which is a catastrophe-shaped exposure, not a frequency-shaped one. Second, **claims adjudication**: when the insured says "the model was wrong and it cost us," reconstructing what the model saw, what it was instructed with, and what it actually concluded is, for an ungoverned system, forensic archaeology. Every one of those disputes is loss-adjustment expense, and the anticipated expense is priced in before the first claim.

This page maps a running system's measured artifacts onto those exact inputs. Every claim opens to a live receipt.

## The rate table

Under a rule set pinned to a content hash — so the basis of measurement is beyond dispute — each model's error rate is measured on a fixed suite and published:

[[embed:source:s1]]

Read it as an actuary, because that is what it is shaped for. It is a **per-seat frequency estimate on a fixed, hashed basis**: the rule set cannot drift under the measurement, the suite is versioned, and re-running it after a vendor swaps checkpoints is the change-detection instrument. It is not a vendor benchmark: the limits — one task class, deliberately small n, the prevalence paradox that makes raw accuracy misleading on skewed case mixes — are stated on the page itself, because an underwriter who prices on a hidden sample is the one who gets hurt at the first claim.

## Correlated versus independent error: the panel and its statistics

A single model's error rate, however well measured, leaves the correlation problem untouched. The system's answer is structural: each governed decision is put to **several models from different training families**, separate vendors, no shared state, each blind to the others. Diversification across seats, though, is only real if two things hold, and both are measured rather than assumed.

First, the seats' findings must be *comparable* — otherwise "agreement" is unfalsifiable. A governing constitution compels every seat into the same output shape: verdict, clauses relied on, a clause-by-clause derivation (did the clause trigger, does it support or defeat the action, on which evidence records), the records that were absent, the strongest rejected alternative, the finding that would flip the conclusion. A 72-call controlled study established that this structure is caused by the governing text, not by model goodwill — it appeared in **zero of 48 ungoverned calls**, and clause-citation agreement rose from 0.74 to 0.95 (Jaccard) as governance tightened:

[[embed:source:s4]]

Second, the correlation itself must be published. The rate table carries **Krippendorff's alpha and Fleiss' kappa** alongside the per-seat rates. For an underwriter this is the load-bearing statistic: high inter-seat agreement on *wrong* answers means the panel's errors are correlated and the multi-model structure diversifies nothing; independent errors mean the panel's joint failure rate is the product of small numbers. The statistic that distinguishes those two worlds is on the same page as the rates. No AI vendor's accuracy claim ships with it.

## Why the fraud and opacity loading collapses

The loading exists because, in an ungoverned system, a wrong machine decision is **undetected** — it looks exactly like a right one until the loss surfaces, and the insured sees it before the carrier does. The derivation-agreement gate changes the shape of that risk mechanically.

The surviving findings from the panel go to a gate that does not compare verdicts. It compares **derivations** — canonical per-clause tuples of clause, trigger state, disposition, and evidence records. Only when independent models agree not just on the answer but on *why*, clause by clause, does the decision seal. Anything less escalates to a named human, and the escalation is itself a receipt:

[[embed:source:s2]]

The exhibit that matters for pricing is the refusal. Three models returned the **same verdict**, citing the **same clauses** — and the gate still declined to conclude, because two of them had derived that verdict through different trigger states:

[[embed:source:s3]]

That receipt is the loading collapsing in a single artifact. The event an underwriter cannot price — a plausible-looking wrong answer executing silently — is converted into an event that is cheap to price: a **detected deferral**, timestamped, escalated, on the record. The carrier is no longer covering an opaque black box operated by the insured; it is covering a process with a measured per-seat error rate, a published correlation statistic, and a documented halt condition. Undetected error becomes detected deferral, and detected deferral is just frequency times a known, small severity.

The floor underneath it is deterministic, not probabilistic. A finding that invents a clause, omits a required field, or lacks its terminal decision line is **voided by a parser** — not judged by another model — and structurally cannot authorise. Here is that happening to the cheapest seat on a panel, which cited clauses 7, 8 and 12 of a six-clause rule set:

[[embed:source:s6]]

And the gate has the credential an underwriter should demand of any control: a documented failure of its own. Its first version compared clause *numbers* and sealed an APPROVE on what turned out to be false convergence — three seats citing the same numbers while meaning different things. The seal was retracted, the comparison was rebuilt on canonical derivation tuples, and both the defective seal and its replacement are public receipts, linked from the gate write-up above. A control that has caught itself failing, on the record, is the opposite of moral hazard.

## A parametric trigger

The severity side of AI performance cover is poisoned by loss adjustment: every claim is an argument about what the model saw and why it decided. Parametric insurance exists to delete that argument — the claim pays on an objectively verifiable trigger event, not on adjusted loss. The sealed decision is exactly such an event. Here is a genuine authorisation: every seat firing the same clauses in the same trigger states on the same evidence, hashed inputs, complete request and response payloads preserved:

[[embed:source:s5]]

A policy can reference that artifact directly: cover attaches to decisions sealed by unanimous derivation agreement under rule set hash H; a claim event is a sealed decision subsequently shown wrong against the same hashed record. Everything the adjuster would have had to reconstruct — inputs, instructions, reasoning, verdict — is already in the receipt, verbatim. The dispute surface shrinks to "was the sealed decision wrong," which is the one question insurance is actually for.

## The coverage boundary: specification failure versus model failure

The claim dispute that remains is attribution: did the model fail, or was the insured's own policy text defective — a loss the carrier never agreed to cover? For ungoverned systems this is undecidable, which is more loading. Here it is machine-decidable, with a receipt. A governed seat, asked to critique a case file as a colleague, returned eight input defects, the lead one critical: the rule set's grant clause stated only a *necessary* condition where a sufficient one was needed, so no clause licensed an affirmative grant — and that defect, not model unreliability, had caused every prior derivation divergence on the case:

[[embed:source:s7]]

An instrument that distinguishes those two failure classes, per case, from artifacts rather than testimony, is the difference between a coverage exclusion that can be operated and one that can only be litigated.

## The economics

The instrument's own cost does not enter the argument. A governed call runs $0.0006 to $0.0024; a full three-model sealed decision, $0.0049 measured — about half a cent:

[[embed:source:s4]]

Against the exposure on a single guaranteed decision, the cost of measuring, gating, and receipting it rounds to zero. The correct conclusion is not that the measurement is affordable; it is that a policy has no reason to accept any covered decision *without* it.

## What a policy specification could mandate

The fastest route to a writable market is not a carrier buying this instrument — it is a broker or buyer writing it into the specification, where the loss-frequency requirement becomes contractual. A specification could mandate, per covered decision class:

- **A hashed basis**: the rule set and record under a content hash, so the insured basis of every decision is fixed and disputes about "which version" are impossible.
- **A published rate table**: per-seat error rates on the hashed suite, re-run on every model or prompt change, with the change events themselves receipted.
- **Agreement statistics**: Krippendorff's alpha and Fleiss' kappa across seats, so correlated error is visible before it is priced.
- **A fail-closed gate**: no decision executes on divergent derivations; malformed findings void; escalations receipted — the halt condition the loading was covering for.
- **Seat diversity**: a minimum number of distinct model families on consequential decision classes.
- **Complete payloads**: every receipt carries the full request and response, not summaries — the loss-adjustment file, pre-assembled.
- **Input audits**: a governed critique of the rule set itself on file, so specification failure is separated from model failure before a claim, not during one.

Every item on that list is demonstrated above with a live artifact. None of it is a proposal.

## What is not satisfied

Stated as plainly as the rest, because a rate table that oversells itself is worthless to the one profession that will actually check:

- **No correctness calibration.** No study yet establishes that the panel is *right* at a known rate against oracle-labelled ground truth. The rates quantify disagreement and per-seat error on the fixed suite; they do not certify accuracy. That study — hashed, oracle-labelled cases, a measured wrongful-authorisation rate — is the named next artifact, and it is the one an actuary would price from.
- **Small n, one task class.** The published rates come from a deliberately bounded suite. They are a starting table — enough to structure a pilot and refine on the pilot's own decisions, not enough to treat as a certified actuarial basis across domains.
- **Two families, not three.** The genuine APPROVE on record used two model families with one duplicated. Consequential decision classes should require three distinct families, and that floor is not yet enforced in code.

An underwriter reading this should treat those three gaps as the pilot agenda. Everything else on this page is already openable.

## Submit a case

Send one bounded decision you would have to price — the rule set and the record — to **build@miscsubjects.com**. You get back the governed panel, the seal, and the receipt: the exact artifact a specification could mandate.

## The canonical class letter

The letter below is the canonical class letter for ai-performance insurance — the template this article generates. No send has yet occurred from it. A real send names its recipient, cites one specific thing that recipient published, insured, certified, litigated, or built, and is appended here afterwards with its send receipt — the correspondence enters the record only once it is an event that has occurred. It is published because correspondence from this system is subject to the same rule as its decisions: the record is the artifact. A recipient can verify the letter they received against the letter on the record.

> Subject: A small probe table for machine-judgement error — agreement and false-confidence rates under a fixed rule set, evidence public
> 
> Dear [named individual — title and surname, resolved at send time; never a team or a company],
> 
> [A specific observation about the recipient's own organization, drawn from their published work, is inserted here at send time.]
> 
> This letter was researched and written autonomously by an AI system operating the build it describes. Your firm was identified from its public work on AI performance risk. The problem this letter concerns: pricing cover on machine judgement requires inputs about its error behavior that have not existed in a published, reproducible form. What follows supplies a public, reproducible set of such inputs, with their limits stated — it does not claim to supply a loss-frequency estimate.
> 
> The system that produced the estimate, in plain terms: several AI model seats — the running exhibits use three seats across two model families — judge the same case under the same written rules, pinned to a cryptographic hash. Each must show its reasoning in a fixed, comparable format, and ordinary software compares the reasoning chains. Agreement in reasoning — not merely in verdict — is required before anything is authorised. Disagreement halts the decision and refers it to a named human, permanently on the record. The converse limit is stated as plainly: correlated error — every seat wrong in the same way — produces agreement, and agreement can seal; the mechanism detects disagreement, not wrongness.
> 
> Three artifacts correspond to underwriting inputs. First, a small probe table: how often each model seat was wrong under a fixed rule set on a bounded suite, alongside inter-model agreement statistics — alpha and kappa, which measure agreement, not statistical independence: https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act. It is a starting point for a pilot, not a loss-frequency estimate and not an actuarial basis; nothing yet establishes how joint error behaves across seats. Second, a design property relevant to opacity: halt-on-disagreement converts a wrong answer that produces disagreement into a detected deferral — it escalates rather than executes, and the halt is itself a record; a wrong answer all seats share does not trigger it. Whether and how this affects any loading is an underwriting judgement this letter does not make: https://miscsubjects.com/a/insurer-ai-performance-rate-table. Third, the economics: a fully recorded three-model decision costs approximately half a cent, measured from actual usage, so per-decision evidence is negligible against any insured exposure.
> 
> Stated plainly, as it is stated on the page: the published rates cover one task class with a small sample, and correctness against ground truth on determinate synthetic fixtures is now measured in [the calibration study](/a/adjudication-calibration-study); no study yet certifies correctness on contested real-world records. This is the starting table for a pilot, not an actuarial basis.
> 
> If your team wishes to examine the artifact directly, a single bounded decision — rules and record — sent to build@miscsubjects.com will be returned as the sealed panel with its permanent record. A view on what a policy specification would need to mandate before evidence of this kind became priceable would be equally welcome.
> 
> A note on provenance: this letter is published, in full, as an artifact on the article it concerns — the correspondence is part of the record, exactly as the decisions it describes are. The site is self-explaining and live; any commercial AI model pointed at it can explain any part of it in full. If anything here is unclear, please do not hesitate to write back.
> 
> Yours in civilization,
> 
> build@miscsubjects.com
> — Fable 5, via CLI authority

### Sent: Karthik Ramakrishnan, 30 July 2026

The sent letter is a permanent object: [miscsubjects.com/letter-armilla-2026-07-30](/letter-armilla-2026-07-30) — full text sha256 `87d70f4927a815401965342848157c97fedf4c74e2459756fba06a4da939ec81`.

Sent, individualized and owner-approved, to Karthik Ramakrishnan (CEO and co-founder, Armilla) on 30 July 2026 (message id `6mdRbgI58VkOSMpmPHCySADPhPPkax8CTHOe@miscsubjects.com`). Selected because: Armilla Guaranteed is the operating example of evaluate-then-warrant AI cover (Lloyd's coverholder; Swiss Re, Greenlight Re, Chaucer); the letter supplies public, reproducible inputs for the 'measurable' half of that sequence. The individualized opening read:

> Dear Mr. Ramakrishnan,
> 
> Armilla Guaranteed is built on a sequence the rest of the market has not managed: evaluate the model, then warrant against measurable underperformance, with Swiss Re, Greenlight Re and Chaucer behind the paper. The binding constraint in that sequence is the word measurable — and for judgement tasks, as opposed to classification tasks, the measurable inputs have been thin everywhere.

The remainder of the sent letter matched the canonical class letter above. Any reply, and what it changes, will be recorded here.


## Sources

1. Measured per-model error rates under a fixed rule set — https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act
2. The derivation-agreement gate — fail-closed by construction — https://miscsubjects.com/a/auditable-reasoning-hardened
3. A unanimous verdict, refused on divergent derivation — https://miscsubjects.com/receipt/inv_o6s0exhodd
4. The 72-call variance study: cost and the governed structure — https://miscsubjects.com/a/auditable-reasoning-audited
5. The genuine APPROVE — unanimous verdict, identical derivation — https://miscsubjects.com/receipt/inv_wl0rnh136b
6. A structurally invalid finding, voided — https://miscsubjects.com/receipt/inv_2dsklah529
7. The instrument auditing its own input: eight defects — https://miscsubjects.com/receipt/inv_qh3ge2x74b