{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"claims-handling-determination-record","urls":{"read":"https://miscsubjects.com/api/articles/claims-handling-determination-record/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/claims-handling-determination-record/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/claims-handling-determination-record/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/claims-handling-determination-record/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/claims-handling-determination-record/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/claims-handling-determination-record/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/claims-handling-determination-record/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"claims-handling-determination-record","title":"The unfair-claims acts require a reasonable investigation and a reasonable explanation. When AI touches the determination, here is the claim file that proves both.","register":"technical","tags":["insurance","claims","auditable-reasoning","use-case"],"updated_at":"2026-07-30T15:05:19.571Z","body_excerpt":"## The obligation the claim file has to prove\n\nEvery 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.\n\nBad-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.\n\nNow 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.\n\nWhich 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?**\n\n## The determination record, mechanically\n\nThe **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.\n\nThree 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.\n\nA 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:\n\n[[embed:source:s1]]\n\nThe 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 p","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"State unfair-claims-settlement-practices acts, following the NAIC model act, prohibit denying claims without a reasonable investigation based upon all available information and require a reasonable explanation of the basis for denial.","tier":"system","section":"The obligation","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The legal duty this record format documents compliance with, in force in some form in nearly every state.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"A claims determination can be run as a governed panel: the policy provisions pinned to a content hash, the claim file hashed as the record, and each seat compelled to a machine-comparable clause-by-clause finding.","tier":"system","section":"The determination record","interaction_risk":false,"status":"active","source_ids":["s8"],"why_material":"Converts 'the adjuster considered the file' from testimony into an artifact.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"A deterministic parser voids any finding that invents a policy provision, omits a required field, or lacks its terminal decision line; structurally invalid output can never support a determination.","tier":"system","section":"The determination record","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"Fail-closed on malformed output is what makes model seats safe near a claim.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"A determination seals only when independent seats agree provision by provision, trigger by trigger, evidence record by evidence record — not merely on the verdict.","tier":"system","section":"The determination record","interaction_risk":false,"status":"active","source_ids":["s3"],"why_material":"Verdict-level agreement is exactly the false consensus bad-faith counsel attacks.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"A unanimous verdict with divergent derivations is refused and escalated to the human adjuster, and the escalation is itself a permanent receipt.","tier":"system","section":"Unanimous is not enough","interaction_risk":false,"status":"active","source_ids":["s1","s2"],"why_material":"The refusal receipt is documented reasonable investigation at the moment it matters most.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"Abstention is a sealed outcome: when the provisions license no action on the record before the panel, that conclusion seals as its own receipt rather than defaulting to denial.","tier":"system","section":"The determination record","interaction_risk":false,"status":"active","source_ids":["s4"],"why_material":"A system that can only approve or deny manufactures wrongful denials at the margin.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"In a 30-case oracle-labelled calibration on synthetic determinate fixtures, the strongest seat scored 30/30, the second 29/30, and the gate produced zero wrongful authorisations in 30 sealed outcomes.","tier":"system","section":"Measured, not asserted","interaction_risk":false,"status":"active","source_ids":["s6"],"why_material":"The wrongful-authorisation rate is the number a claims-compliance team actually needs.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"The same machinery audits the inputs: a governed critique of a case file found eight defects, the lead one an ambiguity in the rule set itself that had caused every prior divergence.","tier":"system","section":"When the policy is the problem","interaction_risk":false,"status":"active","source_ids":["s5"],"why_material":"Ambiguous policy language is a specification failure, not a model failure, and the record distinguishes the two.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"This page is the claims-side process record; the carrier-side treatment of AI-performance risk, with the measured rate table as the actuarial input, is its sibling.","tier":"system","section":"Two sides of the same record","interaction_risk":false,"status":"active","source_ids":["s7"],"why_material":"The same receipts serve the compliance file and the insurability question.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"No state DOI conformance analysis has been performed; coverage judgement on genuinely ambiguous language stays with the human adjuster; every published number comes from synthetic fixtures, not live claims.","tier":"system","section":"What this is not","interaction_risk":false,"status":"active","source_ids":[],"why_material":"A claims-compliance reader must not be sold more than the evidence supports, and these are the exact limits.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"live_surface","url":"https://miscsubjects.com/a/auditable-reasoning-hardened","title":"The derivation-agreement gate — effective challenge, mechanised","summary":"Independent models under a pinned rule set; the gate refuses to authorise when their clause-by-clause derivations diverge, even on a unanimous verdict. Includes the false-convergence defect and its fix.","claim_ids":["c3","c5"],"hash":"a270852719463ef88d1002adfc60dee5b12bec1b5c7bfe6b13bf78236122c585"},{"id":"s2","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_o6s0exhodd","title":"A unanimous verdict, refused on divergent derivation","summary":"Three seats returned the same verdict citing the same clauses; two derived it differently, so the gate escalated to a named human instead of concluding.","claim_ids":["c5"],"hash":"4fab017534425e015f87962564acb9780370cc7be042fac1ea590b23c5b6fd8b"},{"id":"s3","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_wl0rnh136b","title":"The genuine APPROVE — unanimous verdict, identical derivation","summary":"The one clean authorisation on record: every seat fired the same clauses in the same trigger states on the same evidence records.","claim_ids":["c4"],"hash":"db9a4b3542ef4c2717cb60adc495db3380f8fcfad92d0272f777f9361d491849"},{"id":"s4","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_7rqy8ywuls","title":"Abstention as a sealed outcome — the first clean NO_ACTION","summary":"The panel concluded, on identical derivations, that the rule set licensed no action on the record before it — and that conclusion sealed as its own receipt.","claim_ids":["c6"],"hash":"5cd663dc71054a6580718ae8e53f41cca2bc6a7a61bb8a1c46b3c8eb702608c5"},{"id":"s5","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_qh3ge2x74b","title":"The instrument auditing its own input: eight defects found","summary":"A governed seat asked to critique the case input found the rule set stated only a necessary condition where a sufficient one was needed — the divergence was the input, not the models.","claim_ids":["c8"],"hash":"c31c1232751b029496498f1160c8ae664e3a63be0ba7ff257a933fff95708a22"},{"id":"s6","type":"live_surface","url":"https://miscsubjects.com/a/adjudication-calibration-study","title":"The calibration study: 30 oracle-labelled cases through the production gate","summary":"Synthetic determinate fixtures with known ground truth: the strongest seat 30/30, the second 29/30, and zero wrongful authorisations in 30 sealed outcomes.","claim_ids":["c7"],"hash":"7be91c059bbe7f26fde1dac547e7ac2c3f3e8c971c2864d3708fd144ba47d105"},{"id":"s7","type":"live_surface","url":"https://miscsubjects.com/a/insurer-ai-performance-rate-table","title":"The insurer rate table — the carrier-side sibling","summary":"The same machinery pointed at underwriting AI-performance risk: measured per-seat error rates as the actuarial input. This page is the claims-side process; that page is the carrier-side risk.","claim_ids":["c9"],"hash":"e4336c03fb1344b22a0be9c280dd5c9d69059c39567ac3de83e47d8c29a16331"},{"id":"s8","type":"live_surface","url":"https://miscsubjects.com/a/adjudication-contract-service-credit","title":"A worked contract adjudication, end to end","summary":"A service-credit clause applied to an evidence record by the full governed panel — the closest published analogue to a coverage provision applied to a claim file.","claim_ids":["c2"],"hash":"7510031322aede8115eaa8dea6905edd78301400e0a3e75e3467241c8cb18191"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"claims-handling-determination-record","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":10,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":10,"claims_total":10,"sources":8,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}