Escalated case at match known error
Aaron Bianchi
Customer Service · Tier-2 Technical · CS3A Escalated Case to Fix
$20k
value
75%
confidence
15
people affected
6h 32m
age
3h 23m
sla
57%
progress
Currently held by
Tier-2 Technical Orchestrator
An agent owns the next move
Raised by
Yuki Farouk
Requester of record
At station
Match known error
Workflow layer · station 4 of 7
Where this train is on the line
Evidence trail
Every station this unit has passed, who acted, and what they left behind
This is the readable trail. more
Cleared receive
-392mDiagnostic Agent
Inputs, rule version and output hash written to the evidence log
Cleared diagnose
-294mLog Analysis Agent
Inputs, rule version and output hash written to the evidence log
Cleared analyze logs
-196mReproduction Agent
Inputs, rule version and output hash written to the evidence log
Holding at match known error
-98mKnown-Error Match Agent
Inputs, rule version and output hash written to the evidence log
What happens next
The next station and its rule
Apply workaround
run by Workaround Agent · Workflow layer
No gate here. The agent clears this station inside its envelope and posts evidence.
Why the signal is what it is
Derived from time against commitment, not from the state
Amber. Either this item is at or past the time it was committed to and is not material enough to escalate, or it is inside the time but has burned three quarters of it while carrying high or critical materiality. Amber says nothing about who holds it: an item can be amber and moving normally through an agent.
Past SLA by 3h 9m · 15 people or records downstream of this decision