LensReading which lens this session carries.
CS4C-1012In flightmedium materiality

Case at resolve

Simon Ito

Customer Service · Case Management · CS4C Reopen Handling

$64k

value

85%

confidence

35

people affected

4h 19m

age

6h 29m

sla

80%

progress

Currently held by

Case Management Orchestrator

An agent owns the next move

Raised by

Owen Adeyemi

Requester of record

At station

Resolve

Workflow layer · station 4 of 5

Where this train is on the line

CS4CReopen HandlingTransactional · 5 stations

Detect reopen

46 q

Diagnose cause

40 q

Re-route

41 q

Resolve

1 live

Root cause log

27 q

Evidence trail

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

This is the readable trail.

  1. Cleared detect reopen

    -259m

    Case Lifecycle Agent

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

  2. Cleared diagnose cause

    -194m

    SLA Clock Agent

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

  3. Cleared re-route

    -130m

    Aging & Backlog Agent

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

  4. Holding at resolve

    -65m

    Follow-up Agent

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

What happens next

The next station and its rule

Root cause log

run by Reopen Detection 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 4h 19m against a commitment of 6h 29m · 67% of the time used
materiality medium · blast radius 35 records or people downstream
state in-flight — held separately, and deliberately not part of this reading