LensReading which lens this session carries.
MK5C-1002In flightmedium materiality

Campaign send at detect defect

Marcus Sandoval

Marketing · Campaign Orchestration · MK5C Send Incident Response

$67k

value

93%

confidence

5

people affected

1h 8m

age

3h 40m

sla

17%

progress

Currently held by

Send-time Agent

An agent owns the next move

Raised by

Pierre Adeyemi

Requester of record

At station

Detect defect

Workflow layer · station 1 of 6

Where this train is on the line

MK5CSend Incident ResponseTransactional · 6 stations

Detect defect

1 live

Halt sends

7 q

Assess exposure

39 q

Notify

9 q

Remediate

35 q

Post-mortem

29 q

Evidence trail

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

This is the readable trail.

  1. Holding at detect defect

    -68m

    Calendar Coordination Agent

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

What happens next

The next station and its rule

Halt sends

run by Calendar Coordination Agent · AI GBS layer

No gate here. The agent clears this station inside its envelope and posts evidence.

Handed to the AI GBS depot

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 1h 8m against a commitment of 3h 40m · 31% of the time used
materiality medium · blast radius 5 records or people downstream
state in-flight — held separately, and deliberately not part of this reading