Fault report
What the diagnostic report looks like when the engine fires.
This is the canonical output object for the new product direction: fault → location → severity → confidence → repair protocol → reviewer simulation path.
Example
{
"main_fault": {
"code": "F02",
"title": "Delivery Ambiguity",
"location": "M3 / order-tracking link / delivery_chain",
"severity": 82,
"confidence": 0.88,
"repair_protocol_id": "RP-DELIVERY-02"
},
"supporting_faults": [
{ "code": "F04", "location": "M4 / bundle structure / evidence_pack" },
{ "code": "F09", "location": "M6 / decision ask / decision_request" }
],
"missing_evidence": [
"Delivery confirmation / POD",
"Evidence map / reading order",
"Explicit decision ask"
],
"state": "needs_repair",
"recommendation": "RP-DELIVERY-02"
}
Main fault
The dominant structural weakness stopping the file right now.
Location
Where the fault lives: module, submodule, object.
Severity & confidence
How hard the fault hits and how confident the engine is.
Repair routing
The exact repair protocol and pack route that should handle the fault.