F01 M2
Repair path →Timeline Fracture
The chronology is broken, incomplete, or impossible to follow.
Location
M2 / dispute chronology / timeline
Clears when
Unified timeline exists · Critical events restored or explained
Stage 1
Fault taxonomy and fault registry are now explicit.
This is the diagnostic language of the platform. Each code has a module, a localization template, and a repair protocol.
12 fault codes8 modules22 published sensors12 repair protocols
F02 M3
Repair path →Delivery Ambiguity
Delivery proof exists but does not clearly connect order, handoff, and status.
Location
M3 / order-tracking link / delivery_chain
Clears when
Tracking linked to order · Proof of delivery or handoff strengthened
F03 M1
Repair path →Identity Gap
The payer, buyer, recipient, or account relationship is not fully tied together.
Location
M1 / payer-order link / identity_chain
Clears when
Order, payment, and recipient are linked
F04 M4
Repair path →Evidence Scatter
Evidence exists but is spread across too many files, channels, or formats for efficient review.
Location
M4 / bundle structure / evidence_pack
Clears when
Evidence map exists · Reader-facing order created
F05 M6
Repair path →Reviewer Friction
The reviewer has to work too hard to understand the case.
Location
M6 / summary block / reviewer_surface
Clears when
Summary and ask present
F06 M5
Repair path →Policy Mismatch
The evidence does not answer the actual dispute reason or review requirement.
Location
M5 / reason-code mapping / policy_fit
Clears when
Proof bundle matches the reason code
F07 M5
Repair path →Acknowledgment Failure
No clear acceptance, response, or acknowledgment trail exists.
Location
M5 / response trail / ack_path
Clears when
Acknowledgment or response trail added
F08 M7
Repair path →Contradiction Risk
The case contains contradictory dates, actors, amounts, or statements.
Location
M7 / statement conflicts / claim_consistency
Clears when
Conflicts resolved or explicitly explained
F09 M6
Repair path →Missing Ask
The file describes the case but never says what decision is requested.
Location
M6 / decision ask / decision_request
Clears when
Requested decision is explicit
F10 M8
Repair path →Deadline Risk
The deadline is near and unresolved gaps still threaten submission quality.
Location
M8 / deadline proximity / submission_window
Clears when
Critical gaps reduced before deadline
F11 M6
Repair path →Third-Party Readiness Failure
The file may make sense internally, but it is not ready for outside review.
Location
M6 / reviewer surface / third_party_handover
Clears when
Reader-facing bundle exists
F12 M6
Repair path →Scope / Claim Drift
The claim has drifted away from the core issue or remedy.
Location
M6 / requested outcome / claim_scope
Clears when
Core issue and requested remedy narrowed