Files
hermes-skills/skills/devops/debt-recovery-workflow/references/claim-audit-trail.md
T

1.7 KiB

DRE Claim Audit Trail

What Gets Tracked

Every edit to a claim submission is recorded with four fields:

  • What changed (field name, old value → new value)
  • Who made the change (username or "System")
  • When (timestamp)
  • Why (optional note field)

Color Coding

  • Amber/gold — DRE team edit (e.g. "John (DRE) changed Amount: $12,000 → $12,450")
  • Blue — System action (e.g. "System changed Status: Submitted → AI Review")
  • Purple — AI re-analysis triggered by new documents (e.g. "System re-analyzed claim — Score: 78 → 82 ⬆")
  • Green — Client action (e.g. "Robert Smith created claim")

Edit Scope

  • Open claims ONLY — closed claims are read-only
  • Document uploads trigger AI re-analysis but are not "edits" in the audit trail sense (they appear in the timeline instead)
  • Change reason field is optional for DRE team edits; auto-populated for system changes

When Re-analysis Fires

  1. New document uploaded by client
  2. Claim amount edited by DRE team
  3. Claim status changed

Each re-analysis event records: previous score → new score, reason, and timestamp. The score delta is visible in both the case timeline and the change history.

Data model

{
  "claim_id": "DRE-2026-0042",
  "entries": [
    {
      "timestamp": "2026-07-08T10:15:00-04:00",
      "actor": "John (DRE)",
      "actor_type": "team",
      "field": "amount",
      "old_value": "$12,000",
      "new_value": "$12,450",
      "reason": "Corrected from invoice"
    }
  ]
}

Enforcement

  • Open claims: allow edits, track every change
  • Closed claims: read-only — no edits permitted
  • Audit trail included in DRE Internal Binder on case close