Developer request at draft fix

Mei Kowalski

Engineering · Developer Experience · EN9B Friction Remediation

$72k

value

85%

confidence

people affected

2h 9m

age

1h 50m

sla

50%

progress

Currently held by

Friction Sensing Agent

An agent owns the next move

Raised by

Victor Muller

Requester of record

At station

Draft fix

Workflow layer · station 3 of 6

Where this train is on the line

EN9BFriction RemediationTransactional · 6 stations

Sense signal

26 q

Diagnose

33 q

Draft fix

1 live

Owner accept

3 q

Ship

23 q

Measure

13 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 sense signal
-129m
Build Time Agent
Spine control pack posted, three-way evidence attached
Cleared diagnose
-86m
Environment Provisioning Agent
Inputs, rule version and output hash written to the evidence log
Holding at draft fix
-43m
Tooling Support Agent
Inputs, rule version and output hash written to the evidence log

What happens next

The next station and its rule

Owner accept

run by Director, Developer Platform · Policy layer

Held for a named human when the unit exceeds the developer request decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

approver Director, Developer Platform

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 2h 9m against a commitment of 1h 50m · 117% of the time used

materiality medium · blast radius 18 records or people downstream

state in-flight — held separately, and deliberately not part of this reading

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