Timeline Repair
Best for: F01
Steps: Build one event chronology, Restore missing anchors, Explain decisive gaps
Requires: order date, shipment/support timestamps, final dispute timestamp
The engine should never stop at “weak case”. It must point to the repair protocol that knows what to fix first.
Best for: F01
Steps: Build one event chronology, Restore missing anchors, Explain decisive gaps
Requires: order date, shipment/support timestamps, final dispute timestamp
Best for: F02
Steps: Link order to tracking, Attach POD or handoff proof, Map recipient/address status
Requires: tracking reference, carrier status, recipient details
Best for: F03
Steps: Link payer, buyer, recipient, Show order/payment relation, Resolve actor mismatch
Requires: order id, payment proof, recipient evidence
Best for: F04
Steps: Create evidence map, Reduce duplicates, Set reading order
Requires: attachment list, channel inventory
Best for: F05, F11
Steps: Write one summary, Make the ask explicit, Trim reader path
Requires: case summary, desired outcome
Best for: F06
Steps: Identify reason code, Filter irrelevant proof, Add policy-relevant evidence
Requires: reason code, policy snapshot, matching evidence
Best for: F07
Steps: Recover response trail, Insert signed acceptance or reply proof, Highlight acknowledgment point
Requires: email thread, signed note or acceptance, portal response
Best for: F08
Steps: Locate conflict, Choose source of truth, Explain or remove mismatch
Requires: conflicting records
Best for: F09
Steps: State requested decision, Tie ask to evidence map, Trim ambiguity
Requires: desired outcome
Best for: F10
Steps: Rank missing proof, Build minimum viable submission, Escalate only what matters before deadline
Requires: deadline date, critical missing items
Best for: F11
Steps: Build reviewer-facing surface, Add summary + ask + evidence order, Export one clean pack
Requires: core evidence set
Best for: F12
Steps: Narrow the claim, Set one remedy, Remove side disputes
Requires: current claim statement