The NAIC market-conduct examination request is the worst thing that lands in a carrier compliance inbox. It always reads the same way: "Reconstruct the complete decision context behind claim P-9871, as it stood on March 15th."
Three months ago. The rate table has had a Q1-to-Q2 transition since then. The policy form was updated in April. The adjuster's authority matrix changed in February. Your DBA has rolled six Postgres snapshots since the date in question. The Splunk logs from March are still searchable, but reconciling timestamps to rate-table versions is somebody else's eight-hour day.
Most carriers handle this in about six weeks. Two engineers lose a sprint. Outside counsel bills $850 an hour. By the time the response goes back, $90,000 in legal and engineering time has gone to evidence reconstruction, and you still aren't fully certain nothing in the record has been silently modified since March.
What the examiner is actually testing
The state DOI examiner isn't testing whether you adjudicated correctly. They're testing whether you can prove your records haven't been tampered with after the fact. AS-1105 in the audit-evidence world is straightforward: evidence is only admissible if you can prove it hasn't been modified.
That's three things:
- Bitemporal reconstruction. The system must answer "as it stood on March 15" — not "as it stands now," not "from a backup somebody can vouch for."
- Decision lineage. The denial cited exclusion 4.2(c). The exclusion existed in the form. The form was in force. The inspector's report supported the exclusion. All of that has to be one walk.
- Tamper-evidence. The record must be provably unmodified between the decision date and today.
If you put a bitemporal graph + a SHA-256 audit chain under your claim system, all three become one-query operations.
The one-query reconstruction
MATCH (c:Claim) AT RECORDED '2026-03-15T08:00:00Z'
WHERE c.id = 'P-9871'
OPTIONAL MATCH (c)-[:USED_RATE_TABLE]->(rt:RateTable)
OPTIONAL MATCH (c)-[:UNDER_POLICY_FORM]->(pf:PolicyForm)
OPTIONAL MATCH (c)-[:ADJUDICATED_BY]->(a:Adjuster)
RETURN c, rt.version, pf.form_id, a.authority_grantThe AT RECORDED clause rolls the entire claim graph back to March 15 — every node, every edge, every property as the engine understood them on that day. The rate table that was in force. The policy form version. The adjuster's authority matrix at the moment of adjudication. The denial reason as cited at the time.
Total elapsed time on a typical claim graph: under 30 seconds.
The tamper-evidence proof
The harder examiner question is: "How do we know you didn't edit the record after the fact?" The audit chain answers. Every entry in the claim's lifecycle from creation to today is a SHA-256 link. The first link is signed against a trusted root anchor. Every subsequent link includes the hash of the prior link.
CALL db.verifyAclChain('claim:P-9871', from='2026-02-28', to='now')
YIELD entries, tampered
RETURN entries, tamperedFor a well-formed claim, this returns tampered: []. If any single entry between adjudication and today had been altered, the rehash would not match the recorded head, and the proc would name the broken link. The examiner gets cryptographic certainty, not your assertion.
The lineage walk
The third examiner question is "show us the inputs." db.derivedFrom walks every input edge backward. The denial cites exclusion 4.2(c). The exclusion derives from the policy form. The policy form has its filing date with the state DOI. The inspector's report — signed and dated by the inspector — feeds into the exclusion citation. The photo set referenced by the inspector's report is one more edge away. Every depth, every signature.
The examiner doesn't have to take your word for any of it. They walk the graph.
The numbers
A six-week audit-response project costing $180,000 becomes a six-minute project costing about zero. The audit chain stands up to the AS-1105 evidence-integrity standard cryptographically. There's no claim of "we believe nothing has been modified" — you can prove it.