Pipeline run at escalate

Rafael Kowalski

Information Technology · Data & Integration Platform · IT8A Pipeline Incident

$17k

value

46%

confidence

357

people affected

16h 16m

age

13h 6m

sla

83%

progress

Currently held by

Director, Data Platform

A person owns the next move

Raised by

Kofi Costa

Requester of record

At station

Escalate

Policy layer · station 5 of 6

Where this train is on the line

IT8APipeline IncidentTransactional · 6 stations

Detect failure

6 q

Diagnose

33 q

Auto-retry

44 q

Backfill

40 q

Escalate

1 live

Restore

30 q

Evidence trail

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

Auditor pack

This is the readable trail. more

Cleared detect failure
-976m
Lineage Agent
Spine control pack posted, three-way evidence attached
Cleared diagnose
-781m
Lineage Agent
Spine control pack posted, three-way evidence attached
Cleared auto-retry
-586m
Lineage Agent
Spine control pack posted, three-way evidence attached
Cleared backfill
-390m
Lineage Agent
Spine control pack posted, three-way evidence attached
Holding at escalate
-195m
Director, Data Platform
Inputs, rule version and output hash written to the evidence log

What happens next

The next station and its rule

Restore

run by Platform Strategy 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

Red. This item is past the time it was committed to and it is either high or critical materiality or wide enough downstream to matter. Red says nothing about who holds it: an item can be red and still be moving through an agent that has not stopped.

clock 16h 16m against a commitment of 13h 6m · 124% of the time used

materiality low · blast radius 357 records or people downstream

state human-hold — held separately, and deliberately not part of this reading

Past SLA by 3h 10m · 357 people or records downstream of this decision

Open the escalation lane