LensReading which lens this session carries.

The register

What the platform knows is not done

Every entry on this page was derived, not typed in. 23 entries across 14 registers, each one a query the platform runs against its own records rather than a line somebody typed into a plan.

Who has to act, and on how many entries

Every entry is classified once. The three add to the register.

Platform
3
The gap closes with an edit to records the platform already owns.
A person
13
A named person has to read something and decide. The platform can route it and hold the answer.
A commitment
7
Money, staff, or a reporting line. No feature closes these.
20 of the 23 entries need somebody outside this platform to act. What it would take to close each one

Agents and autonomy

3 entries derived from this part of the record

RM-001Agents that no written rule namesPlatform
620 of 1,361 agents
Ibrahim Sy · Director, IT Service Management
Nothing has been done
Platform date 2026-09-16
Every agent name is compared against the agent names written into the binding list of every policy item.
The records behind it3 steps to close it
RM-002Agents already past the autonomy gate that no rule namesPlatform
204 of 805 agents
Ibrahim Sy · Director, IT Service Management
Nothing has been done
Platform date 2026-09-16
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 records behind it2 steps to close it, 1 blocked
RM-003Agents outside lifecycle managementPlatform
1,159 of 1,361 agents
Ibrahim Sy · Director, IT Service Management
Nothing has been done
Platform date 2026-09-16
Every agent name is compared against the agent names carried on lifecycle records.
The records behind it2 steps to close it

Verification

2 entries derived from this part of the record

RM-004Positions that have never been checked by anyoneA person
148 of 209 positions
Chief Architect · Ratifier
Nothing has been done
Platform date 2026-09-16
Every strategy position reference is compared against the subject reference on every verification check.
The records behind it3 steps to close it
RM-005Checks where the checker is the authorA commitment
189 of 251 checks
Marta Alvarez, Cost Accounting Manager · Finance
Nothing has been done
Platform date passed 2025-11-20
Every verification check carries a flag set when the checking team differs from the authoring team.
The records behind it2 steps to close it, 1 blocked

Segregation of duties

1 entry derived from this part of the record

RM-006Duty conflicts that have only been detectedA person
291 of 385 conflicts
Group Financial Controller · Control owner
Part of the population is moving
Platform date 2026-08-18
Duty conflicts are counted by status.
The records behind it2 steps to close it

Records and lineage

2 entries derived from this part of the record

RM-007Records past their retention review dateA person
2,833 of 8,051 records
Nobody is named
Nothing has been done
Platform date 2026-09-16
Each retention class carries a count of records due for review.
The records behind it3 steps to close it, 1 blocked
RM-008Facts standing on an inference rather than a readA commitment
5,581 of 7,560 facts
Nobody is named
Nothing has been done
Platform date passed 2026-06-20
Every lineage fact carries a confidence.
The records behind it2 steps to close it, 2 blocked

Data quality

1 entry derived from this part of the record

RM-009Records held out of the runA person
67 of 171 records
N. Ferreira · Data owner
Part of the population is moving
Platform date 2026-09-08
Quarantine records are counted by status.
The records behind it2 steps to close it

Ownership

1 entry derived from this part of the record

RM-010Handoffs between functions with nobody namedA commitment
19 of 25 handoffs
Nobody is named
Nothing has been done
Platform date 2026-09-16
Every cross-flow handoff carries an owning party.
The records behind it2 steps to close it

Measurement

3 entries derived from this part of the record

RM-011Counts that disagree with the source and nobody has explainedA person
4 of 20 checks
A. Whitfield · Reconciliation owner
Nothing has been done
Platform date 2026-09-11
Each drift check compares a count held here against the same count in the system that owns it.
The records behind it2 steps to close it
RM-012Comparisons that have never been runA commitment
2 of 20 checks
A. Whitfield · Reconciliation owner
Nothing has been done
Platform date 2026-09-16
A drift check at never-run is a comparison that was defined and has never been executed against the source.
The records behind it1 step to close it, 1 blocked
RM-013Source systems that have never returned a recordA commitment
26 of 26 systems
A. Whitfield · Revenue Systems
Nothing has been done
Platform date 2026-09-16
Every source system carries a connection state.
The records behind it3 steps to close it, 1 blocked

Attestation

1 entry derived from this part of the record

