Change at regenerate

Simon Baptiste

Engineering · Build · EN3C Documentation Sync

$40k

value

85%

confidence

people affected

4h 3m

age

3h 56m

sla

50%

progress

Currently held by

GBS spine

Running in the shared AI GBS spine

Raised by

Daniel Lindqvist

Requester of record

At station

Regenerate

AI GBS layer · station 2 of 4

Where this train is on the line

EN3CDocumentation SyncTransactional · 4 stations

Detect drift

18 q

Regenerate

1 live

Owner review

9 q

Publish

36 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 drift
-243m
Build Orchestrator
Spine control pack posted, three-way evidence attached
Holding at regenerate
-122m
Specification Agent
Spine control pack posted, three-way evidence attached

What happens next

The next station and its rule

Owner review

run by Director, Platform Engineering · Policy layer

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

approver Director, Platform Engineering

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 4h 3m against a commitment of 3h 56m · 103% of the time used

materiality low · blast radius 36 records or people downstream

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

Past SLA by 7m · 36 people or records downstream of this decision