LensReading which lens this session carries.

RM-002 · Agents and autonomy

Agents already past the autonomy gate that no rule names

204 of 805 agents — 25% of the population. The same comparison, restricted to agents already running at autonomy A3 or A4. These act without a person in the path and no rule names them. The platform can close this.

Back to the register
Outstanding
204
agents of 805
State
Nothing has been done
No record shows any of these agents being named in a rule or moved back below the gate.
Who closes it
Platform
The platform can close this
First seen
2026-08-17
These records carry no timestamp of their own, so the first observation is the day the register opened.
Platform date
2026-09-16
30 days away, and nobody has agreed to it

Where this entry came from

The query, run against the platform's own records

The same comparison, restricted to agents already running at autonomy A3 or A4. These act without a person in the path and no rule names them.

These records carry no timestamp of their own, so the first observation is the day the register opened.

The records this counts

Who carries it

Taken from the records, never assigned

Ibrahim Sy · Director, IT Service Management

The owner named on the largest number of agent lifecycle records.

Thirty days from the first observation. The platform set this date; nobody has agreed to it.

What it would take to close this

2 steps, 1 of them waiting on something else

1Lower the ceiling on the agents past the gate until a rule names themHours
This is the subset already acting without a person in the path. The honest order is to stop first and bind second.
Ibrahim Sy · A decision, then an edit. The delay here is the decision.
2Bind, then restore the ceiling one agent at a timeDaysBlocked
Restoring autonomy on an agent that a rule now names is the same edit as the row above, run in the opposite direction.
The platform · Paced by the reading above it, not by the platform. Waits on RM-001, which has not closed.
1 step waits on somebody outside this platform. The same question across the whole register

Everything recorded against it

Each line is a record, not a note

The platform saw it2026-08-17
The platform · counted 204
The same comparison, restricted to agents already running at autonomy A3 or A4. These act without a person in the path and no rule names them.
An owner was taken from the records2026-08-17
The platform
Ibrahim Sy was taken from the records, not assigned. The owner named on the largest number of agent lifecycle records.
A date was set by the platform2026-08-17
The platform
Thirty days from the first observation, applied to every entry in the register without exception. Nobody has agreed to this date.
Measured again2026-08-17
The platform · counted 204
No record shows any of these agents being named in a rule or moved back below the gate.
Every line above was written by the platform. Nobody has touched this entry.

What it is tangled with

Dependencies taken from the steps, not asserted

Waits on

RM-001

Holds up

No other entry is waiting on this one.

Nobody agreed to this date

Every date on this page came from the same rule: thirty days from the first time the platform could see the gap. The platform set it. Nobody has agreed to any of them, no counterparty has been told, and none of them is a commitment. They are here so that an entry cannot sit without a clock against it, and they should be replaced by real dates the moment somebody accepts one.