RM-014Work accepted on somebody saying soA person
9 of 18 items
Nils Andersen · Submitter
Nothing has been done
Platform date 2026-09-10
Accepted intake items are checked for an attestation reference.
The records behind it2 steps to close it

Coverage

2 entries derived from this part of the record

RM-015Work seen off the platform that nobody has confirmedA person
4 of 16 processes
Sofia Kalogeropoulou · Function owner
Nothing has been done
Platform date 2026-09-08
Shadow processes are counted by state.
The records behind it3 steps to close it, 1 blocked
RM-016Items a week that the platform has never seenA commitment
15,628 of 200,240 items a week
Chief Administrative Officer · Function head
Nothing has been done
Platform date 2026-09-16
Coverage statements written against a function are summed.
The records behind it2 steps to close it, 1 blocked

Learning

2 entries derived from this part of the record

RM-017Positions that failed and nothing was written downA person
11 of 20 failures
Grace Abbott, Head of Internal Audit · Recorder
Nothing has been done
Platform date passed 2026-07-15
Every position whose outcome check says it did not hold is compared against the learning records.
The records behind it2 steps to close it
RM-018Break conditions that have firedA person
34 of 627 conditions
Chief Architect · Ratifier
Nothing has been done
Platform date 2026-09-16
Break conditions carry a fired flag set when the measured value crosses the threshold the position set for itself.
The records behind it2 steps to close it

Decisions

1 entry derived from this part of the record

RM-019Decisions past the date they were neededA person
3 of 12 decisions
Avery Chen · Chief of Staff to the CEO, on behalf of the CFO
Nothing has been done
Platform date passed 2026-07-08
Executive decisions are counted by status.
The records behind it2 steps to close it

Service levels

2 entries derived from this part of the record

RM-020Service levels being missedA commitment
12 of 28 service levels
Morgan Idris · Function Leader, Revenue Growth Management
Nothing has been done
Platform date passed 2026-02-19
Service levels are counted by status.
The records behind it2 steps to close it
RM-021Service levels past their review dateA person
8 of 28 service levels
Morgan Idris · Function Leader, Revenue Growth Management
Nothing has been done
Platform date passed 2026-06-14
Service levels are counted by status.
The records behind it2 steps to close it

Human in the loop

1 entry derived from this part of the record

RM-022Escalations waiting on a personA person
24 of 56 escalations
Rafael Achebe · Data Protection Officer
Part of the population is moving
Platform date 2026-09-15
Escalations are counted by status.
The records behind it2 steps to close it

Controls

1 entry derived from this part of the record

RM-023Control exceptions still openA person
11 of 12 exceptions
Acme Identity and Access Management · customer
Part of the population is moving
Platform date passed 2026-08-14
Control exceptions are counted by status.
The records behind it1 step to close it

Actions

What is waiting on a person

Every entry in this register was found by a query the platform already runs.

8

entries with a closure step that cannot start yet

RM-002 · RM-005 · RM-007 · RM-008 · RM-012 · RM-013 · RM-015 · RM-016. The step is written, the doer is named, and something outside the entry has to happen first.

7

entries that no software and no single person can close

RM-005 · RM-008 · RM-010 · RM-012 · RM-013 · RM-016 · RM-020. Each of these needs a hire, a budget line or a standing commitment.

7

entries already past the date the platform set

The oldest is RM-005, 270 days past.

3

entries whose underlying records name nobody at all

RM-007 · RM-008 · RM-010. The platform picks an owner by reading the most common owner on the records behind the gap.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

This surface runs the same queries that produce the gap counts elsewhere in the estate and turns each one into a worked entry with an owner, a date, a state and a history.

Live observability

What the record shows right now

All 23 entries on the register, split 3 ways by what it would actually take to close them.

Current distribution

23 register entries

The platform can close313%
A named person has to close1357%
Only the organization can close730%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Not yet. The register names the work and nothing has closed on it.

Not holding on the record

The written intent is that a gap the platform can count should not stay a number on a dashboard.

This register is derived, not written

This register is derived, not written.

Why there is no total

The counts on this page are in different units - agents, records, checks, items a week - so they are never added together.

Nobody agreed to these dates

Every date on this page came from the same rule: thirty days from the first time the platform could see the gap.

Where the owners came from

Owners are taken from the records, never invented.