Order at re-submit

Sanjay Haddad

Revenue Growth Management · Booking & Order Management · RO4B Order Exception

$29k

value

96%

confidence

people affected

3h 31m

age

3h 20m

sla

100%

progress

Currently held by

O2C spine

Running in the shared AI GBS spine

Raised by

Lukas Duarte

Requester of record

At station

Re-submit

AI GBS layer · station 5 of 5

Where this train is on the line

RO4BOrder ExceptionTransactional · 5 stations

Detect exception

19 q

Classify

2 q

Auto-resolve

43 q

Human resolve

8 q

Re-submit

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 detect exception
-211m
Order Validation Agent
Inputs, rule version and output hash written to the evidence log
Cleared classify
-169m
Credit Check Agent
Inputs, rule version and output hash written to the evidence log
Cleared auto-resolve
-127m
Order Validation Agent
Spine control pack posted, three-way evidence attached
Cleared human resolve
-84m
Director, Order Management
Approval recorded with rationale and policy clause cited
Holding at re-submit
-42m
Order Validation 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 3h 31m against a commitment of 3h 20m · 106% of the time used

materiality low · blast radius 13 records or people downstream

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

Past SLA by 11m · 13 people or records downstream of this decision