LensReading which lens this session carries.

Closing it

What it would take

49 steps across 23 register entries. 26 of them are edits to records the platform already owns. 23 are not: 16 wait on a named person and 7 wait on money, staff or a reporting line. 9 steps cannot start today because they wait on an entry that has not closed.

Steps written
49
across 23 entries
The platform can do
26
53% of the plan
A person has to act
16
33% of the plan
Needs a commitment
7
money, staff, or who reports to whom
Blocked today
9
waiting on a step or an entry that is not done

How long each step takes

Bands, never numbers. Nothing here has been timed.

Hours
21
Days
14
Weeks
7
Open ended
7
The four bands account for every step. 7 steps are open ended, which means it is a commitment rather than a piece of work and no band would be honest.

The one that holds up the rest

Derived from what each step waits on

RM-013 Source systems that have never returned a record

3 other entries have steps that cannot start until this one closes. It is the largest single item in the register and the least like software.

Every entry, in the order its own steps run

18 of 23 entries start with something the platform can do on its own

RM-001Agents that no written rule namesPlatform
  1. 1List every unbound agent against the rule that should name itThe platformHours
  2. 2Read the proposed bindings and refuse the wrong onesIbrahim SyDays
  3. 3Write the accepted names into the binding listsThe platformHours
RM-002Agents already past the autonomy gate that no rule namesPlatform
  1. 1Lower the ceiling on the agents past the gate until a rule names themIbrahim SyHours
  2. 2Bind, then restore the ceiling one agent at a timeThe platformDaysWaits on RM-001, which has not closed.
RM-003Agents outside lifecycle managementPlatform
  1. 1Create a lifecycle record for every agent that has noneThe platformHours
  2. 2Point each record at an evaluation suiteIbrahim SyWeeks
RM-004Positions that have never been checked by anyoneA person
  1. 1Queue the unchecked positions by what rests on themThe platformHours
  2. 2Check themChief ArchitectWeeks
  3. 3Record the verdict and the checkerThe platformHours
RM-005Checks where the checker is the authorA commitment
  1. 1Name a checking party that does not report into the authoring partyWhoever sets the reporting linesOpen ended
  2. 2Re-run the self-checks under the new partyThe platformDaysWaits on the step above it in the same entry.
RM-006Duty conflicts that have only been detectedA person
  1. 1Group the conflicts by the person holding both dutiesThe platformHours
  2. 2Take one duty away, or sign a compensating controlGroup Financial ControllerWeeks
RM-007Records past their retention review dateA person
  1. 1Present each class as a worklist rather than a numberThe platformHours
  2. 2Name an owner for each retention classNobody is named on these recordsOpen ended
  3. 3Review and disposeNobody is named on these recordsWeeksWaits on the step above it in the same entry.
RM-008Facts standing on an inference rather than a readA commitment
  1. 1Connect the systems the inferred facts came fromWhoever owns the source systemsOpen endedWaits on RM-013, which has not closed.
  2. 2Re-extract and raise the confidenceThe platformDaysWaits on RM-013, which has not closed.
RM-009Records held out of the runA person
  1. 1Route each held record to the owner already named on itThe platformHours
  2. 2Release or refuseN. FerreiraDays
RM-010Handoffs between functions with nobody namedA commitment
  1. 1Put the priced gap in front of both function leadersThe platformHours
  2. 2Agree which function owns the gapNobody is named on these handoffsOpen ended
RM-011Counts that disagree with the source and nobody has explainedA person
  1. 1Show both counts side by side with the method that produced eachThe platformHours
  2. 2Explain the difference or accept the sourceA. WhitfieldDays
RM-012Comparisons that have never been runA commitment
  1. 1Run the comparisonThe platformHoursWaits on RM-013, which has not closed.
RM-013Source systems that have never returned a recordA commitment
  1. 1Choose which systems to connect firstThe platformHours
  2. 2Fund and staff the integrationWhoever funds the integration workOpen ended
  3. 3Move each system to live and re-measure everything drawn from itThe platformWeeksWaits on the step above it in the same entry.
RM-014Work accepted on somebody saying soA person
  1. 1Refuse to treat an unattested acceptance as evidenceThe platformHours
  2. 2Get a named person to signNils AndersenDays
RM-015Work seen off the platform that nobody has confirmedA person
  1. 1Put the inferred process in front of the function that would be doing itThe platformHours
  2. 2Confirm or refuse itSofia KalogeropoulouDays
  3. 3Model the confirmed onesThe platformWeeksWaits on the step above it in the same entry.
RM-016Items a week that the platform has never seenA commitment
  1. 1Publish the unseen volume per function with its uncertainty bandThe platformHours
  2. 2Connect the systems carrying the unseen volume, or ask the people doing itWhoever owns the source systemsOpen endedWaits on RM-013, which has not closed.
RM-017Positions that failed and nothing was written downA person
  1. 1Show every failed position beside the record that is missingThe platformHours
  2. 2Write down what was learned, including that nothing changedGrace Abbott, Head of Internal AuditDays
RM-018Break conditions that have firedA person
  1. 1Send the notice to a person rather than writing a rowThe platformDays
  2. 2Withdraw or restate the positionChief ArchitectWeeks
RM-019Decisions past the date they were neededA person
  1. 1Show the cost of the delay and what is blocked behind itThe platformHours
  2. 2DecideAvery ChenDays
