RM-001 · Agents and autonomy

Agents that no written rule names

620 of 1,361 agents — 46% of the population. Every agent name is compared against the agent names written into the binding list of every policy item. An agent that appears in no list is unbound. The platform can close this.

Back to the register

Outstanding

620

agents of 1,361

State

Nothing has been done

No record shows any of these agents being named in a rule since the register opened.

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

Every agent name is compared against the agent names written into the binding list of every policy item. An agent that appears in no list is unbound.

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

3 steps, none of them blocked

1List every unbound agent against the rule that should name itHours

The platform already knows each agent’s class, layer and sub-function; the policy library already holds a rule for most of those combinations. The match is a query, not a decision.

The platform · A query over records the platform already holds.

2Read the proposed bindings and refuse the wrong onesDays

A rule binding an agent is a statement about what that agent is allowed to do. Somebody has to disagree with the ones that are wrong before they are written.

Ibrahim Sy · Judgment over six hundred proposals. There is no way to make this quick and still mean it.

3Write the accepted names into the binding listsHours

The edit itself is mechanical once it has been agreed.

The platform · An edit to records the platform owns.

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 620

Every agent name is compared against the agent names written into the binding list of every policy item. An agent that appears in no list is unbound.

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 620

No record shows any of these agents being named in a rule since the register opened.

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

No other entry. Its first step can start today.

Holds up

RM-002

Alongside it in Agents and autonomy

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.