Lead at log outcome

Victor Novak

Sales · Demand Qualification · SL3B Intent Surge Response

$31k

value

82%

confidence

people affected

1h 57m

age

1h 34m

sla

100%

progress

Currently held by

Routing Agent

An agent owns the next move

Raised by

Owen Sorensen

Requester of record

At station

Log outcome

Workflow layer · station 5 of 5

Where this train is on the line

SL3BIntent Surge ResponseTransactional · 5 stations

Detect surge

17 q

Match account

0 q

Assemble context

35 q

Alert seller

45 q

Log outcome

1 live

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 surge
-117m
Lead Enrichment Agent
Inputs, rule version and output hash written to the evidence log
Cleared match account
-94m
Fit Scoring Agent
Inputs, rule version and output hash written to the evidence log
Cleared assemble context
-70m
Intent Signal Agent
Inputs, rule version and output hash written to the evidence log
Cleared alert seller
-47m
Outreach Sequencing Agent
Inputs, rule version and output hash written to the evidence log
Holding at log outcome
-23m
Meeting Booking Agent
Inputs, rule version and output hash written to the evidence log

What happens next

The next station and its rule

This is the last station. more

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 1h 57m against a commitment of 1h 34m · 124% of the time used

materiality low · blast radius 17 records or people downstream

state evidence-posted — held separately, and deliberately not part of this reading

Past SLA by 23m · 17 people or records downstream of this decision