LensReading which lens this session carries.
RO10A-1020Evidence postedmedium materiality

Change at escalate

Talia Tanaka

Revenue Growth Management · Systems & Integration · RO10A Integration Incident

$43k

value

79%

confidence

31

people affected

3h 2m

age

5h 9m

sla

67%

progress

Currently held by

Sync Failure Agent

An agent owns the next move

Raised by

Hannah Ellery

Requester of record

At station

Escalate

Policy layer · station 4 of 6

Where this train is on the line

RO10AIntegration IncidentTransactional · 6 stations

Detect failure

0 q

Classify

42 q

Auto-retry

7 q

Escalate

1 live

Restore

25 q

Post-mortem

46 q

Evidence trail

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

This is the readable trail.

  1. Cleared detect failure

    -182m

    Sandbox Refresh Agent

    Spine control pack posted, three-way evidence attached

  2. Cleared classify

    -137m

    Sync Failure Agent

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

  3. Cleared auto-retry

    -91m

    Sandbox Refresh Agent

    Spine control pack posted, three-way evidence attached

  4. Holding at escalate

    -46m

    Director, Revenue Systems

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

What happens next

The next station and its rule

Restore

run by Access Provisioning 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 3h 2m against a commitment of 5h 9m · 59% of the time used
materiality medium · blast radius 31 records or people downstream
state evidence-posted — held separately, and deliberately not part of this reading