Promise at notify

Daniel Achebe

Supply Chain · Order Promising · SC9B Promise Breach Response

$92k

value

81%

confidence

people affected

2h 59m

age

2h 15m

sla

100%

progress

Currently held by

M2D spine

Running in the shared AI GBS spine

Raised by

Sanjay Voss

Requester of record

At station

Notify

AI GBS layer · station 5 of 5

Where this train is on the line

SC9BPromise Breach ResponseTransactional · 5 stations

Detect slip

0 q

Assess customer impact

35 q

Draft communication

0 q

Owner approve

3 q

Notify

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 slip
-179m
Available-to-Promise Agent
Spine control pack posted, three-way evidence attached
Cleared assess customer impact
-143m
Capable-to-Promise Agent
Inputs, rule version and output hash written to the evidence log
Cleared draft communication
-107m
Substitution Agent
Inputs, rule version and output hash written to the evidence log
Cleared owner approve
-72m
Director, Order Promising
Approval recorded with rationale and policy clause cited
Holding at notify
-36m
Available-to-Promise 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 2h 59m against a commitment of 2h 15m · 133% of the time used

materiality medium · blast radius 15 records or people downstream

state evidence-posted — held separately, and deliberately not part of this reading

Past SLA by 44m · 15 people or records downstream of this decision