ClaimLens Showcase · fictional policies

Claim · policy P-1005

a1e1923c-4a2e-4775-ad86-d19f3158ebb2

FRAUD_REVIEW R1 reviewed Log verified · 17 events

Photo p1 is a near-copy (0 bits apart) of a photo in claim af36d7c3-1920-4589-9de1-f941a8f72f25.

Stages

  1. Intake chat skipped filed by form
  2. Photo check done 1 accepted, 0 rejected
  3. Damage and parts done 2 finding(s)
  4. Integrity done
  5. Pricing done
  6. Coverage done
  7. Triage agent done
  8. Decision done FRAUD_REVIEW (R1)
  9. Memory done
  10. Human review done deny

Photos

Claim photo p1 glass_shatter · 0.96 glass_shatter · 0.91
p1 · accepted

Evidence

Story
Someone broke my side mirror in the supermarket car park.
Damage
glass_shatter (0.96); glass_shatter (0.91)
Estimate
$1200–$2500
Coverage
active, collision cover, $500 deductible
Fraud signals
photo_near_copy (0.80): Photo p1 is a near-copy (0 bits apart) of a photo in claim af36d7c3-1920-4589-9de1-f941a8f72f25.

Triage agent advises; the rules decide

FRAUD_REVIEW confidence medium · 3 model call(s) · $0.0225

The claim photo is an exact near-copy (0 bits apart) of a photo in another claim (af36d7c3-...), which suggests the image was reused (E1). The story is also vandalism by an unknown person, which is covered under STD-5.2 with the collision deductible, and STD-9.3 requires a police report. The history shows no police report, and I could not open the other claim to compare.

Clauses cited
STD-5.2, STD-9.3
Evidence cited
e6119dc7-82ed-4d01-9794-f504374eba2a
Skills used
glass-claims@v1
Tools used
find_similar_claims, get_claim_history
Open questions
Is the photo in claim af36d7c3-1920-4589-9de1-f941a8f72f25 the same image, and is it from the same claimant or vehicle? · Has a police report been filed for the vandalism (STD-9.3)? · Why do the vision findings show glass_shatter on an unknown part rather than the side mirror?

Similar claims in memory

None found, or memory is off.

Audit trail (17 events)
  1. 1 · ClaimReported · human:claimant · 2026-10-03T14:25:30+00:00
  2. 2 · PhotoUploaded · human:claimant · 2026-10-03T14:25:30+00:00
  3. 3 · PhotoAccepted · system:workflow · 2026-10-03T14:25:30+00:00
  4. 4 · DamageDetected · system:workflow · 2026-10-03T14:25:31+00:00
  5. 5 · IntegrityChecked · system:workflow · 2026-10-03T14:25:31+00:00
  6. 6 · CostEstimated · system:workflow · 2026-10-03T14:25:31+00:00
  7. 7 · PolicyRetrieved · system:workflow · 2026-10-03T14:25:31+00:00
  8. 8 · LLMCalled · system:llm-gateway · 2026-10-03T14:25:33+00:00
  9. 9 · ToolCalled · agent:mcp:triage · 2026-10-03T14:25:33+00:00
  10. 10 · ToolCalled · agent:mcp:triage · 2026-10-03T14:25:33+00:00
  11. 11 · LLMCalled · system:llm-gateway · 2026-10-03T14:25:35+00:00
  12. 12 · LLMCalled · system:llm-gateway · 2026-10-03T14:25:41+00:00
  13. 13 · AgentRecommended · agent:triage-agent-v1+triage/v2 · 2026-10-03T14:25:41+00:00
  14. 14 · RouteDecided · system:workflow · 2026-10-03T14:25:41+00:00
  15. 15 · MemoryWritten · system:workflow · 2026-10-03T14:25:41+00:00
  16. 16 · HumanReviewed · human:Showcase investigator · 2026-10-03T14:25:41+00:00
  17. 17 · MemoryWritten · system:workflow · 2026-10-03T14:25:41+00:00