Escalated case at close

Yuki Kowalski

Customer Service · Tier-2 Technical · CS3A Escalated Case to Fix

$91k

value

94%

confidence

people affected

4h 16m

age

3h 57m

sla

100%

progress

Currently held by

GBS spine

Running in the shared AI GBS spine

Raised by

Yuki Whitfield

Requester of record

At station

AI GBS layer · station 7 of 7

Where this train is on the line

CS3AEscalated Case to FixTransactional · 7 stations

Receive

32 q

Diagnose

22 q

Analyze logs

3 q

Match known error

20 q

Apply workaround

5 q

Verify

9 q

1 live

Evidence trail

Every station this unit has passed, who acted, and what they left behind

Auditor pack

This is the readable trail. more

Cleared analyze logs
-256m
Reproduction Agent
Inputs, rule version and output hash written to the evidence log
Cleared match known error
-205m
Known-Error Match Agent
Inputs, rule version and output hash written to the evidence log
Cleared apply workaround
-154m
Workaround Agent
Inputs, rule version and output hash written to the evidence log
Cleared verify
-102m
Engineering Handoff Agent
Inputs, rule version and output hash written to the evidence log
Holding at close
-51m
Engineering Handoff Agent
Spine control pack posted, three-way evidence attached

What happens next

The next station and its rule

This is the last station. more

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.

clock 4h 16m against a commitment of 3h 57m · 108% of the time used

materiality medium · blast radius 35 records or people downstream

state auto-cleared — held separately, and deliberately not part of this reading

Past SLA by 19m · 35 people or records downstream of this decision