Change at escalate
Hannah Mensah
Engineering · Build · EN3B Dependency Update
$14k
value
86%
confidence
30
people affected
11h 24m
age
6h 19m
sla
100%
progress
Currently held by
Dependency Update Agent
An agent owns the next move
Raised by
Callum Lindqvist
Requester of record
At station
Escalate
Policy layer · station 6 of 6
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 assess breaking change
-684mSpecification Agent
Spine control pack posted, three-way evidence attached
Cleared patch
-547mCode Generation Agent
Spine control pack posted, three-way evidence attached
Cleared test
-410mScaffold Agent
Spine control pack posted, three-way evidence attached
Cleared auto-merge low risk
-274mRefactor Agent
Spine control pack posted, three-way evidence attached
Holding at escalate
-137mDirector, Platform Engineering
Inputs, rule version and output hash written to the evidence log
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.
Past SLA by 5h 5m · 30 people or records downstream of this decision