LensReading which lens this session carries.
EN9C-1007In flightmedium materiality

Developer request at assign path

Owen Bianchi

Engineering · Developer Experience · EN9C Developer Onboarding

$90k

value

90%

confidence

34

people affected

2h 8m

age

2h 16m

sla

60%

progress

Currently held by

AI-OPS spine

Running in the shared AI GBS spine

Raised by

Oscar Baptiste

Requester of record

At station

Assign path

AI GBS layer · station 3 of 5

Where this train is on the line

EN9CDeveloper OnboardingTransactional · 5 stations

Trigger

42 q

Provision toolchain

24 q

Assign path

1 live

Verify readiness

26 q

Manager confirm

2 q

Evidence trail

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

This is the readable trail.

  1. Cleared trigger

    -128m

    Build Time Agent

    Inputs, rule version and output hash written to the evidence log

  2. Cleared provision toolchain

    -85m

    Build Time Agent

    Spine control pack posted, three-way evidence attached

  3. Holding at assign path

    -43m

    Build Time Agent

    Spine control pack posted, three-way evidence attached

What happens next

The next station and its rule

Verify readiness

run by Onboarding Automation 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

Green. This item is still inside the time it was committed to, and it is not close enough to that line for its materiality to pull it forward. Green says nothing about who holds it: an item can be green and sitting with a person.

clock 2h 8m against a commitment of 2h 16m · 94% of the time used
materiality medium · blast radius 34 records or people downstream
state in-flight — held separately, and deliberately not part of this reading