Approved remedy decision
Comes from refund/replacement approval gate. It is a permission to route, not execution.
Remedy execution split
After support approval, FAEDA routes the case toward replacement, refund finance, shop correction, or escalation. This page prepares downstream drafts only.
Execution boundary
This gate creates the correct remedy route. Replacement stock, rider dispatch, refund finance, partner rail, ledger posting, and trust impact still need their own later approvals.
Approvals
3
remedy decisions
Replace
1
replacement lane
Refund
1
finance lane
Value
PKR 850
candidate value
Loading
Loading approved remedy and settlement evidence.
Step 1
In production these packets come from the approval gate. The split cannot start from a raw complaint.
Step 2
Readiness
Needs one proofIssue linked
Customer item selected
Support checker decision present
Shop replacement stock not confirmed
Dispatch draft not created
Step 3
Step 4
Owner assignment is a draft label here. Real role permissions and task queues come later.
Creates
Blocked
Approved remedy decision
Comes from refund/replacement approval gate. It is a permission to route, not execution.
Split into correct lane
Replacement, refund, shop correction, or escalation gets its own evidence packet.
Prepare downstream draft
Stock, dispatch, finance, partner, or support closure gets a draft only.
Later gate executes
Real stock, dispatch, refund, partner callback, ledger, and trust impact remain separate.
Source evidence
Settlement review
03-Jul-2026, 6:52 pm
Runtime locks
Next connected gates