RM-020Service levels being missedA commitment
  1. 1Show the measured attainment against the committed targetThe platformHours
  2. 2Add capacity, change the target, or pay the penaltyThe parties to the commitmentOpen ended
RM-021Service levels past their review dateA person
  1. 1Call the review the commitment already asks forMorgan IdrisDays
  2. 2Record the outcome against the commitmentThe platformHours
RM-022Escalations waiting on a personA person
  1. 1Age the queue and show what each escalation is holding upThe platformHours
  2. 2Answer themRafael AchebeDays
RM-023Control exceptions still openA person
  1. 1Work the exception queue that already existsAcme Identity and Access ManagementDays

Who is being waited on

Names taken from the register entries, not assigned here

Ibrahim SyA person3
Chief ArchitectA person2
Nobody is named on these recordsA commitment2
Whoever owns the source systemsA commitment2
A. WhitfieldA person1
Acme Identity and Access ManagementA person1
Avery ChenA person1
Grace Abbott, Head of Internal AuditA person1
Group Financial ControllerA person1
Morgan IdrisA person1
N. FerreiraA person1
Nils AndersenA person1
Nobody is named on these handoffsA commitment1
Rafael AchebeA person1
Sofia KalogeropoulouA person1
The parties to the commitmentA commitment1
Whoever funds the integration workA commitment1
Whoever sets the reporting linesA commitment1
18 parties are waited on across 23 steps. The platform can route every one of them and hold every answer. It cannot supply one.

What no software closes

7 entries in the register

RM-005Checks where the checker is the author189 of 251 checks
Independence is a second person who does not report into the first. That is a staffing commitment, not a feature. The platform refuses to count a self-check as independent and can do nothing further.
RM-008Facts standing on an inference rather than a read5,581 of 7,560 facts
A fact becomes a read rather than an inference when the system that owns it is connected. That is the connection work in RM-013, not a change to this platform.
RM-010Handoffs between functions with nobody named19 of 25 handoffs
Naming the owner of the gap between two functions is a decision two function leaders have to reach. The platform can price the gap and it does; it cannot settle it.
RM-012Comparisons that have never been run2 of 20 checks
A comparison cannot run against a system that is not connected. This one waits on RM-013.
RM-013Source systems that have never returned a record26 of 26 systems
This is the root of most of the register. Until a system is connected, every count taken from it is modeled, every comparison against it is not run, and every fact drawn from it is an inference.
RM-016Items a week that the platform has never seen15,628 of 200,240 items a week
Unseen volume becomes seen when the systems carrying it are connected or the people doing it tell us. Both sit outside the platform.
RM-020Service levels being missed12 of 28 service levels
A missed level is closed by capacity, by a changed target, or by paying the penalty. All three are commitments, not configuration.
30% of the register sits here. The register itself

Actions

What is waiting on a person

A sequence is only useful if it says where it stops. These are the places this one stops, in the order they should be read.

9

steps that cannot start yet

Each blocked step names what has to happen first, and RM-013 is behind 3 of them. A blocked step is still written out in full, because a plan that hides its dependencies reads as faster than it is.

7

steps the platform will not put an effort band against

These are hires, budget decisions and standing commitments. The board prints open-ended rather than a number of weeks, because a fabricated estimate on a step like this is worse than no estimate.

7

entries the software cannot finish under any sequence

RM-005 · RM-008 · RM-010 · RM-012 · RM-013 · RM-016 · RM-020. Every one of these has a written sequence and none of the sequences end in the platform. They are the honest floor of what this product can do about its own findings.

1

entry with no platform step anywhere in its sequence

RM-023. The platform contributes nothing at all to closing these, not even the measurement. Naming them keeps the board from reading as though software is always part of the answer.

Operations

What this desk is allowed to start

A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.

Trigger and bound

This surface holds a written sequence for every entry on the register: what happens, in what order, who does it, roughly how long it takes and what it waits on. It performs none of it. The steps the platform can do are the ones already implemented on other pages, and the board points at them rather than running them from here.

Live observability

What the record shows right now

All 49 closure steps across 23 entries, split 3 ways by who has to do the work. The three add to 49 because every step names exactly one doer.

Current distribution

49 closure steps

The platform does it2653%
A named person does it1633%
The organization does it714%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Not yet. The sequence exists for every entry and not one step has been recorded as done.

Not holding on the record

The written intent is that the platform should be specific about what closing a finding costs rather than leaving it as an owner and a date. That holds on paper: 49 steps across all 23 entries, 18 of which start with something the platform does itself, and the heaviest named load falls on Ibrahim Sy at 3 steps. It does not hold in the record. There is no completion state on a step, nothing writes back when one is done, and 23 of the 49 steps are somebody else’s work in the first place. This board is a plan, and the product does not display it as progress.

What is judgment here and what is not

The steps are a plan, and a plan is a judgment. Two things on this page are not judgments: who does each step, which is taken from the owner already derived onto the register entry, and whether a step is blocked, which is derived from whether the entry it waits on has closed. Effort is given as a band and never as a number, because nothing here has been timed.

The limit of the product

Some entries cannot be closed by software at all. Independence of verification is a second person who does not report into the first. An attestation is a name against a statement. Connecting a system is money and staff. The platform can show the gap, route the work and hold the result, and that is the whole of what it can do about these.