Pipeline run at restore
Bruno Tanaka
Information Technology · Data & Integration Platform · IT8A Pipeline Incident
$40k
value
79%
confidence
28
people affected
2h 54m
age
2h 26m
sla
100%
progress
Currently held by
Pipeline Health Agent
An agent owns the next move
Raised by
Talia Voss
Requester of record
At station
Restore
Workflow 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 diagnose
-174mLineage Agent
Spine control pack posted, three-way evidence attached
Cleared auto-retry
-139mLineage Agent
Spine control pack posted, three-way evidence attached
Cleared backfill
-104mLineage Agent
Spine control pack posted, three-way evidence attached
Cleared escalate
-70mDirector, Data Platform
Approval recorded with rationale and policy clause cited
Holding at restore
-35mPlatform Strategy Agent
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 28m · 28 people or records downstream of this decision